Looker

Euno's Looker integration supports auto-discovery of the following Looker resources and sub-resources:

Setting up The Looker integration:

  1. Create a Looker API key to be used by Euno to access Looker's API

  2. Configure Euno's Looker integration

Setting up Euno's Looker Integration

Step 1: Create a Looker API key to be used by Euno to access Looker's API

Euno uses Looker API keys to access Looker's API and auto-discover Looker resources.

We recommend creating a dedicated API Key for Euno's Looker integration. To ensure that the API Key has the required permissions , create the API Key for a user with the Admin role. For more granular control over the permissions provided to the API Key, Follow the steps in Using a custom Looker Role, and come back here once a dedicated Euno user is created.

  1. Log in to Looker with a user with "Admin" role

  2. Go to "admin" found in the left sidebar

Looker: Admin Settings

  1. Scroll down to find "Users" in the left sidebar

Looker: Admin Settings - Users

  1. Click on a user to create the API key for. Make sure this user has the "Admin" role

Looker: Admin Settings - Users

  1. Find "API Keys" and click the button "Edit Keys" located next to it

Looker: Edit Keys

  1. Click "New API Key". You should now see the new key's Client ID and Client Secret. Make note of the two values (or leave the browser tab open). You'll need both values to configure Euno's Looker integration in the next stage.

Looker: New API Key

Step 2: Configure New Looker Source in Euno

Step 1: Access the Sources Page

  1. Go to the Sources page.

  2. Click on Add New Source and select Looker from the list of supported platforms.

Step 2: General Configuration

Asterik (*) means a mandatory field.

Configuration
Description

Name*

Enter a name for your Looker source (e.g., "Looker - Sales Data")

Host*

Enter the Looker host URL (e.g., https://<your-looker-domain>.cloud.looker.com).

Client ID*

Provide the Client ID from your Looker API credentials.

Client Secret*

Enter the Client Secret from your Looker API credentials.

Step 3: Scheduling Updates

  1. Enable the Schedule toggle.

  2. Choose from the following:

    1. Weekly: Specify the days and times for updates.

    2. Hourly: Enter an interval in hours (e.g., every 6 hours).

Step 4: Resource Cleanup

To keep your data relevant and free of outdated resources, Euno provides automatic resource cleanup options. These settings determine when a resource should be removed if it is no longer detected by a source integration. For a detailed explanation on Euno's cleanup strategies, see: Resource Sponsorship in Euno.

  • Immediate Cleanup: Remove resources not detected in the most recent successful source integration run.

  • No Cleanup: Keep all resources indefinitely, even if they are no longer detected.

Step 5: Advanced Settings (Optional)

Click on the 'Advanced' section to display these additional configurations.

Configuration
Description

LookML Project Includes

Specify LookML projects to include. This is a wildcard match, so, for example, if the pattern is mart*, then all projects starting with martwill be processed. Leave blank or set to *to process all LookML projects

LookML Model Includes

Specify LookML models to include. This is a wildcard match, so, for example, if the pattern is sales*, then all models starting with sales be processed. Leave blank or set to *to process all LookML models.

Crawl LookML Only

Enable this if you want to crawl LookML only.

Mapping

Euno will ingest looker resources using the connections defined in the application unless a mapping is added. In that case, the resource will be ingested using the mapped value of the target.

Mapping

Euno will ingest looker resources using the connections defined in the application unless a mapping is added. Each connection can be mapped to a target data source. This can be useful, for example, when Looker is connected to a copy of production database, and we want to trace lineage to the original instead of the copy. If mapping is configured, the resource will be ingested using the mapped value of the target.

Configuration
Description

connection_name

The name of the connection as it appears in your Looker instance. This should match exactly what you see in Looker's connection settings, for example: snowflake_prod, bigquery_analytics, postgres_main

host

The target database server hostname to map to.

Examples:

  • Snowflake: mycompany.snowflakecomputing.com

  • BigQuery: bigquery.googleapis.com

  • PostgreSQL: db.example.com

  • Redshift: redshift-cluster.amazonaws.com

port (optional)

The target database port number. Defaults to 0 if not specified.

Examples:

  • PostgreSQL: 5432

  • MySQL: 3306

  • SQL Server: 1433

  • Snowflake: 443

database

The specific database name that contains your tables.

Examples:

  • Snowflake: ANALYTICS_DB, PROD_DW

  • BigQuery: my-project-id (the Google Cloud project ID)

  • PostgreSQL: production, analytics

dialect

The database type, i.e. Snowflake, BigQuery etc.

db_schema (optional)

The default schema within the database. Leave empty if not applicable.

aws_account (optional)

AWS account ID, required only for Athena connections.

Step 6: Save Configuration

Click the Save button to complete the setup.

If the integration is not successful, refer to Looker Integration Troubleshooting Guide

Previousdbt CloudNextUsing a custom Looker role

Last updated