Looker

Overview

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.


Prerequisites

Looker client ID and client secret

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.


Set up a Looker data-source connector via Zenskar dashboard

Once the prerequisites are complete, connect Looker as a data source in Zenskar.

  1. Log into your Zenskar dashboard.
  2. In the left side bar, click Usage > Data Sources.
  3. In the top-right corner, click + ADD DATA SOURCE.
  4. On the Add New Data Source page, configure the Looker connector:
General details
FieldDescriptionRequired
Source NameEnter a unique name for this data source.Yes
Source TypeSelect Looker from the dropdown menu.Yes
Connector configuration
FieldDescriptionRequired
Client IDThe first part of the API3 key generated in Looker. Each Looker user has a unique API key.Yes
Client SecretThe second part of the API3 key generated in Looker.Yes
DomainThe domain of your Looker instance. Examples:domainname.looker.com or looker.clientname.com or 123.123.124.123:8000Yes
Look IDs to runIDs of specific Looks to run and sync results from. Leave empty if you do not want to sync Look-based query results.No
Data source access mode (read-only)

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
  1. Click on the SAVE SOURCE button.

Addendum

Supported Looker output streams

Refer to the Looker API documentation.

Dashboards and Looks

ObjectDescription
DashboardsDashboard metadata
Dashboard ElementsWidgets / tiles inside dashboards
Dashboard FiltersFilters configured on dashboards
Dashboard LayoutsDashboard layout definitions
Dashboard Layout ComponentsLayout building blocks
LooksSaved Look queries
Run LooksExecution results for selected Look IDs

Content and Navigation

ObjectDescription
BoardsBoards in Looker UI
Board ItemsItems pinned to Boards
Board SectionsSections inside Boards
FoldersFolder hierarchy for content
Folder AncestorsFolder lineage
SpacesLegacy content spaces
Content MetadataMetadata for content objects
Content Metadata AccessPermissions for content metadata

Users and Access Control

ObjectDescription
UsersUser accounts
User SessionsUser login sessions
User AttributesDefined user attributes
User Attribute ValuesAttribute values per user
User Attribute Group ValuesGroup-based values for attributes
RolesRole metadata
Model SetsModel access per role
Permission SetsPermission bundles
PermissionsDefined permissions
Role GroupsGroups attached to roles
User Login LockoutsLogin lockout records

Projects and Models

ObjectDescription
ProjectsLooker projects
Project FilesFiles inside a Looker project
Git BranchesGit branches for Looker projects
LookML ModelsLookML model definitions

System and Administration

ObjectDescription
ConnectionsDatabase connections defined in Looker
DatagroupsCaching / refresh logic definitions
Integration HubsAvailable integration hubs
IntegrationsConfigured integrations
Primary Homepage SectionsHomepage UI sections
Query HistoryQuery execution history
Legacy FeaturesDeprecated system features
VersionsAPI version metadata
WorkspacesWorkspaces in Looker