Built-In Lineage Scanner

This guide is intended for admin users. To make sure you have the necessary permissions to run the scanner, see Lineage Permissions.

To retrieve lineage metadata using Ataccama built-in lineage scanner, you first need to create a scan plan and then execute it. Once the plan finishes successfully, your next step is to import lineage metadata to ONE.

Prerequisites

You are using the built-in Ataccama lineage scanner.
You have a scan plan you want to use. A scan plan is a valid JSON file whose structure depends on the source technology.

For detailed instructions about what your scan plan should contain, see the relevant guide depending on your source technology in Configuration by technology section of the documentation.

Create scan plan

To add a new scan plan to ONE:

Go to Knowledge Catalog > Scan Plans.
Select Create.
Provide a name for the scan and paste the JSON file as instructed. The file must be in valid JSON format.
To provide missing secrets, select Identify secrets. If there is a secret with no value provided, enter the value for the secret.

See Configure scan plan secrets to learn how to safely handle sensitive information in plans. If you’re using Azure Key Vault secrets, see Configure Azure Key Vault.
Select Validate & Save to check the file syntax again and save the plan. Alternatively, if you are confident your scan data is in valid JSON format, select Save instead.

You can now continue with step Run lineage scan.

In case you need to modify your scan plan, you can do so by opening the three dots menu of the scan from the Scan Plans screen and selecting Edit scan plan.

Configure scan plan secrets

We recommend encrypting any sensitive information such as passwords, secrets, and other credentials information. For this purpose, you can use secret placeholders that ensure actual values are safely stored in the encrypted form in the service.

The syntax for secret placeholders is as follows:

"@@ref:ata:[<secret-name>]"

For example: "clientSecret" : "@@ref:ata:[powerbi.client.secret]".

The <secret-name> is a unique identifier of the secret across all scan plans. The same secret can therefore be used in multiple scan plans.

Configure Azure Key Vault

If your scan plan uses an Azure Key Vault for storing secrets (@@ref:akv:), configure the connection to Azure Key Vault before running the plan.

On the Scan Plans screen, select the key icon (next to Create scan plan option).
Fill in the following information:
- URL: The full URL to your Azure Key Vault instance.
  
  Available in the Azure Portal under your Key Vault > Overview > Vault URI.
- Client ID: The application (client) ID of the Azure AD Service Principal (or managed identity) you’re using to authenticate.
  
  Found in *Azure Portal > Azure Active Directory > App registrations > [your app] > Overview.
- Client secret: The password or secret associated with the client ID.
- Tenant ID: The Azure Active Directory tenant ID that your app and Key Vault belong to.
Test the connection to verify the Azure Key Vault has been successfully configured. If the connection fails, review your settings and try again.
Save your changes. You can now run your lineage scan.

To edit or delete the configured Azure Key Vault, select the key icon again.

Run lineage scan

Once you have a scan plan ready, you can now run it to retrieve lineage metadata from your source.

On the Scan Plans screen, open the three dots menu of the plan you want to use and select Run lineage scan. This starts the scan and the scan status changes to Running.

Once the scan finishes, the scan status is updated automatically so you don’t need to refresh the page.

If the scan successfully finished, you can now import the scan results to ONE. See Next steps.

Troubleshooting the scan

If the scan finished with en error, download the scan debug archive and examine its content.

To access the debug archive, on the Scan Plans screen, open the three dots menu of the plan and select Download debug archive.

Next steps

Once you generate the lineage file, it needs to be uploaded to Ataccama ONE.

Was this page useful?