Overview Looker integration steps

The Looker integration enables you to harvest Looker metadata and create new Looker assets in Data Catalog. Collibra analyzes and processes the Looker metadata and presents it as specific asset types, retaining their original names.

Tip To ingest Looker metadata in Data Catalog, you need to run the lineage harvester. The Looker ingestion workflow explains the role of the lineage harvester in the Looker ingestion process.

Steps

The table below shows the steps and prerequisites required to integrate Looker in Data Catalog.

Important In the global assignment of each asset type included in the Looker operating model, ensure that none of the characteristics that are in the operating model have a maximum cardinality of “0”. If the maximum cardinality is set to “0” for any such characteristics, ingestion will fail.

Step

What?

Description

Prerequisites

1

Set up Looker authentication.

Before you start the Looker integration, you have to enable Collibra to access your Looker metadata.
  • You have a Looker subscription.

2

Create a new domain.

Before you can ingest Looker metadata, you have to create a new domain or choose an existing domain to store the new Looker assets.
  • You have a resource role with the following resource permissions:
    • Domain: Add
3

Download and install

the lineage harvester and prepare a configuration file with Looker connection properties.

You use the lineage harvester to collect metadata from Looker and upload it to Collibra, where the metadata is scanned, processed and analyzed.

When you download the lineage harvester, you can access the configuration file. You prepare a configuration file with Looker connection properties.

Note You need the lineage harvester 1.3.0 or newer to ingest Looker metadata into Data Catalog
  • Collibra Data Intelligence Cloud.
  • A global role with the following global permissions:
    • Catalog, for example Catalog Author
    • Data Stewardship Manager
    • Manage all resources
    • System administration
    • Technical lineage
  • A resource role with the following resource permission on the community level in which you created the BI Data Catalog domain:
    • Asset: add
    • Attribute: add
    • Domain: add
    • Attachment: add

4

Run the lineage harvester

You run the lineage harvester to start the ingestion process.

Collibra creates new Looker assets in Data Catalog and imports relations between these assets. It also creates a technical lineage for Looker Look assets.

You can create a lineage harvester job to schedule automatic Looker ingestion and synchronization.
  • You have Collibra Data Intelligence Cloud 2020.12 or newer.
  • Your environment meets the system requirements to run the lineage harvester.
  • You have added Firewall rules so that the lineage harvester can connect to Collibra Data Lineage service instances with the following IP addresses:
    • 15.222.200.199 (techlin-aws-ca.collibra.com)
    • 18.198.89.106 (techlin-aws-eu.collibra.com)
    • 13.228.38.245 (techlin-aws-sg.collibra.com)
    • 54.242.194.190 (techlin-aws-us.collibra.com)
    • 51.105.241.132 (techlin-azure-eu.collibra.com)
    • 20.102.44.39 (techlin-azure-us.collibra.com)
    • 35.197.182.41 (techlin-gcp-au.collibra.com)
    • 34.152.20.240 (techlin-gcp-ca.collibra.com)
    • 35.205.146.124 (techlin-gcp-eu.collibra.com)
    • 34.87.122.60 (techlin-gcp-sg.collibra.com)
    • 35.234.130.150 (techlin-gcp-uk.collibra.com)
    • 34.73.33.120 (techlin-gcp-us.collibra.com)
4 View the Looker assets and technical lineage

After the Looker metadata is ingested in Data Catalog, you can go to the domain where you ingested Looker and see the list of ingested Looker assets.

You can go to a Looker Look asset page and click the Technical lineage lineage tab to view the technical lineage.

Warning When you run the lineage harvester, Collibra Data Lineage creates all Looker assets in the specified domain (or domains) in Collibra. We highly recommend that you do not move these assets to other domains. If you move assets to other domains, they will be deleted and recreated in the initial Data Catalog BI domain (or domains) when you synchronize Looker. As a consequence, all manually added data of those assets is lost.