Common Looker connectivity issues

Have more questions? Submit a request

403 Forbidden error when clicking Test Authentication

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

  1. Ensure you have provided the API host URL for Looker. (This may be different from the Looker instance URL.)
  2. Ensure your Looker instance is running on port 433. If not, add the port number explicitly to the URL.
  3. Ensure your client ID and client secret are correct.
  4. 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.

Missing lineage from an Explore to a Tile or Look

If you are missing lineage 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, re-run the Looker crawler in Atlan.

Missing lineage between data sources and Looker assets

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

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

Once you have confirmed or corrected these, re-run the Looker crawler in Atlan.

Missing lineage from tables to models

If you are missing lineage 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, re-run the Looker crawler in Atlan.

Missing relationship between models and queries, or Looks and models

If you are missing a relationship 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, re-run the Looker crawler in Atlan.

Related articles

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