Data Lineage

Top-level UI section for upstream / downstream lineage across the ODD entity model — both data-object lineage and microservices-tracing lineage.

The Data Lineage section of ODD Platform is the home for upstream and downstream traceability across the catalog. The role is durable: anything that documents how entities are connected — which dataset was read by which job, which job produced which model, which microservice traced which call — belongs here.

ODD covers Data Lineage fully and across two complementary surfaces — data-object lineage (catalog entities and the edges between them) and microservices lineage (OpenTelemetry-traced microservice calls rendered alongside the data graph). See the Data Governance map for the position of Data Lineage among the other governance pillars.

Open lineage from the Lineage tab on any data-entity detail page (per-entity view) or from the Group lineage entry point on a Data Entity Group detail page. The microservices view is reached from any catalogued microservice entity ingested through odd-tracing-gateway.

Subsections

• Data Objects Lineage — per-entity upstream / downstream graphs across the full ODD entity model: datasets, transformers, transformer runs, quality tests + their runs, consumers, data inputs, data entity groups (including ML experiments), and entity relationships. Backed by /api/dataentity/{id}/lineage plus the dedicated group-lineage endpoint.

• Microservices Lineage — microservice call lineage rendered alongside data-object lineage. Sourced from OpenTelemetry traces ingested via odd-tracing-gateway (the platform's only standalone gateway push adapter today).

Why this is a separate pillar

For how Data Lineage relates to the other governance pillars (Data Discovery, Data Modelling, Master Data Management, Data Glossary, Data Quality), see Main Concepts → Data Governance map → Pillar differentiation — the canonical home for the six-pillar framing. Lineage is its own pillar because the connection graph cuts across every other pillar; a dataset has a structure, a meaning, a location, a quality signal, and a lineage, and the lineage itself is the cross-pillar record.

Where to next

• If you want to trace upstream / downstream from a specific catalogued entity → Data Objects Lineage.

• If you ingest microservices through OpenTelemetry traces and want to see them alongside your data graph → Microservices Lineage.

• For the Lineage HTTP API (per-entity, group-level, and microservices) → API Reference → Lineage.

• For the broader catalog vocabulary (Data Entity, ODDRN, Plugin, Push adapter) → Main Concepts.

• For where Data Lineage sits among the other governance pillars → Main Concepts → Data Governance map.