Connect Looker to Glean
Give Glean governed access to Looker’s 30 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Looker to Glean in four steps
Admins approve the server once. Everyone in Glean then gets it through the same governed connection.
- 1
Approve Looker in Runlayer
Add Looker from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Glean to Runlayer
Users add the Runlayer Plugin to Glean by following Runlayer’s setup guide. Glean reaches Looker’s 30 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Glean setup guide - 3
Sign in to Looker
Each user signs in to Looker with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Looker from Glean
Looker’s approved tools appear in Glean. Every call is checked against policy and recorded.
Tools
30 Looker tools in Glean
Runlayer policy decides which of these Glean users can call.
Dev mode
Allows toggling the Looker IDE session between Development Mode and Production Mode.
Generate embed URL
Generates a signed, private embed URL for specific Looker content, allowing users to access it directly.
Get connection databases
Retrieves a list of databases available through a specified Looker connection.
Get connection schemas
Retrieves a list of database schemas available through a specified Looker connection.
Get connection table columns
Retrieves a list of columns for one or more specified tables within a given database schema and connection.
Get connection tables
Retrieves a list of tables available within a specified database schema through a Looker connection.
Get connections
Retrieves a list of all database connections configured in the Looker system.
Get dashboards
Searches for saved dashboards in a Looker instance.
Control
What Runlayer can see and stop in Glean
Some controls apply to every client at the gateway. Others depend on what Glean exposes to Runlayer.
Gateway policy (available)
Every Looker call from Glean passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Glean as the client, the tool, and the policy and scanner decisions.
OTLP telemetry (available)
Glean can send supported OpenTelemetry events to Runlayer for observe-only session visibility.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Glean yet, so control happens at the gateway.
In Glean
- Runlayer sees Glean activity through OpenTelemetry traces for monitoring only; enforcement happens at the gateway.
Frequently asked questions
Connect more