Console/Log - Locate, Save and Send the Console File (Chrome) - ROES Web
Save the Google Chrome Console Log for ROES Web
Use this article when reporting ROES Web issues and support needs the Chrome browser console log.
Overview
The Chrome console log can help support identify ROES Web errors that occur in the browser. The steps below explain how to reproduce the issue, open Chrome Developer Tools, save the console log, and send it with the support request.
Save the Chrome Console Log
Open ROES Web in Chrome
Open the ROES Web Client that is having issues using the Google Chrome browser.
Reproduce the issue
Repeat the operation that causes the issue so the related messages are captured in the browser console.
Open Developer Tools
Right-click anywhere on the ROES Web page and select Inspect to open Chrome Developer Tools.
If this image does not display, open it directly: Chrome_Open_DevTools.png
Save the console log
Click the Console tab. Right-click anywhere inside the console content and choose Save as....
If this image does not display, open it directly: Chrome_Save_Console.png
Send the file to support
Attach the saved console file to a help ticket or email it to the support team with a description of the issue.
What to Include with the Log
- The saved Chrome console file.
- A short description of the issue.
- The steps used to reproduce the issue.
- The ROES Web Client URL or lab/client name where the issue occurred.
Expected Result
The customer should have a saved Chrome console file that can be attached to the help ticket or emailed to support for troubleshooting.
Escalation Notes
- Ask the customer to reproduce the issue before saving the console log.
- Confirm the log was saved from the Console tab, not only a screenshot of the page.
- Request the steps used to reproduce the issue along with the log file.
- If the issue occurs only after a specific action, have the customer perform that action immediately before saving the log.