If you want to reproduce the situation where an error occurred based on the context to identify the cause of the error, you can use the session tracing feature of Application Real-Time Monitoring Service (ARMS) Browser Monitoring. This feature implements distributed tracing based on a username or user ID to show a comprehensive list of user behavior traces, including page loading, API calls, JS errors, and user operations. This helps identify and analyze the cause of an error.
Procedure
- Log on to the ARMS console.
- In the left-side navigation pane, click Browser Monitoring. On the Browser Monitoring page, click the name of the application.
- In the left-side navigation pane, choose .
View session details
Other methods to view session details
- In the left-side navigation pane, choose Session ID column of the Slow Page Session Trace (TOP20) section. . On the page that appears, click a session ID in the
- In the left-side navigation pane, choose Frequent Errors tab, click Diagnose in the Actions column that corresponds to an error. On the page that appears, click View Session in the User behavior backtracking section. . On the
- In the left-side navigation pane, choose API Requests tab, click the number of errors in the Error Number column. On the page that appears, click View Session in the Network Request Information section. . On the
- In the left-side navigation pane, choose All Logs tab, click View Session in the Actions column in the Log List section. . On the