> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/advanced-topics-pentaho-data-integration-overview/data-lineage/contribute-additional-step-and-job-entry-analyzers-to-the-pentaho-metaverse/examples/see-it-in-action.md).

# See it in action

It is assumed that you have set up your system for data lineage. If you have not already done so, see [Setup](https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/advanced-topics-pentaho-data-integration-overview/data-lineage/setup.md) for data lineage.

1. Save a transformation which contains a step you want to explore with the analyzer. (In the sample, use the Table Input step).
2. Connect a remote debugger to PDI on port 5005. Enter a breakpoint in your step analyzer's implementation.
3. Execute your transformation from PDI.

   You should hit your breakpoint when the step you are exploring is assessed by the transformation analyzer.

The execution will generate a GraphML file (along with an execution profile) for the transformation. You can find these files in `data-integration/pentaho-lineage-output/<Date of execution>/original/path/to/the/file/`. You can use a tool such as yEd to view the GraphML files.

**Note:** Working with yEd can be difficult. We have created a configuration for yEd to help ease the pain of viewing these graphs which you can access here: [https://github.com/pentaho/pentaho-engineering-samples/tree/master/Supplementary Files/yED Configuration Files](https://github.com/pentaho/pentaho-engineering-samples/tree/master/Supplementary%20Files/yED%20Configuration%20Files) Read the `readme.txt` file for help.

**Note:** In yEd, you will need to apply a layout to view the graph properly. Otherwise, all of the nodes will overlap each other.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/advanced-topics-pentaho-data-integration-overview/data-lineage/contribute-additional-step-and-job-entry-analyzers-to-the-pentaho-metaverse/examples/see-it-in-action.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
