home User Guide Getting Started Help Center Documentation Community Training Certification
menu
close
settings
Looker keyboard_arrow_down
language keyboard_arrow_down
English
Français
Deutsch
日本語
search
print
Usage

The Usage page is a Looker-created dashboard that presents usage information about your Looker instance. Admins can use the data to better understand how their users utilize the application. To view the Usage page, from the Server section of the Admin menu, select Usage.

The i__looker model

All of the information in the Usage panel is based on a LookML model called i__looker. Understanding that model can help you build useful, custom reports around the usage of your Looker instance and information about saved Looks and Dashboards. See our Creating Looker usage and metadata reports with i__looker documentation page to learn more.

Usage dashboard

The Usage dashboard is accessed from the Admin page of Looker:

You can download or schedule the Usage dashboard just as any other dashboard.

Also, you can drill into metrics and elements like any other dashboard:

Query by Source tile

The Query by Source tile, which is located at the top of the Usage page, includes information about the number of queries run from different sources within Looker. The possible sources are:

Context comments for SQL queries

Looker adds a unique comment to the beginning of each SQL query. The comments are added to queries from Explores, SQL Runner, the API, and filter suggestions. Context comments are automatically included.

On Google BigQuery connections, context comments invalidate Google BigQuery’s ability to cache, and can negatively impact cache performance. Context comments can be disabled for Google BigQuery connections. See the Google BigQuery documentation page for more information.

Context comments are added in the following format:

-- Looker Query Context '{ "user_id":<user ID>,"history_id":<history ID>,"instance_slug":"<Looker instance number>"}'

The comments provide the following information:

The context comments are added to outgoing SQL commands right before the SQL is sent to the database. This prevents the comments from affecting the caching of Looker queries, but it also means that you cannot see the added comments in most places in Looker (such as the Queries page or i__looker).

Instead, you’ll see these comments in your database logs, which is useful for security and auditing. You might also be able to query the comments in SQL Runner:

This example is for Amazon Redshift. See the documentation for your SQL dialect to determine the command you’d need to run.

Top