In the process of JavaScript (JS) error diagnostics, Application Real-Time Monitoring Service (ARMS) browser monitoring provides the user behavior backtracking feature to show you a comprehensive list of the user behaviors that lead up to the errors.
Background information
ARMS browser monitoring defines all events on the page as user behaviors, including console behaviors, page jumps, user clicks, user inputs, and API calls. You can connect user behaviors in chronological order to form a behavior trace. Then, you can backtrack and analyze the behavior trace to reproduce the situation in which a specific error occurred.
Step 1: Install an ARMS agent
After you install the ARMS agent, your frontend applications can be fully monitored. Select a method to install the ARMS agent as needed. For more information, see Browser Monitoring overview.
Step 2: Diagnose an error
Use the user behavior backtracking feature to reproduce the situation in which a specific JS error occurred and diagnose causes of the error.
-
Log on to the ARMS console. In the left-side navigation pane, choose .
-
On the Browser Monitoring page, select a region in the top navigation bar and click the name of the application that you want to manage.
- In the left-side navigation pane, click JS Error Diagnostics.
- On the JS Error Diagnostics page, click the Frequent Errors tab.
The page displays a list of frequent errors with the following columns: Error Message, Page, Error Count, Affected Users, and Actions. The Actions column contains a Diagnose link for each error.
- For the desired error, click Diagnosis in the Actions column.
- On the Error details page, analyze the actions in the User Behavior Trace section to find the operation that caused the error.
The Stack Trace section at the top of the page displays the specific error message, such as
Error Request failed with status code 504. The User Behavior Trace section below presents a timeline of user actions that occurred before the error. These actions include types such as API call (with status codes and request counts), click events, and page navigation. Each record includes a timestamp and a link to more details, helping you pinpoint the operation that caused the error.