System Activity is a [LookML model](https://docs.cloud.google.com/looker/docs/model-and-view-files#model_files) that connects to Looker's underlying application database. System Activity [Explores](https://docs.cloud.google.com/looker/docs/usage-reports-with-system-activity-explores.md.txt) and [dashboards](https://docs.cloud.google.com/looker/docs/system-activity-dashboards.md.txt) that are built upon this model show information about your Looker instance, which includes the following:

- All Looks and dashboards that are saved on your instance
- User and historical query information
- 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.
>
> 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 models. Looker admins have access to System Activity by default. A Looker admin can grant access to System Activity to a non-admin user by giving the user the `see_system_activity` permission.

System Activity includes the following elements:

- [System Activity dashboards](https://docs.cloud.google.com/looker/docs/system-activity-dashboards.md.txt): Looker-created dashboards showing usage and performance information about the Looker instance. You can [download](https://docs.cloud.google.com/looker/docs/viewing-legacy-dashboards#downloading_your_dashboard), [schedule](https://docs.cloud.google.com/looker/docs/viewing-legacy-dashboards#scheduling_dashboard_data_delivery), [set alerts on](https://docs.cloud.google.com/looker/docs/alerts-overview.md.txt), and [drill into](https://docs.cloud.google.com/looker/docs/viewing-and-interacting-with-explores.md.txt#drilling_down_into_the_data) metrics and elements just like on any other dashboard. Data in the System Activity dashboards is updated and cached every 12 hours.

- [System Activity Explores](https://docs.cloud.google.com/looker/docs/usage-reports-with-system-activity-explores.md.txt): Using System Activity Explores, you can create your own Looks and dashboards to monitor and analyze your Looker instance. See the [System Activity Explores](https://docs.cloud.google.com/looker/docs/usage-reports-with-system-activity-explores.md.txt#system_activity_explores) page for a list of Explores and their cache rules.

- [System Activity for Looker reports](https://docs.cloud.google.com/looker/docs/system-activity-for-looker-reports.md.txt): If the [Looker reports](https://docs.cloud.google.com/looker/docs/enabling-looker-reports.md.txt) feature is enabled on your Looker instance, System Activity dashboards and Explores include information about the [Looker reports](https://docs.cloud.google.com/looker/docs/move-share-copy-reports.md.txt) that are saved on your Looker
  instance.

- [Elite System Activity](https://docs.cloud.google.com/looker/docs/elite-system-activity.md.txt): An optional analytical store that increases System Activity performance and storage limits. Elite System Activity is a paid feature on Looker (original), and is a standard feature on the [**Enterprise** and **Embed** editions](https://docs.cloud.google.com/looker/docs/looker-core-feature-differences.md.txt) of Looker (Google Cloud core).

- [Read replica option](https://docs.cloud.google.com/looker/docs/system-activity-read-replica-db.md.txt): For customer-hosted instances only, this method increases System Activity performance and provides longer System Activity data retention.

- [Understanding PDT log actions](https://docs.cloud.google.com/looker/docs/pdt-log-actions.md.txt): Use the **PDT Event Log** Explore to view and understand PDT log actions and their corresponding action data.

- [Looker events](https://docs.cloud.google.com/looker/docs/events.md.txt): The events that Looker generates and how to view them.

## System Activity in embedded environments

In an [embedded environment](https://docs.cloud.google.com/looker/docs/signed-embedding.md.txt), strict restrictions
prevent embedded users from rendering underlying system data, even if you grant
the
[`see_system_activity`](https://docs.cloud.google.com/looker/docs/admin-panel-users-roles.md.txt#see_system_activity)
permission during single sign-on (SSO) authentication. Directly embedding System
Activity dashboards for typical embedded users isn't supported.

To share System Activity insights with embedded users, you must extract the data
and serve it from a customer-controlled model. You can use the following
alternatives:

- **Looker API scripting** : Use a [Looker API client SDK](https://docs.cloud.google.com/looker/docs/api-sdk.md.txt), such as the Python SDK, to programmatically run queries against the `system__activity` model. Schedule a script to fetch daily results and write them directly to an external database.
- **Scheduled deliveries** : Create a Look that's based on System Activity and [schedule a daily delivery](https://docs.cloud.google.com/looker/docs/delivering-looks-explores.md.txt) as a CSV or JSON file to an [Amazon S3 bucket](https://docs.cloud.google.com/looker/docs/delivering-looks-explores.md.txt#delivery_options_for_amazon_s3) or [SFTP server](https://docs.cloud.google.com/looker/docs/delivering-looks-explores.md.txt#delivery_options_for_sftp). Then, use an extract, transform, and load (ETL) pipeline to ingest the data.
- **Custom models and dashboards** : Extract the data by using Looker API scripting, scheduled deliveries, or [Elite System Activity](https://docs.cloud.google.com/looker/docs/elite-system-activity.md.txt), and load it into your own database, such as BigQuery. Then, create a standard LookML model on top of that data and embed dashboards that you build from the new model.