Collibra

Integrate Collibra with Acceldata Data Observability Cloud (ADOC) to bridge the gap between data governance and data observability. This integration allows Collibra users to access Acceldata's data quality and reliability insights directly within the Collibra platform, ensuring unified visibility and trust in enterprise data assets.

Overview

The Collibra integration enables governance users to assess data reliability and quality without leaving the Collibra environment.

By connecting Collibra as a data catalog source in ADOC, organizations can map existing ADOC data sources (such as Snowflake or Hive) to corresponding Collibra assets. For this mapping to work, the underlying database must first be ingested into Collibra's catalog through a Collibra Edge connection, and the corresponding ADOC data source must point to that same database.

When reliability policies execute on a mapped ADOC data source, the execution results — including data quality metrics and reliability scores — are automatically published to the mapped asset in Collibra. If a mapped Collibra asset exists, results are displayed on that asset's Collibra Overview page; if not, they are ignored.

This integration delivers a governance-grade, automated publishing workflow, ensuring that data reliability insights from ADOC remain continuously synchronized with Collibra's data catalog.

Supported Authentication Methods

Key Capabilities

• Unified Governance and Observability: View Acceldata data quality and reliability insights directly within Collibra.
• Automated Publishing Workflow: Reliability scores and data quality metrics automatically sync after each policy run in ADOC.
• Always Up-to-Date Metrics: No manual export or synchronization required — data is refreshed automatically.
• Secure Integration: Supports both Basic and OAuth authentication modes for secure, enterprise-ready connectivity.
• Streamlined Experience: Collibra users can assess asset health without switching between platforms. Users are provided with a link to navigate back to the ADOC platform and view execution results.

Prerequisites

Before configuring the integration, ensure that:

• You have valid Collibra credentials (Username/Password, or OAuth Client ID, Client Secret, and Token URL).
• You have access to a healthy Collibra Edge site, with permissions to create connections and assign capabilities on it.
• You have the JDBC driver for your data source (for example, the Snowflake JDBC driver), and permissions in Collibra Catalog to register a data source and run schema synchronization.
• The Collibra REST API is accessible from your ADOC Control Plane network. The Control Plane handles configuration, API communication, and metadata publishing to Collibra.
• The database you want observability results for does not need to already be in Collibra before you start — Part A below ingests it. It does need to be reachable from your Collibra Edge site and from ADOC using the same connection details (host, database, and schema).

Part A: Prepare the Data Source in Collibra

Acceldata publishes reliability results to a Collibra asset only if that asset already exists in Collibra's catalog. Complete this part first, using the same database you plan to connect in ADOC.

Step 1: Create an Edge Connection

