[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-25。"],[],[],null,["# Admin settings - Usage\n\n| **Note:** [Looker (Google Cloud core)](/looker/docs/looker-core-overview) instances do not include this page. Usage information can be viewed using the [System Activity dashboards](/looker/docs/system-activity-dashboards) and [Explores](/looker/docs/usage-reports-with-system-activity-explores).\n\nThe **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**.\n| **Note:** Check the [System Activity dashboards](/looker/docs/system-activity-dashboards) for additional usage information about your Looker instance.\n\nUsage dashboard\n---------------\n\nAccess the **Usage** dashboard from the **Admin** panel under the **Server** section.\n| **Note:** If you have a permission that provides access to only select pages in the Admin panel, such as [`manage_schedules`](/looker/docs/admin-panel-users-roles#manage_schedules), [`manage_themes`](/looker/docs/admin-panel-users-roles#manage_themes), or [`see_admin`](/looker/docs/admin-panel-users-roles#see_admin), but you don't have the [Admin role](/looker/docs/admin-panel-users-roles#default_roles), the page or pages that are described here may not be visible to you in the Admin panel.\n\nYou can [download](/looker/docs/viewing-legacy-dashboards#downloading_your_dashboard) or [schedule](/looker/docs/viewing-legacy-dashboards#scheduling_dashboard_data_delivery) the **Usage** dashboard just as any other dashboard.\n\nYou can also [drill down](/looker/docs/viewing-and-interacting-with-explores#drilling_down_into_the_data) on data points on the **Usage** dashboard.\n\n### Query by Source tile\n\nThe **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. These are the possible sources:\n\n- **API (version number)**: Queries that came from the Looker API for the instance.\n- **Dashboard**: Queries relating to tiles present on a dashboard.\n- **Dashboard Prefetch**: Queries from the API to pre-run a dashboard.\n- **Explore**: Queries associated with running Explores.\n- **Other**: Queries from sources that do not fall into any other category.\n- **Private Embed**: Queries that were initiated by a private embed context.\n- **Public Embed**: Queries run from content that is accessed via public URL.\n- **Query** : Short for `source_query`, queries generated by Looker's internal database.\n- **Renderer**: Queries relating to the generation of images (.png and .pdf) for scheduled items and downloads.\n- **SQL Runner** : Queries that are run directly in the [SQL Runner](/looker/docs/sql-runner-basics).\n- **Saved Look**: Queries associated with Looks.\n- **Scheduled Task**: Queries run by Looker when it generates a Look or dashboard for delivery.\n- **Suggest Filter** : Queries generated when users click on a filter that generates suggestions. In this case, Looker runs a `SELECT DISTINCT` on the filtered field to find the suggestions to surface to the user.\n\nContext comments for SQL queries\n--------------------------------\n\nLooker 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.\n\u003e [Context comments on Google BigQuery connections](/looker/docs/db-config-google-bigquery#context_comments) are disabled by default because context comments invalidate Google BigQuery's ability to cache and can negatively impact cache performance. You can enable context comments for a BigQuery connection by enabling the [**Disable Context**](/looker/docs/db-config-google-bigquery#disable_context_comment) toggle on the [Connection Settings](/looker/docs/connecting-to-your-db) page for the connection. See the [Google BigQuery](/looker/docs/db-config-google-bigquery#context_comments) documentation page for more information.\n\nContext comments are added in the following format: \n\n -- Looker Query Context '{ \"user_id\":\u003cuser ID\u003e,\"history_slug\":\u003chistory slug\u003e,\"instance_slug\":\"\u003cLooker instance number\u003e}'\n\nThe comments provide the following information:\n\n- **`user_id`** : The unique identifier for each user on the Looker instance. You can match this user ID to the user IDs on the [**Users**](/looker/docs/admin-panel-users-users#viewing_and_searching_users) page in the **Admin** menu.\n\n- **`history_slug`**: The unique identifier for each query that is run on the database by the Looker instance.\n\n- **`instance_slug`**: The ID number of the Looker instance that issued the query. Looker support can use this information to help you troubleshoot, if necessary.\n\nThe 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](/looker/docs/caching-and-datagroups) 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 [System Activity](/looker/docs/usage-reports-with-system-activity-explores)).\n\nInstead, you'll see these comments in your database query logs."]]