Link Search Menu Expand Document

Integrate Soda Cloud with Alation

Integrate Soda with Alation to access details about the quality of your data from within the data catalog.

  • Run data quality checks using Soda and visualize quality metrics and rules within the context of a data source, dataset, or column in Alation.
  • Use Soda Cloud to flag poor-quality data in lineage diagrams and during live querying.
  • Give your Alation users the confidence of knowing that the data they are using is sound.



  • You have a Soda Cloud account with Admin permissions, connected to an instance of Soda SQL.
  • You have configured Soda SQL to access the data source on which you want to run quality checks.
  • You have completed at least one Soda scan to validate that the data source’s datasets appear in Soda Cloud as expected.
  • You have an Alation account with the privileges necessary to allow you to add a data source, create custom fields, and customize templates.
  • You have a git repository in which to store the integration project files.

Set up the integration

  1. Sign into your Soda Cloud account and confirm that you see the datasets you expect to see in the data source you wish to test for quality.
  2. To connect your Soda Cloud account to your Alation Service Account, create an .env file in your integration project in your git repo and include details according to the example below. To obtain the values for your Soda API keys, refer to the Connect to Soda Cloud documentation.
    ALATION_USER=<your username for your Alation account>
    ALATION_PASSWORD=<your password for your Alation account>
    SODA_API_KEY_ID=<your Soda Cloud pubic key>
    SODA_API_KEY_SECRET=<your Soda Cloud private key>
  3. To sync a data source and schema in the Alation catalog to a data source in Soda Cloud, you must map it from Soda Cloud to Alation. Create a .datasource-mapping.yaml file in your integration project and populate it with mapping data according to the following example. The table below describes where to retrieve the values for each field.
    - name: Cars
     datasource_id: 2d33bf0a-9a1c-4c4b-b148-b5af318761b3
     # optional dataset_mapping   soda: catalog
        Cars_data: Cars
     type: "alation"
     datasource_id: "31"
     datasource_container_name: "soda"
    - name: Soda Demo
     datasource_id: 8505cbbd-d8b3-48a4-bad4-cfb0bec4c02f
     type: "alation"
     datasource_id: "37"
     datasource_container_name: "public"

Field Retrieve value from
name A name you choose as an identifier for an integration between Soda Cloud and a data catalog.
The data source information panel in Soda Cloud.
(Optional) When you run the integration, Soda automatically maps all of the datasets between data sources. However, if the names of the datasets differ in the tools you can use this property to manually map datasets between tools.
The name of the cataloging software; in this case, “alation”.
Rhe URL on the data source page in the Alation catalog; see image below.
Effectively the schema of the data source, retrieve this value from the data source page in the Alation catalog under the subheading Schemas; see image below.

Retrieve the Alation datasource_id from the URL

Retrieve the Alation datasource_container_name (schema) from the data source page

Customize the catalog

  1. Create custom fields in Alation that reference information that Soda Cloud pushes to the catalog. These are the fields the catalog users will see that will display Soda Cloud data quality details.
    In your Alation account, navigate to Settings > Catalog Admin > Customize Catalog. In the Custom Fields tab, create the following fields:
    • Under the Pickers heading, create a field for “Has DQ” with Options “True” and “False”.
    • Under the Dates heading, create a field for “Profile - Last Run”.
    • Under the Rich Texts heading, create the following fields:
      • “Soda DQ Overview”
      • “Soda Data Quality Rules”
      • “Data Quality Metrics”
  2. Add each new custom field to a Custom Template in Alation. In Customize Catalog, in the Custom Templates tab, select the Table template, then click Insert… to add a custom field to the template:
    • “Soda DQ Overview”
  3. In the Table template, click Insert… to add a Grouping of Custom Fields. Label the grouping “Data Quality Info”, then Insert… two custom fields:
    • “Has DQ”
    • “Profile - Last Run”
  4. In the Column template, click Insert… to add a custom field to the template:
    • “Has DQ”
  5. In the Column template, click Insert… to add a Grouping of Custom Fields. Label the grouping “Soda Data Profile Information”, then Insert… two custom fields:
    • Data Quality Metrics
    • Soda Data Quality Rules

Run the integration

Contact Soda Support directly to acquire the assets and instructions to run the integration and view Soda Cloud details in your Alation catalog.

Use the integration

Access Soda Cloud to create monitors that execute tests against datasets in your data source each time you run a Soda scan manually, or orchestrate a scan using a data pipeline tool such as Airflow. Soda Cloud pushes data quality scan results to the corresponding data source in Alation so that users can review data quality information from within the catalog.

In Alation, beyond reviewing data quality information for the data source, users can access the Joins and Lineage tabs of individual datasets to examine details and investigate the source of any data quality issues.

Open in Soda

In a dataset page in Alation, in the Overview tab, users have the opportunity to click links to directly access Soda Cloud to scrutinize data quality details; see image below.

  • Under the Soda DQ Overview heading in Alation, click Open in Soda to access the dataset page in Soda Cloud.
  • Under the Dataset Level Monitors heading in Alation, click the title of any monitor to access the monitor info page in Soda Cloud.


Go further

Last modified on 18-Jan-22

Was this documentation helpful?
Share feedback in the #soda-docs channel in the Soda community on Slack.

Help improve our docs!

  • Request a docs change.
  • Edit this page in our GitHub repo.