How to Find ChromeOS Logs and Analyze Them

A common troubleshooting step in Windows is to review the logs in Event Viewer or use Windows Debugger (windbg) or other utilities to analyze dump files.

Chrome also has event logs that can be viewed in the Chrome browser. These logs should be familiar to support analysts who know Linux. A way to interpret these logs is to use the Google log analyzer.

Collect General Chrome Device Logs

There are two ways to collect general device logs:

1. Option 1 - Only available in Chrome version 120 and later.
   1. On the affected device, enter chrome://support-tool in the address bar.
   2. In the Describe the issue page, do the following:
      1. (Optional) Enter your support ticket ID.
      2. (Optional) Enter your email address.
      3. (Optional) Enter the description of your issue.
      4. Click Continue.
   3. At the bottom of the list, click Select all.
      Note: Unless you are asked to collect specific logs, we recommend collecting all logs to share with the support team.
   4. Click Continue.
   5. Review the personal information that is collected in the logs. You can keep the information in the collected file or remove them by categories.
   6. Click Export.
   7. Select the folder where you want to create the log file.
   8. Click Save. A new .zip file is created on the device in the folder that you have selected. You can then upload to the Log Analyzer or your support ticket.
2. Option 2
   1. On the affected device, enter chrome://network in the address bar.
   2. At the top, click Network logs.
   3. Under Options, select the following checkbox options:
      1. Include a policies.json file with policy configurations
      2. Include all log files collected by debugd as a separate archive
      3. Include Chrome log files in the archive
   4. Click Store system logs. A new .tgz file is created on the device in the Downloads folder. You can then upload to the Log Analyzer or your support ticket.

Collect Network Logs

Sometimes, the issue that you reproduce is not captured in the general logs. You must capture the issue by enabling the correct type of debugging.

1. On the affected device, enter chrome://network in the address bar.
2. At the top, click Network logs.
3. Under Network debugging, select the correct debug mode.
4. Open a new tab and reproduce the issue.
5. Once completed, go back to the original tab.
6. Under Options, select the following checkbox options:
   • Include the system_logs.txt file sent in feedback reports
   • Include all log files collected by debugd as a separate archive
7. (Optional) Under Options, select additional checkbox options, if needed.
8. Click Store System Logs. Upload or export the logs from the Downloads folder to an external storage. You can then upload them to the NetLog Viewer or your support ticket.