[[["易于理解","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 - Log\n\n| **Note:** [Looker (Google Cloud core)](/looker/docs/looker-core-overview) instances don't include this page. Looker (Google Cloud core) uses Cloud Logging. See the [View instance logs for Looker](/looker/docs/looker-core-logging) documentation page for more information.\n\nLog panel\n---------\n\nThe **Log** panel shows the 500 most recent system log messages that were generated by your Looker instance. To view the **Log** page, from the **Server** section of the **Admin** menu, select **Log**.\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 limit the information that is shown in the Log panel. To do so, enter text in the **Filter** field to have the Log panel show only messages that include that text.\n\nTo update the log and show the most recent 500 messages, select **Refresh Log**.\n\nTo adjust the severity level of log messages that are shown for Looker services, adjust the [log levels](#log_levels).\n| **Note:** Although logs from Looker-hosted instances cannot be exported, you can access the same information in a System Activity Explore. To explore data about usage on your Looker instance, see the [Monitoring Looker usage with System Activity Explores](/looker/docs/usage-reports-with-system-activity-explores) documentation page.\n\nLog levels\n----------\n\nThe **Log Levels** section lets you set the minimum severity level required for a message to show up in the log, for several different Looker services. This lets you hide log information that does not interest you.\n\u003e The default severity level for the **db:** \\* and **db:looker** services is set to **info** , which means SQL statements that contain or filter on personal information (for example, customer names) are logged by Looker. This is true for severity settings of **info** , **verbose** , or **debug** . To turn off logging of SQL statements, set the severity level of the **db:** \\* and **db:looker** services to **warn** , **error** , or **fatal**.\n\u003e\n\u003e \u003cbr /\u003e\n\u003e\n\u003e \u003cbr /\u003e\n\u003e\n\u003e Looker logs SQL statements both to an internal database (where metadata for Looker objects created by users is stored) and to an external databases (where customer data and metadata is stored).\n\u003e\n\u003e \u003cbr /\u003e\n\u003e\n### Severity descriptions\n\nLog message severity levels are listed next, from least severe to most severe:\n\n- **debug**: Debug log entries are detailed information messages that show Looker's internal application processes. This severity level is typically used only for debugging internal code.\n\n- **verbose**: These are detailed informational messages that show events occurring in Looker at a more finely grained level. This severity level is typically used only for troubleshooting.\n\n- **info**: These are standard informational messages that show regular events occurring in Looker.\n\n- **warn**: These messages indicate potentially harmful situations.\n\n- **error**: These messages indicate error events that are probably not serious enough to cause Looker to stop running.\n\n- **fatal**: These messages indicate very severe error events that will likely cause Looker to stop running.\n\n### Service descriptions\n\nThe **Default** drop-down sets the default severity level for all Looker services. All services that are set to **default** use the severity level in the **Default** drop-down. The default severity level for the **Default** drop-down is **info**.\n\nYou can also set severity levels individually for the following services:\n\n- **pdt** : Messages that are associated with the [persistent derived table](/looker/docs/derived-tables#persistent_derived_tables_(pdts)) process.\n\n- **db:**\\*: Messages that are generated by queries to the analytics database or by queries to any customer database.\n\n- **db:looker**: Messages that are generated by queries to the Looker backend database.\n\n- **http**: Messages that are generated from HTTP requests that the frontend webserver is receiving or processing.\n\n- **http_core**: Messages that are generated from HTTP requests to the core webserver that serves the internals of the application.\n\n- **jsch** : Messages that are generated by SSH connections to the Git service. The default setting is **warn** level, which displays no information. Change to the **info** level to troubleshoot SSH connection issues.\n\n- **logger**: Messages that are generated when you make changes to the log level.\n\n- **org.apache.active**: Messages that are generated by ActiveMQ. ActiveMQ is a messaging service that Looker uses to communicate tasks between subsystems. It is used by the scheduler, PDT regeneration, and other long-running tasks.\n\n- **raven**: Messages that are generated by the error reporting service.\n\n- **render**: Messages that are generated by the renderer, which renders PDFs and PNGs.\n\n- **scheduler**: Messages that are generated by the scheduler process.\n\nAfter you have modified the log level for a service, select **Set Levels** to save your changes.\n\nSetting the log format on customer-hosted instances\n---------------------------------------------------\n\nBy default, system messages are displayed in text using the following format: \n\n 2019-09-25 15:14:12.301 -0700 [INFO|007d0|main] :: Starting Looker : Version 6.21.0-localdev-ea88a4\n ...\n 2019-10-01 14:37:53.424 -0700 [INFO|0002a|http] :: Request from 0:0:0:0:0:0:0:1 GET /folders/1, {}\n ...\n 2019-10-01 14:37:53.425 -0700 [INFO|0002a|db:looker] :: (0.000180s) SELECT count(*) AS \"COUNT\" FROM \"USER\" LIMIT 1\n\nSome system messages, such as exceptions and SQL queries, are generated as multiple-line output. This can cause problems for log processors that require single-line entries for pattern matching.\n\nIf your Looker instance is customer-hosted and you require single-line output, you can use the `--log-format=json` [startup option](/looker/docs/startup-options) to format log entries into single-line JSON structures. The following example shows the same events as the previous example, but in JSON format: \n\n {\"t\":\"2019-09-25 15:14:56.513 -0700\",\"s\":\"INFO\",\"rid\":\"007d0\",\"c\":\"main\",\"msg\":\"Starting Looker : Version 6.21.0-localdev-ea88a4\"}\n ...\n {\"t\":\"2019-10-01T14:35:37.577 -07:00\",\"s\":\"INFO\",\"rid\":\"0002c\",\"c\":\"http\",\"ip\":\"0:0:0:0:0:0:0:1\",\"verb\":\"GET\",\"path\":\"/folders/1\",\"params\":{}}\n ...\n {\"t\":\"2019-10-01T14:35:37.581 -07:00\",\"s\":\"INFO\",\"rid\":\"0002c\",\"c\":\"db:looker\",\"duration\":\"0.000344\",\"sql\":\"SELECT count(*) AS \\\"COUNT\\\" FROM \\\"USER\\\" LIMIT 1\"}"]]
