Visualizar a linhagem no catálogo universal do Dataplex
Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Esta página descreve como conferir a linhagem de dados gerada pelos pipelines do Cloud Data Fusion com outros movimentos de dados em Google Cloud, para fins de descoberta e governança. É possível
visualizar os gráficos de linhagem das fontes de dados com suporte na
página do Dataplex Universal Catalog no console ou usar a API Data Lineage
para extrair registros completos de linhagem de dados.
Plug-ins compatíveis com a linhagem de dados do Dataplex Universal Catalog
O Cloud Data Fusion e o catálogo universal do Dataplex oferecem suporte à linhagem de recursos para os seguintes plug-ins:
Amazon S3
BigQuery
Coletor de várias tabelas do BigQuery (versão 6.9.1 e mais recentes)
Spanner
Cloud Storage
Cloud SQL para MySQL
Cloud SQL para PostgreSQL
Catálogo universal do Dataplex
FTP
Banco de dados genérico
HTTP
MSSQL/SQL Server
Origem de várias tabelas de banco de dados (versão 6.9.1 e mais recentes)
Conceda o papel de produtor de eventos de linhagem de dados
(roles/datalineage.producer)
à conta serviço gerenciado pelo Cloud Data Fusion, o agente de serviço da API Cloud Data
Fusion.
O processo varia se a instância for executada em uma versão anterior do Cloud Data Fusion e o RBAC estiver ativado.
6.10 ou mais recente ou sem RBAC
Se a instância do Cloud Data Fusion usa a versão 6.10.0 ou mais recente ou
usa uma versão anterior e o RBAC não está ativado, siga estas
etapas:
Marque a caixa de seleção Incluir concessões de papel fornecidas pelo Google.
Selecione a conta de serviço do agente de serviço da API Cloud Data Fusion e clique em
edit
Editar.
Clique em Adicionar outro papel e selecione a função Produtor de eventos de linhagem de dados.
Clique em Salvar.
<6.10 com RBAC
Se a instância do Cloud Data Fusion usar uma versão anterior à
6.10.0 e o RBAC estiver ativado, a conta de serviço não vai aparecer na
lista de principais na página do IAM. É necessário inserir o
nome da conta de serviço manualmente.
Para conceder o papel necessário, siga estas etapas:
No campo Novos participantes, insira a conta de serviço do agente de serviço da API Cloud Data Fusion. Use o seguinte formato: datafusion-system@TENANT_PROJECT_ID.iam.gserviceaccount.com.
Substitua TENANT_PROJECT_ID pelo ID do locatário da sua instância. Para conferir o ID do projeto do locatário, acesse a página Instâncias e clique no nome da instância para conferir os detalhes.
Selecione a função Produtor de eventos de linhagem de dados.
Clique em Salvar.
Ativar a linhagem de dados do Dataplex Universal Catalog no Cloud Data Fusion
Para novas instâncias no Cloud Data Fusion, a linhagem de dados do Dataplex Universal Catalog fica desativada por padrão. Se você criou a instância antes de 27 de janeiro de 2024 com a versão 6.8.0 ou mais recente, ela será ativada por padrão após a conclusão das etapas em Antes de começar.
Ativar a linhagem de dados do Dataplex Universal Catalog ao criar uma instância
Console
Para ativar a linhagem de dados do Dataplex Universal Catalog ao criar uma instância,
siga estas etapas:
Acesse a página Instâncias do Cloud Data Fusion e clique em Criar uma
instância.
Ao configurar a instância, abra a seção Opções avançadas e clique em Ativar a integração com a linhagem de dados do Dataplex. Para mais
informações sobre como criar instâncias, consulte Criar uma instância
pública.
API REST
Para ativar a linhagem de dados do Dataplex Universal Catalog ao criar uma instância,
defina a propriedade opcional dataplex_data_lineage_integration_enabled como
true:
No campo Integração da linhagem de dados do Dataplex, clique em Editar.
Ative ou desative a linhagem de dados do Dataplex Universal Catalog e clique em
Salvar.
API REST
Para ativar a linhagem de dados do Dataplex Universal Catalog em uma instância atual no
Cloud Data Fusion, defina a propriedade dataplex_data_lineage_integration_enabled
como true e inclua o valor do parâmetro updateMask:
Para desativar a linhagem de dados do Dataplex Universal Catalog em uma instância atual no
Cloud Data Fusion, defina a propriedade dataplex_data_lineage_integration_enabled
como false e inclua o valor do parâmetro updateMask:
A visualização da linhagem no Dataplex Universal Catalog tem as seguintes limitações:
A linhagem no catálogo universal do Dataplex só pode ser descoberta se houver uma entidade do BigQuery conectada aos plug-ins compatíveis. Para mais informações sobre quando os gráficos de linhagem de dados estão disponíveis, consulte Sobre a linhagem de dados.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-12 UTC."],[[["\u003cp\u003eThis page details how to view data lineage generated by Cloud Data Fusion pipelines, integrated with other data movement activities in Google Cloud, for enhanced discovery and governance.\u003c/p\u003e\n"],["\u003cp\u003eLineage graphs for supported data sources can be accessed through the Dataplex page in the console, or using the Data Lineage API for complete records.\u003c/p\u003e\n"],["\u003cp\u003eEnabling the Data Lineage API and granting the Data Lineage Events Producer role to the Cloud Data Fusion service account are essential prerequisites for viewing Cloud Data Fusion lineage graphs in Dataplex.\u003c/p\u003e\n"],["\u003cp\u003eDataplex data lineage is turned off by default for new Cloud Data Fusion instances, but can be enabled either during instance creation or for existing instances via the console or REST API.\u003c/p\u003e\n"],["\u003cp\u003eThere are certain limitations to viewing lineage in Dataplex, such as the necessity of a connected BigQuery entity, lack of support for customer-managed encryption keys, and region restrictions.\u003c/p\u003e\n"]]],[],null,["# View lineage in Dataplex Universal Catalog\n\nThis page describes how to view the data lineage generated by your\nCloud Data Fusion pipelines with other data movement on Google Cloud,\nfor discovery and governance purposes. You can\nview the lineage graphs for supported data sources on the\nDataplex Universal Catalog page in the console, or use the Data Lineage API\nto retrieve complete data lineage records. \n\nPlugins that support Dataplex Universal Catalog data lineage\n------------------------------------------------------------\n\nCloud Data Fusion and Dataplex Universal Catalog support asset-level\nlineage for the following plugins:\n\n- Amazon S3\n- BigQuery\n- BigQuery Multi Table sink (version 6.9.1 and later)\n- Spanner\n- Cloud Storage\n- Cloud SQL for MySQL\n- Cloud SQL for PostgreSQL\n- Dataplex Universal Catalog\n- FTP\n- Generic Database\n- HTTP\n- MSSQL/SQL Server\n- Multiple Database Tables source (version 6.9.1 and later)\n- MySQL\n- Oracle\n- PostgreSQL\n- SAP OData\n- SAP ODP\n- SAP Table\n\nFor more information, see\n[Cloud Data Fusion plugins](/data-fusion/plugins).\n\nBefore you begin\n----------------\n\nTo enable viewing Cloud Data Fusion lineage graphs on the\nDataplex Universal Catalog page in the console, do the following:\n\n1. [Create a data pipeline](/data-fusion/docs/create-data-pipeline)\n that uses only the [supported plugins](#supported_plugins).\n\n2. [Enable the Data Lineage API](/dataplex/docs/use-lineage) in the project that contains your\n Cloud Data Fusion instance.\n\n3. Grant the Data Lineage Events Producer role\n ([`roles/datalineage.producer`](/iam/docs/understanding-roles#datalineage.producer))\n to the Cloud Data Fusion-managed service account, the [Cloud Data\n Fusion API Service\n Agent](/data-fusion/docs/concepts/service-accounts#cloud-data-fusion-service-account).\n The process varies if your instance runs in an earlier version of\n Cloud Data Fusion and RBAC is enabled.\n\n ### 6.10+ or no RBAC\n\n\n If your Cloud Data Fusion instance uses version 6.10.0 or later, or\n your instance uses an earlier version and RBAC isn't enabled, follow these\n steps:\n 1. In the Google Cloud console, go to the **IAM** page.\n\n [Go to IAM](https://console.cloud.google.com/iam-admin/iam?supportedpurview=project)\n 2. Select the **Include Google-provided role grants** checkbox.\n\n 3. Select the Cloud Data Fusion API Service Agent service account and\n click\n edit\n **Edit**.\n\n 4. Click **Add another role** and select the **Data Lineage Events\n Producer** role.\n\n 5. Click **Save**.\n\n ### \\\u003c6.10 with RBAC\n\n If your Cloud Data Fusion instance uses a version earlier than\n 6.10.0 and RBAC is enabled, the service account doesn't appear in the\n list of principals on the IAM page. You must enter the\n service account name manually.\n\n To grant the required role, follow these steps:\n 1. In the Google Cloud console, go to the **IAM** page.\n\n [Go to IAM](https://console.cloud.google.com/iam-admin/iam?supportedpurview=project)\n 2. Click **Grant access**.\n\n 3. In the **New principals** field, enter the Cloud Data Fusion API\n Service Agent service account. Use the following format:\n `datafusion-system@`\u003cvar translate=\"no\"\u003eTENANT_PROJECT_ID\u003c/var\u003e`.iam.gserviceaccount.com`.\n\n Replace \u003cvar translate=\"no\"\u003eTENANT_PROJECT_ID\u003c/var\u003e with the\n tenant ID for your instance. To view the tenant project ID, go to\n the **Instances** page and click the instance name for instance\n details.\n\n [Go to Instances](https://console.cloud.google.com/data-fusion/locations/-/instances)\n 4. Select the **Data Lineage Events Producer** role.\n\n 5. Click **Save**.\n\nEnable Dataplex Universal Catalog data lineage in Cloud Data Fusion\n-------------------------------------------------------------------\n\nFor new instances in Cloud Data Fusion, Dataplex Universal Catalog data\nlineage is turned off by default. If you created the instance before January 27,\n2024 with version 6.8.0 or later, it's turned on by default after completing the\nsteps in [Before you begin](#before_you_begin).\n\n### Enable Dataplex Universal Catalog data lineage when you create an instance\n\n### Console\n\n\nTo enable Dataplex Universal Catalog data lineage when you create an instance,\nfollow these steps:\n\n1. Go to the Cloud Data Fusion **Instances** page and click **Create an\n instance**.\n\n [Create an instance](https://console.cloud.google.com/data-fusion/instance-create)\n2. When you configure the instance, expand the **Advanced options** section\n and click **Enable integration with Dataplex data lineage** . For more\n information about creating instances, see [Create a public\n instance](/data-fusion/docs/how-to/create-instance).\n\n### REST API\n\nTo enable Dataplex Universal Catalog data lineage when you create an instance,\nset the optional `dataplex_data_lineage_integration_enabled` property to\n`true`: \n\n echo '{ \"description\": \"CDAPinstance\", \"dataplex_data_lineage_integration_enabled\": \"true\"}' | curl -X POST \\\n -H \"Authorization: Bearer $(gcloud auth print-access-token)\" \\\n -H \"Content-Type: application/json\" \\\n --data @- \\\n \"https://datafusion.googleapis.com/v1/projects/\u003cvar translate=\"no\"\u003ePROJECT\u003c/var\u003e/locations/\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e/instances?instanceId=\u003cvar translate=\"no\"\u003eINSTANCE_NAME\u003c/var\u003e\"\n\nTo turn it off, either set the property to false or omit the property, as\nlineage is turned off by default when you create a new instance.\n\n### Enable or disable Dataplex Universal Catalog data lineage in an existing instance\n\n### Console\n\n\nTo enable or disable Dataplex Universal Catalog data lineage in an existing instance in\nCloud Data Fusion, follow these steps:\n\n1. View the instance details:\n 1. In the Google Cloud console, go to the Cloud Data Fusion page.\n\n 2. Click **Instances** , and then click the instance's name to go to the\n **Instance details** page.\n\n [Go to Instances](https://console.cloud.google.com/data-fusion/locations/-/instances)\n2. In the **Dataplex data lineage integration** field, click **Edit**.\n3. Enable or disable Dataplex Universal Catalog data lineage, and then click **Save**.\n\n### REST API\n\nTo enable Dataplex Universal Catalog data lineage in an existing instance in\nCloud Data Fusion, set the `dataplex_data_lineage_integration_enabled`\nproperty to `true` and include the `updateMask` parameter value: \n\n echo '{ \"description\": \"CDAPinstance\", \"dataplex_data_lineage_integration_enabled\": \"true\"}' | curl -X POST \\\n -H \"Authorization: Bearer $(gcloud auth print-access-token)\" \\\n -H \"Content-Type: application/json\" \\\n --data @- \\\n \"https://datafusion.googleapis.com/v1/projects/\u003cvar translate=\"no\"\u003ePROJECT\u003c/var\u003e/locations/\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e/instances?instanceId=\u003cvar translate=\"no\"\u003eINSTANCE_NAME\u003c/var\u003e?updateMask=dataplex_data_lineage_integration_enabled\"\n\nTo disable Dataplex Universal Catalog data lineage in an existing instance in\nCloud Data Fusion, set the `dataplex_data_lineage_integration_enabled`\nproperty to `false` and include the `updateMask` parameter value: \n\n echo '{ \"description\": \"CDAPinstance\", \"dataplex_data_lineage_integration_enabled\": \"false\"}' | curl -X POST \\\n -H \"Authorization: Bearer $(gcloud auth print-access-token)\" \\\n -H \"Content-Type: application/json\" \\\n --data @- \\\n \"https://datafusion.googleapis.com/v1/projects/\u003cvar translate=\"no\"\u003ePROJECT\u003c/var\u003e/locations/\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e/instances?instanceId=\u003cvar translate=\"no\"\u003eINSTANCE_NAME\u003c/var\u003e?updateMask=dataplex_data_lineage_integration_enabled\"\n\nView data lineage graphs\n------------------------\n\nTo view lineage graphs for entities across all Google Cloud services,\ndo the following:\n\n1. Go to your instance in Cloud Data Fusion and run a data pipeline\n that uses supported plugins.\n\n2. [View the lineage graphs on the Dataplex Universal Catalog page in the console](/dataplex/docs/use-lineage#view-lineage-graphs)\n and find the asset for which you want to view lineage information.\n\nLimitations\n-----------\n\nViewing lineage in Dataplex Universal Catalog has the following limitations:\n\n- The lineage in Dataplex Universal Catalog is only discoverable if there is a\n BigQuery entity connected to the supported plugins. For more\n information about when data lineage graphs are available, see\n [About data lineage](/dataplex/docs/about-data-lineage).\n\n- The Data Lineage API [doesn't support customer-managed encryption keys (CMEK)](/dataplex/docs/lineage-considerations#compliance).\n\n- Cloud Data Fusion doesn't support this feature in `me-central1` or\n `europe-west12` locations.\n\n- Review the\n [data lineage considerations](/dataplex/docs/lineage-considerations).\n\n| **Warning:** Dataplex Universal Catalog uses IP addresses to form a fully qualified name that uniquely identifies sources and sinks (such as a Database sink) to display lineage. If you must prevent sharing IP address or hostname information, don't enable Dataplex Universal Catalog data lineage integration.\n\nWhat's next\n-----------\n\n- Learn more about [data lineage](/dataplex/docs/about-data-lineage)."]]
