Looker
Add a Looker connection to your decube so that you can discover the lineage of your assets from source to dashboards.
Supported Capabilities
Metadata Extraction
✅
Metadata Types Collected
Schema, Virtual Table, Virtual Column, Chart, Dashboard
Data Profiling
❌
Data Preview
❌
Data Quality
❌
Configurable Collection
❌
External Table
❌
View Table
❌
Stored Procedure
❌
Supported Lineage Mapping
Looker supports lineage mapping from the following sources:
Upstream Connectors: mysql, singlestore, postgresql, redshift, snowflake, azure_server, sql_server, synapse, bigquery, databricks, oracle
Connection Requirements
Minimum Requirement
From our Looker account, we will need the following information:
Looker instance URL
Client ID
Client secret
To ensure proper functionality of the ingestion process, it is imperative to grant the following permissions.
access_data
develop
explore
manage_project_models
manage_project_connections
see_lookml
see_lookml_dashboards
see_looks
see_queries
see_sql
For more info on how to create permission sets. Please refer to this looker documentation.
Additional configuration for lineage
To build out the lineage, we will need to know the data sources that you've referenced within your Looker definitions. You can do a one-time mapping for the sources by using the Additional Configuration in the Data Sources page. Check out how below.
Additional configurationsFor Looker, we match your Views in Looker to decube Tables by the View name. If you have customized View names, please refer to the next section below.
Override View Mapping (Optional)
If you have a customized View name, it is recommended to use the View Mapping Override to add the name of the Table in decube so that our metadata scanner can build the lineage automatically to your Looker view.
Last updated