home User Guide Getting Started Help Center Documentation Community Training Certification
Looker keyboard_arrow_down
language keyboard_arrow_down
Looker documentation will be moving to cloud.google.com in mid-2022!
All the information you rely on will be migrated and all docs.looker.com URLs will be redirected to the appropriate page.
System Activity dashboards

The System Activity section of Looker’s Admin menu displays Looker-created dashboards that show usage and performance information about the Looker instance. You can download, schedule, set alerts on, and drill into metrics and elements just like on any other dashboard. Data in the System Activity dashboards is updated and cached every 12 hours.

Before enabling System Activity on a customer-hosted Looker deployment with MySQL backend, verify that you have properly set up the user for the backend database. Specifically, you must perform the step to grant all on looker_tmp.* to '<DB_username>'@'%'; before enabling the System Activity feature. See the procedure on the Migrating the Looker backend database to MySQL documentation page.

Because the permission to deliver content to email destinations is model specific, to send or schedule System Activity dashboards to email destinations, users must have All models selected in the Model Set specified for their role.

The System Activity dashboards connect to Looker’s underlying application database. They show information about your Looker instance, including Looks and dashboards saved on your instance, user information, historical query information, and instance performance statistics. Both the granularity and retention of System Activity data are subject to system constraints. System Activity is designed for collecting high-volume data, and aggregating it can be used to supplement your business logs.

This data can be useful for supplementing monitoring and auditing activities, but is not intended to replace your current compliance strategy.

By default, System Activity data is stored in Looker’s internal database. In this configuration, Looker stores a maximum of 90 days of historical query and event data.

The text in filters run by users is accessible in System Activity and can be viewed by any user who has permission to view the System Activity model.

Take action: Modify who has view access to the System Activity model. Looker admins have access to this model by default. Non-admin users can be granted access to the System Activity model if they are given the see_system_activity permission.

System Activity dashboards and Explores are restricted in the number of concurrent queries that can be run. This restriction may increase loading times for System Activity dashboards.

Chat Team Tip: Time-based data in System Activity is stored in the Looker System time zone. See the Using time zone settings documentation page for more information.

System Activity dashboards

These are the System Activity dashboards:

User Activity dashboard

The User Activity dashboard shows information about your users and their usage of your Looker instance:

The User Activity dashboard includes tiles that show the following information:

Content Activity dashboard

The Content Activity dashboard shows information about which dashboards, Looks, and Explores are being viewed and scheduled on your Looker instance:

The Content Activity dashboard includes tiles showing:

Database Performance dashboard

The Database Performance dashboard shows information about the performance of content and PDTs on your Looker instance, including the total and average runtimes of queries and PDTs, and lists the number of query errors and PDT build failures:

The Database Performance dashboard includes tiles showing:

Instance Performance dashboard

The Instance Performance dashboard shows information about the load and performance of the scheduler and performance-intensive content:

The Instance Performance dashboard includes tiles showing:

Errors and Broken Content dashboard

The Errors and Broken Content dashboard shows dashboards, Looks, schedules, and PDTs that produce errors, and numbers of errors for each query source:

The Errors and Broken Content dashboard includes tiles showing: