This document provides information on data lineage compliance and limitations.Data lineage is enabled on a per-project basis, not aper-system basis.This means that after you enable the Data Lineage API, lineage informationcan be automatically reported for multiple systems in the project, depending oneach system's product-level lineage control.

Automatic lineage tracking is supported for the following systems:

Product-level lineage controls in Google Cloud supported systems

System	Available lineage controls
BigQuery, Cloud Data Fusion	There is no configurability to restrict lineage tracking to only Cloud Data Fusion or BigQuery when the Data Lineage API is enabled in a project.
Cloud Composer	Cloud Composer uses environment-level data lineage integration control. Data lineage is automatically enabled for all new Cloud Composer environments, provided they meet the requirements. See Data lineage with Dataplex Universal Catalog for more information. For existing environments, you can enable or disable data lineage integration in environment settings.
Dataflow	Dataflow jobs can capture lineage events and publish them to the Data Lineage API. SeeUse data lineage in Dataflow for more information.
Dataproc	Dataproc Spark jobs can capture lineage events and publish them to the Data Lineage API. SeeData lineage Dataproc integration for more information.
Vertex AI	Data lineage is automatically enabled for Vertex AI artifacts and parameters, such as models, datasets, pipeline templates, and components. The lineage of a pipeline includes factors that contributed to its creation, as well as artifacts and metadata derived afterwards. SeeTrack the lineage of pipeline artifacts for more information.

Important: SeeSupported systemsfor details on the support status of these systems. When a new system becomesavailable, depending on the level of that system'slineage control, the Data Lineage API can automatically start harvestinglineage data.

Billing impact

When you enable the Data Lineage API on a project, reviewthe impact on your billing charges because the Data Lineage API is enabledon a per-project basis (see the previous section for details).For more information about how data lineage is charged, seeDataplex Universal Catalog pricing.

For BigQuery Omni, lineage processingis distributed to specific regions, and costs depend on the regions wherethe processing is performed.

Data lineage compliance

• Data lineage records metadata about data movement butdoesn't capture the data itself. Seedata lineage information model andData Lineage API referencefor details on what fields are included in the metadata.
• Data lineage as part of Dataplex Universal Catalog offers VPC-SC support.
• Dataplex Universal Catalog doesn't offer the ability to useCustomer Managed Encryption Keys to protect the harvested lineage metadata.

Data lineage limitations

When you select a node in the lineage graph, the node details side panelwill be empty when:

1. the resources is located in another organization, or
2. the user is not a member of the organization hosting the resource.