The Looker data source allows you to bring modeled analytics data from Looker into Zenskar. You can sync metadata, (such as dashboards, models, and users) and optionally run specific Looks to ingest query results.
An API key is used to access the Looker API. API keys are created by Looker and consist of a Client ID and a Client Secret. Looker requires an API key to execute commands with the Looker API.
Please read the API Key section in Looker's documentation for instructions on how to generate Client ID and a Client Secret.
Once the prerequisites are complete, connect Looker as a data source in Zenskar.
- Log into your Zenskar dashboard.
- In the left side bar, click Usage > Data Sources.
- In the top-right corner, click + ADD DATA SOURCE.
- On the Add New Data Source page, configure the connector:
- Click on the SAVE SOURCE button.
| Field | Description | Required |
|---|
| Source Name | Enter a unique name for this data source. | Yes |
| Source Type | Select Looker from the dropdown menu. | Yes |
| Field | Description | Required |
|---|
| Client ID | The first part of the API3 key generated in Looker. Each Looker user has a unique API key. | Yes |
| Client Secret | The second part of the API3 key generated in Looker. | Yes |
| Domain | The domain of your Looker instance. Examples:domainname.looker.com or looker.clientname.com or 123.123.124.123:8000 | Yes |
| Look IDs to run | IDs of specific Looks to run and sync results from. Leave empty if you do not want to sync Look-based query results. | No |
Zenskar replicates data directly from your Looker instance to Zenskar’s data infrastructure. The data is periodically synced to maintain freshness. This option is:
- Ideal for small-mid size database (less than 30GB)
- Ideal for periodical data ingestion
- Optimised for quicker invoice generation
Refer to the Looker API documentation.
| Object | Description |
|---|
| Dashboards | Dashboard metadata |
| Dashboard Elements | Widgets / tiles inside dashboards |
| Dashboard Filters | Filters configured on dashboards |
| Dashboard Layouts | Dashboard layout definitions |
| Dashboard Layout Components | Layout building blocks |
| Looks | Saved Look queries |
| Run Looks | Execution results for selected Look IDs |
| Object | Description |
|---|
| Boards | Boards in Looker UI |
| Board Items | Items pinned to Boards |
| Board Sections | Sections inside Boards |
| Folders | Folder hierarchy for content |
| Folder Ancestors | Folder lineage |
| Spaces | Legacy content spaces |
| Content Metadata | Metadata for content objects |
| Content Metadata Access | Permissions for content metadata |
| Object | Description |
|---|
| Users | User accounts |
| User Sessions | User login sessions |
| User Attributes | Defined user attributes |
| User Attribute Values | Attribute values per user |
| User Attribute Group Values | Group-based values for attributes |
| Roles | Role metadata |
| Model Sets | Model access per role |
| Permission Sets | Permission bundles |
| Permissions | Defined permissions |
| Role Groups | Groups attached to roles |
| User Login Lockouts | Login lockout records |
| Object | Description |
|---|
| Projects | Looker projects |
| Project Files | Files inside a Looker project |
| Git Branches | Git branches for Looker projects |
| LookML Models | LookML model definitions |
| Object | Description |
|---|
| Connections | Database connections defined in Looker |
| Datagroups | Caching / refresh logic definitions |
| Integration Hubs | Available integration hubs |
| Integrations | Configured integrations |
| Primary Homepage Sections | Homepage UI sections |
| Query History | Query execution history |
| Legacy Features | Deprecated system features |
| Versions | API version metadata |
| Workspaces | Workspaces in Looker |
