Skip to main content
Atlan stores tables, views, columns, and lineage as assets in its data catalog. This integration brings Validio’s data quality metrics directly into Atlan’s collaborative workspace. View quality scores, incident history, and utilization data alongside your assets.
An Atlan asset page showing Validio quality score, incident counts, and validation coverage fields

Example of Validio metric information viewed in Atlan

Validio sends the following aggregated metrics to Atlan: The data quality score sent to Atlan is a snapshot of the most recent poll, so it can differ from the data quality score shown in Validio. The Atlan score uses only each validator’s latest result and counts every incident regardless of status, while the score in Validio covers a selected time range and excludes resolved and false-positive incidents.

​
Prerequisites for integrating with Atlan

To connect Validio to your Atlan instance, you will need:
  • The URL to your Atlan instance and an Atlan API token to create the credential in Validio.

​
Add a credential for Atlan

To add an Atlan credential in Validio,
  1. Navigate to Credentials, and click + New credential.
  2. Under Namespace, select a namespace to define where resources will be created and who can access it.
  3. Under Credential Type, select Atlan Credential.
  4. Fill in the Configuration parameters for the credential. For more information, see Atlan Credential Parameters.
  5. (Optional) Click Test credential to validate that Validio can successfully access the Atlan account. If validation fails, check that you provided the correct parameter values.
  6. Click Create credential.

​
Atlan credential parameters

​
Asset mapping between Validio and Atlan

The following describes how assets are mapped between Validio and Atlan:
  • Atlan will discover assets for each connection or credential. If you add identical connections twice, Atlan will discover two identical assets. Validio will deduplicate assets. If two Validio credentials discover the same asset, Validio treats them as one asset.
  • When mapping assets to Atlan, Validio accounts for the type, catalog, schema, and table—so, there cannot be duplicates between different warehouses, such as Snowflake and Postgres. If one Validio asset resolves to multiple Atlan assets, all Atlan assets will be updated based on the assumption that the assets are the same but originate from different workflows or connections.
Because you can add multiple sources to one asset in Validio, a single source is not always a single asset. Any aggregation on the asset-level (such as “Number of incidents” or “Has freshness”) means that the incident can come from any amount of sources, and it only requires at least one of the sources to have a freshness validator, not all of them.