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. An easy way to interpret these logs is to use the Google log analyzer .

How to Collect General Chrome Device Logs

To access general Chrome logs:

1. On the affected device, enter chrome://net-internals in the Chrome address bar.
2. On the top-left hand menu, select ChromeOS (the last option).
3. Click Store System Logs or Store System and User Logs (available in Chrome OS 74 and later).

A new .tgz file will be created on your device in your Downloads folder, which you can then upload to the Google log analyzer . This will provide a relatively easy to understand summary of any errors found. Most of the errors will be networking issues, but all of the system logs are captured and analyzed in this procedure.

How to Collect Network Logs

Some issues will not be captured in the general logs. To capture these issues, enable the correct type of debugging.

1. On the affected device, enter chrome://net-internals in the Chrome address bar.
2. On the top-left hand menu, select ChromeOS (the last option).
3. Select the correct debug mode. (ie Select Wi-Fi if you’re experiencing wireless issues)
4. Open a new tab and reproduce the issue.
5. Once completed, go back to the original tab.
6. Click Store System Logs or Store System and User Logs (available in Chrome OS 74 and later).