Looker Integration Discovered Resources

Overview

The Looker integration discovers the following resources:

• LookML Explore

• LookML View

• Looker Dimension

• Looker Measure

• Looker Folder

• Looker Look

• Looker Tile

• Looker Dashboard

• Table

Looker Folder

Property	Value
name	The name of the folder.
native_id	The ID of the folder in Looker's API
parent	The parent folder of this folder. Null if the folder has no parent folder.
created at
created by	The email of the user that created the folder

Looker data visualizations: Looker Look and Looker Tile

The term "Looker Tile" is used to describe a visualization in a Looker Dashboard that is not a reference to a Looker Look.

In Looker, a dashboard is made up of dashboard elements. Some dashboard elements are data visualizations, which can either reference a Looker Look, or a visualization that "lives" inside the dashboard. Looker documentation uses the terms lookless and tile to describe the latter type of visualization. Euno uses the more commenly used term tile.

property	Value	Applicable to
name	The title of the visualization	Look, Tile
description		Look
sql_dialect	The SQL dialect of the query powering the visualization	Look, Tile
looker_model	The name of the LookML model powering the visualization	Look, Tile
looker_project_name	The name of the LookML project containing the LookML model	Look, Tile
created_at		Look, Tile
type	looker_look, looker_tile	Look, Tile
updated_at	For looker tiles, an update include all updates to the tile or the dashboard containing it	Look, Tile
native_id	The ID of the look/tile in the Looker instance	Look, Tile
created_by	The display name of the Looker user that created the Look	Look
updated_by	The display name of the Looker user that last updated the Look	Look
parent_container	For Looks, this is the Looker Folder containing it. For Tiles, this is the Looker dashboard containing the tile.	Look, Tile
last_7d_views (last_30d_views)	The total number of impressions for this Look over the last 7 (30) days	Look
last_viewed_at	The last impression time of the Look	Look

Looker Measure and Dimension for Custom Fields

Visualizations in Looker may make use of Custom Fields .

Euno observes each such custom fields as resources.

A custom measures, and a filtered custom measure are observed with type looker_measure. A custom dimension is observed with type looker_dimension.

Property	Value
name
type	looker_measure or looker_dimension
parent_container	The URI of the visualization (Looker Look or Looker Tile) where the custom field is defined
is_calculated	always true
is_identity_transformation	always false

The compiled code of a custom field is available if all the following conditions are met:

• Euno has access to the LookML model powering the query

• All the expressions in the custom field (including filter expressions) are valid

• The fields used by the custom field refer to a single LookML view, and that view was successfully processed and compiled by Euno.

• No expression in the custom field (including filter expressions) is longer than 1000 characters

Table

The Looker Integration will discover resources of type Table when it discovers a LookML view that refers to a database table. For example, if a LookML view is using the sql_table_name parameter, Euno will observe the referred table.

To determine the exact location of the referred table, the Looker Integration looks up the correct Looker Connection using the LookML Model's connection parameter. The Looker Connection usually has all the metadata required for Euno to uniquely determine the URI of the referred table.

In the case of a connection with dialect athena, The Looker Integration is not able to fetch from Looker's API the term "AWS account id" which is required to uniquely identify the referred tables. In this case, Euno defaults to using the aws account id default_aws_account.us_central1 . If you have multiple AWS accounts and you need to distinguish between them, set up manual "connection mapping".

Property	Value
name	The name of the table.
database_technology	The technology of the database, based on the the dialect of the connection
database	The name of the database
schema	The name of the schema