Troubleshooting Looker integration

"Invalid Looker Credential" when trying to connect Looker

To troubleshoot this issue, follow the steps:

1. Verify you correctly typed the Client ID and Client Secret in the "Configure Looker Integration" pop-up window.

2. If you're using IP whitelisting on your Looker instance, make sure Euno's public IP address is one of the rules in the whitelist. Follow Looker's guide here. Euno's public IP address is 35.224.29.172. Add a rule with:

   • Type: IP Address

   • Value: 35.224.29.172

3. Confirm the API key user has permission to query Looker's system__activity model (required during source validation). The Admin role satisfies this requirement; for custom roles, include the see_system_activity permission. See Using a custom Looker role.

Integration saves but LookML resources are missing

If Looks, Tiles, and Dashboards appear but views, explores, and lineage are missing:

1. Link a Git account with read access to your LookML repositories. See GitHub or GitLab.

2. Check LookML Project Includes and LookML Model Includes in Advanced Settings—overly narrow patterns can exclude projects or models.

3. If Crawl LookML Only is enabled, application-layer content (Looks, Tiles, Dashboards) is intentionally skipped.

Users or groups are not observed

1. Confirm Observe users and Observe groups are enabled in Advanced Settings (they are enabled by default).

2. For custom Looker roles, ensure the permission set includes see_users (required for user and group observation). See Using a custom Looker role.