Skip to main content
Gable analyzes your services’ source code to discover how data moves within each service — from the ingresses where data enters, through the transformations in code, to the egresses where it leaves. Combined with cross-service edges, those in-service paths chain together into end-to-end lineage: a field can be traced from where it originates, across every service and data store it passes through, to where it is finally consumed. Use the Lineage Explorer to navigate that graph.

​
Open the Lineage Explorer

The Lineage Explorer shows your components — services and data stores — connected by cross-service edges. The graph loads the component topology first, then fills in field-level details in the background.
The Lineage Explorer graph of services and data stores

The Lineage Explorer graph

Each service shows its ingresses and egresses; each data store shows its schema. If friendly names have been configured, they are shown alongside the underlying signature names.

​
Trace a field

  1. Open the field search sidebar and search for the field you want to trace.
  2. Select the field from the results. You can select multiple fields to trace them together.
  3. The graph filters to the selected fields, showing the field-level connections between components — which upstream fields feed the selection, and which downstream fields consume it.
Field-level lineage for a selected field

Field-level lineage for a selected field

Follow the connections hop by hop:
  • an egress field on one service connects to an ingress field on another service, or to a data store column
  • within a service, ingress fields connect to egress fields through the service’s internal paths
Your field selection is reflected in the page URL, so you can share a link that reproduces the exact trace you are looking at.

​
Inspect a mapping in a component

To understand how a single service produces a field, open its Component Details page (select the service in the Lineage Explorer and open its details).
  1. Open the Known dependencies section, which lists the component’s field mappings — each ingress field and the egress field it becomes.
  2. Select a mapping to open its details, including the code paths that produced it.
  3. Review the code path steps to see where the value is read, how it is transformed, and where it is written.
For the full set of metadata on each mapping — the Known dependencies columns and the code path steps — see Field-Level Lineage Metadata.
A field mapping's details with its code paths

A field mapping's details on the Component Details page

To inspect a cross-service connection, select the edge in the graph. The Edge Details panel shows every field mapping the edge carries. See Dependencies (Cross-Service Edges) for managing edges.

​
Next steps