Skip to main content
This section provides guides and references to use the Collibra connector. Configure and schedule Collibra metadata workflow from the Collate UI:

Requirements

To connect to Collibra, you will need:
  • Username: A user account with privileges to read all metadata in Collibra
  • Password: The password for the user account
  • Host and Port: The URL of your Collibra instance (e.g., https://<your-instance>.collibra.com)

Data Mapping and Assumptions

Following entities are supported and will be mapped to the Collate entities as shown below.
  • Collibra glossaries will be mapped to Collate glossaries with their terms and relationships preserved.
  • When Enable Asset Enrichment is enabled, the connector will match Collibra assets to existing Collate entities and enrich them with descriptions, tags, and ownership information from Collibra without creating new assets.
  • Use the glossaryFilterPattern to include or exclude specific glossaries based on their names.
  • Use the domainFilterPattern to include or exclude specific domains and communities based on their names.

Metadata Ingestion

To ingest metadata from Collibra, you need to create a service connection. The service connects Collibra with Collate. Once you create a service, Collate automatically starts ingesting metadata.

Step 1: Add New Service

  1. In the left navigation, click Connections.
  2. On the Connections page, click Add New Service.
Add New Service

Step 2: Select a Service and Connector

From the service type dropdown, select Metadata Services, then click the Collibra connector tile. Select Service

Step 3: Add Service Name and Description

  • Enter a unique, descriptive Service Name. Collate identifies services by their service name. Enter a name that distinguishes this deployment from other Collibra services you are ingesting metadata from.
  • Optional: Enter a Description for the service.
Add New Service Name
Note: The service name cannot be changed after it is set.

Step 4: Configure Connection Options

Specify where ingestion runs, provide your source credentials, and verify the connection.

Select Ingestion Runner

Select an Ingestion Runner: the runner where the ingestion pipeline will execute. Add Name and Select Ingestion Runner

Enter Connection Details

Enter the connection details for Collibra. The right-hand panel in the UI displays inline help for each field. Configure Service Connection
  • hostPort: Host and port of the Collibra instance.
  • username: Username to connect to Collibra. This user should have privileges to read all the metadata in Collibra.
  • password: Password for the Collibra user account.
  • glossaryFilterPattern: Regex pattern to include or exclude glossaries based on their names. Use this to control which glossaries are ingested. Examples:
    • Include specific glossaries: ^(BusinessGlossary|DataGlossary)$
    • Exclude test glossaries: ^(?!.*test).*$
  • domainFilterPattern: Regex pattern to include or exclude domains and communities based on their names. Examples:
    • Include specific domains: ^(Finance|Sales)$
    • Exclude archived domains: ^(?!.*archived).*$
  • enableEnrichment: When enabled, the connector will enrich existing Collate assets with metadata from Collibra (descriptions, tags, owners) by matching Collibra assets to Collate entities. This will not create new assets, only update existing ones. By default, this is set to false.

Advanced Configuration

Database Services have an Advanced Configuration section, where you can pass extra arguments to the connector and, if needed, change the connection Scheme. This would only be required to handle advanced connectivity scenarios or customizations.
  • Connection Options (Optional): Enter the details for any additional connection options that can be sent to database during the connection. These details must be added as Key-Value pairs.
  • Connection Arguments (Optional): Enter the details for any additional connection arguments such as security or protocol configs that can be sent during the connection. These details must be added as Key-Value pairs.
Tip: When using a Hybrid Ingestion Runner, any sensitive credential fields—such as passwords, API keys, or private keys—must reference secrets using the following format:
This applies only to fields marked as secrets in the connection form (these typically mask input and show a visibility toggle icon). For more information about managing secrets in hybrid setups, see the Hybrid Ingestion Runner Secret Management Guide

Test Connection

Once the credentials have been added, click on Test Connection and Save the changes. Test Connection

Step 5: Configure Ingestion Options

In the What to Ingest step, configure the metadata ingestion pipeline settings, then click Create & Deploy. Collate creates the service connection and automatically triggers the first metadata ingestion run. In AI 2.0, ingestion is managed by the Auto Pilot app — you do not need to schedule a separate pipeline. After deployment, you can monitor the ingestion status by navigating to Connections, selecting your service, and viewing the ingestion pipeline.
Tip: If AutoPilot is enabled, usage tracking, data lineage, and other downstream workflows start automatically after the first metadata ingestion completes.

Configure Metadata Agent and Schedule Ingestion

The Metadata Agent extracts databases, schemas, tables, stored procedures, and other structural metadata from your connected data source and keeps your Collate catalog in sync. It powers discovery, lineage, and governance across your data assets. When you click Create & Deploy, Collate automatically deploys a Metadata Agent for this service and triggers the first ingestion run. View its status and run history from the Agents tab on the service detail page. To configure the additional Metadata Agent and schedule ingestion, follow these steps:
  1. In the left navigation, click Connections and select your service.
  2. Click the Agents tab.
  3. Click Add Agent and select Metadata from the dropdown. Add Metadata Agent For some services, the dropdown is not available and clicking Add Agent takes you directly to the agent configuration page.
  4. On the Configure Ingestion page, do the following and click Next.
    • Name this Ingestion: Enter a unique recognizable name for this ingestion pipeline. Name this Ingestion
    • Agent Setup: Configure the core parameters for this agent. The following fields are available: Agent Setup
    • Filter Patterns: Apply include or exclude rules to scope which databases, schemas, tables, and stored procedures this agent ingests. These follow the same filter options described in Step 5. Filter Patterns
    • Scope & Behaviour: Control what metadata to include and how to handle deletions. Toggle each option on or off based on your needs: Scope & Behaviour
  5. On the Schedule Interval page, set when the agent runs:
    • Schedule: Choose a preset interval (Hourly, Daily, Weekly, Monthly) or enter a custom cron expression.
    • On-Demand: No automatic schedule; trigger the agent manually when needed.
    Schedule Interval
  6. Click Add to deploy the agent.

Troubleshooting

Collibra Troubleshooting

Learn more about how to troubleshoot common Collibra connector issues and resolve configuration or ingestion errors.