• In Collibra, select the App launcher icon in the top header menu and navigate to Settings.
• From the Settings left menu, click Edge, and open your Edge site by clicking its name.
• On the Connections tab, click Add Connection.
• Set the Connection type to Generic JDBC connection.
• Give the connection a Name you can recognize later (for example, matching your database name), and an optional Description.
• Provide:
  • Driver class name: the fully qualified name of the JDBC driver for your database type (for example, net.snowflake.client.jdbc.SnowflakeDriver for Snowflake).
  • Driver JAR: the JDBC driver JAR file for your database (for example, snowflake-jdbc-3.22.0.jar).
  • Connection string: the JDBC connection string for your database (for example, jdbc:snowflake://<account>.snowflakecomputing.com for Snowflake).
• Under Property, add a row for each connection property your database requires. For each row, set:
  • Type: Text.
  • Value type: Secret for credentials such as a password (Collibra encrypts these on Edge and does not display them again), or Plaintext for non-sensitive values.
  • Name: the property name (for example, password, role, warehouse, or user for Snowflake).
  • Value: the property value.
• Click Test connection to confirm Edge can reach the database, then save the connection.

Step 2: Add Capabilities

Capabilities are configured at the Edge site level, not on the connection itself. Add two capabilities that both reference the connection you created in Step 1: one for ingestion and one for sampling.

• On your Edge site, go to the Capabilities tab.
• Click Add Capability and create a capability with:
  • Capability type: Catalog JDBC Ingestion.
  • Name: a name you can recognize later (for example, <connection-name>-ingestion).
  • JDBC Connection: the connection you created in Step 1.
  • (Deprecated) JDBC datasource type: GENERIC, unless your database has a dedicated type available.
  • Leave Supports schemas, Other Settings, Debug, and Log level at their defaults unless you have a specific reason to change them.
• Repeat step 2 to add a second capability with Capability type set to Catalog JDBC Sampling, pointing to the same JDBC Connection.

Step 3: Register the Data Source in Catalog

• In Collibra, select the App launcher icon in the top header menu, then go to Catalog > Integrations.
• On the Data source registration tab, find the row for the Edge connection you created in Step 1, and click Register in that row's Action column. The Register a Data Source dialog opens with your Edge Site and Edge Connection already filled in based on the row you selected.
• Provide:
  • Community: the Collibra community this data source belongs to.
  • System: the system asset for this data source.
  • Owner: the user or group responsible for this data source.
  • Responsibility role: the role that Owner has on this data source. Defaults to Owner.
  • Database: the specific database to register.
  • Description (optional).
• Click Register.

Step 4: Synchronize the Schema

• Open the database asset you registered in Step 3 (search for it, or navigate from Catalog > Data sources).
• Go to the Configuration tab, then the Metadata Synchronization sub-tab.
• Under Available Schemas, select the schema you want to synchronize (for example, PUBLIC). Each schema shows its own status, such as Not Synchronized.
• Click Add Rule to define which tables in that schema to bring into Collibra:
  • Include Tables: a pattern matching the tables to include. Use * to include all tables in the schema.
  • Exclude Tables (optional): a pattern matching tables to leave out, even if they match Include Tables.
  • Target Domain: where the resulting table assets are created in Collibra. Defaults to Automatically Created for Schema.
  • Options (optional): Exclude Database Views, Include Source Tags, Include Semantic Views, Include Data Usage Statistics.

You can add more than one rule per schema, for example to include most tables but exclude a pattern, or to apply different options to different table sets.

• Click Save, then click Synchronize Schemas with Rules and wait for it to complete.
• Confirm the sync worked by searching Collibra for one of the tables and verifying it now appears as an asset in the catalog. The schema's status changes from Not Synchronized to reflect the sync result.

Once this part is complete, proceed to Part B to connect ADOC and Collibra.

Part B: Add Collibra as a Data Source in ADOC

Follow these steps to register Collibra in ADOC:

• Navigate to the left main navigation menu, click Control Center > Integrations.
• From the Integrations page, click Add Data Source.
• Select Collibra from the list of available connectors.
• In the Basic Details page, enter a Data Source Name and provide an optional Description.
• Click Next to open the Connection Details page.
• Provide the following:
  • Collibra Base URL: Enter the Collibra server or cloud URL. Example: https://myorg.collibra.com
  • Authentication method:
    • If OAuth is enabled: Provide the OAuth token URL, Client ID, and Client Secret.
    • If OAuth is disabled: Provide Username and Password.
• Click Test Connection to validate access.
  • If successful, click Next to continue.
  • If unsuccessful, verify your credentials or network access.
• On the Observability Setup page, map your Collibra data source to your ADOC data source:
  • Select one or more ADOC data sources (for example, the Snowflake data source pointing at the database you prepared in Part A).
  • Select the corresponding Collibra data source to link them.
  • Click Add Mapping to include additional pairs.
• Click Submit to complete registration.

Once configured, ADOC automatically publishes reliability scores and data quality metrics to Collibra after each policy execution.

Part C: View Acceldata Attributes in Collibra

Once an asset is mapped between ADOC and Collibra (Part B) and a policy has run against it in ADOC, no manual layout configuration is needed to see the results. Open the asset in Collibra and its Overview tab shows an Acceldata Data Quality Score section with two attributes, populated automatically after each policy execution:

• Acceldata Reliability Score: The overall reliability score for the asset, as a number (for example, 100).
• Acceldata Data Quality Report: A View this asset in Acceldata link back to the matching asset in ADOC, followed by a rendered summary report. The report includes the overall reliability score as a percentage, and a component scores table breaking that score down by policy type:
  • Data Quality Score
  • Reconciliation Score
  • Data Drift Score
  • Data Cadence Score
  • Schema Drift Score
  • Profile Anomaly Score
• A component shows a score only if a policy of that type has run against the asset; otherwise it shows N/A. The report also shows when it was generated and when it was last updated.

These are the only two Acceldata attributes populated on an asset. The component scores, the generated-by line, and the last-updated timestamp are all part of the single Acceldata Data Quality Report attribute's content — they are not separate Collibra attributes.

• In Collibra, search for or navigate to the asset that is mapped to ADOC.
• Open the asset and stay on the Overview tab (or the Summary tab, depending on your Collibra version).
• Under Acceldata Data Quality Score, review the Acceldata Reliability Score and the Acceldata Data Quality Report.
• Select View this asset in Acceldata to open the same asset's detailed results in ADOC.

If reconciliation policies involve two data sources (for example, left and right datasets), and both are registered in Collibra, Acceldata publishes reliability results for each participating asset, and both assets' Overview tabs are populated independently.

Part D: Verify the Integration

• In ADOC, create a Data Quality policy against an asset in the data source you mapped in Part B.
• Run the policy and wait for it to complete successfully.
• In Collibra, search for the same asset.
• Confirm that:
  • The Reliability Score and Data Quality Report attributes are populated.
  • Selecting View this asset in Acceldata opens the matching asset in ADOC.

Automated Data Publishing Workflow

After successful configuration:

• ADOC automatically sends data quality and reliability results to Collibra following each policy execution.
• Collibra's data catalog reflects updated reliability scores, freshness metrics, and rule outcomes.
• Governance users can review these insights without leaving Collibra, ensuring both compliance and trust.

No manual export or synchronization is required. Updates occur automatically after every successful ADOC policy run.

Next Steps

• Verify successful data publishing in Collibra's asset details view.
• Schedule regular policy runs in ADOC to keep insights up to date.
• Enable notifications in Collibra for key updates or quality threshold breaches.