Troubleshooting Looker connectivity

What are the known limitations of the Looker connector?

Following are the known limitations of the Looker connector:

  • Cross-project lineage is currently not supported for Looker assets. For example, if an explore includes a view from an imported project, lineage will not be generated in Atlan.
  • Persistent derived tables (PDTs) and Liquid parameterized tables are currently not supported for Looker views.
  • Fields and field-level lineage for looks, tiles, and dashboards are currently not supported in Atlan.

What is the timeframe for calculating sourceViewCount for Looks and dashboards?

The Atlan property sourceViewCount is based on the source property view_count:

  • view_count displays a total count of views for a Look or dashboard since creation of the asset.
  • Atlan currently does not support a timestamp for views due to limitations of the Looker APIs.

Why do I get a 403 forbidden error after clicking the test authentication button?

If you receive a 403 forbidden error when testing authentication, confirm the following:

  • Ensure you have provided the API host URL for Looker. (This may be different from the Looker instance URL.)
  • Ensure your Looker instance is running on port 433. If not, add the port number explicitly to the URL.
  • Ensure your client ID and secret are correct.
  • Ensure you have allowlisted the Atlan IP in your Looker instance. (To get details of your Atlan IP, please raise a support ticket.)

Once you have confirmed or corrected these, retry the authentication.

Why is lineage missing from an Explore to a Tile or Look?

If lineage is missing from an Explore to a Tile or Look, this is usually because you have not given content access to a folder.

Once you have corrected the access in Looker, rerun the Looker crawler in Atlan.

Why is lineage missing between data sources and Looker assets?

If lineage is missing from data sources to Looker assets, confirm the following:

  • Ensure you have given the see_sql permission to the role for which you generated the API3 credentials.
  • Ensure you have crawled the data sources' assets in Atlan, before crawling the Looker assets.

Once you have confirmed or corrected these, rerun the Looker crawler in Atlan.

Why is lineage missing from tables to models?

If lineage is missing from tables to models, this is usually because you have excluded a folder or project that contains these lineage details.

Once you have corrected this in the crawler configuration, rerun the Looker crawler in Atlan.

Why is relationship missing between models and queries, or Looks and models?

If a relationship is missing between some Looker assets, this is usually because you have excluded a project that contains these details.

Once you have corrected this in the crawler configuration, rerun the Looker crawler in Atlan.

Can I use deploy keys for setup?

Deploy keys only grant access to a single repository. For more complex projects where Looker connects to multiple repositories, Atlan does not support using deploy keys.

Why am I seeing a failed to clone project error?

Exception: ('Failed to clone project %s. Git URL: %s', '<project>', '<git_url>')

If you encounter the above error, please ensure that the SSH key you’re using has access to all the GitHub project files included for crawling. Refer to the Looker setup documentation to learn more.

Related articles

Was this article helpful?
1 out of 1 found this helpful