JS Errors
The JS Errors page displays site error statistics, including JS stability, JS error list, JS error types, and JS error rate ranking.
Procedure
- Log in to the management console.
- Click
on the left and choose Management & Governance > Application Performance Management.
- In the navigation pane on the left, choose Web Monitoring > JS Errors. The JS error data is displayed.
- JS Stability: displays the number of errors, error rate, and proportion of affected users. Move the cursor to the graph. The detailed metric information is displayed.
- Click
in the upper right corner of JS Error List, JS Error Type List, and JS Error Rate Ranking and select the target metric data.
- JS Error List: displays the page URL, error information, error stack, latest error time, number of errors, and number of affected users. By default, the JS error list is sorted by Errors in descending order.
- JS Error Type List: displays the error type, error rate, number of errors, number of affected users, and PV encountering errors. By default, the JS error type list is sorted by Error Rate (%) (preferred) or Errors in descending order.
- JS Error Rate Ranking: displays the page URL, page error rate, number of errors, and PVs.
- Click a URL in the Page URL column. The detailed performance data of this URL is displayed.
- Page JS Error Rates: displays the page JS error rate, PV, and proportion of affected users. Move the cursor to the graph. The detailed metric data is displayed.
- Page JS Error Statistics: displays the time when JS errors occurred, UID, tag, error info, error stack, and allowed operations. By default, the page JS error statistic list is sorted by Time in descending order.
Table 1 JS errors parameters Parameter
Description
UV
Number of visitors who access the website. If a user accesses the site multiple times in a day, only one UV will be counted.
PV
Page view (PV), which is the number of times a page is opened or refreshed.
Avg. Load Time
Average page load time.
JS Errors
Number of JS errors.
Slow APIs
Slow APIs refer to APIs with load time longer than 1,000 ms. Slow API proportion = Number of slow APIs/Total number of APIs
API Success Rate
API success rate = Number of APIs that are successfully called/Total number of APIs
Errors
Number of errors reported during page access.
Error Rate
Error rate = Number of errors reported during page access/Total number of page views
Affected Users
Proportion of affected users = Number of users who fail to access a page/Total number of users who access the page. For example, if 100 users access a page and 10 of them encounter errors, the proportion of affected users is 10%.
Page URL
URL of the page.
Error Info
Error information.
Error Stack
Stack where an error occurred.
Latest Error Time
Time when the last error was reported.
Affected Users
Number of users who are affected.
Page Error Rate
Page error rate = Number of errors reported during page browsing/Total number of browsed pages
- Click Analyze in the Operation column to go to the summary page.
- Click
on the right of the page, select a map file, and upload it.
Based on the uploaded map file, the backend parses the error stack to locate JS errors in source code.
- Only .map files can be uploaded. The file size cannot exceed 20 MB.
- To use the stack information function, upload a map file on the right first. After the file is uploaded, the Stack Info option will be automatically enabled. If the Stack Info button is enabled, you can locate errors in the source code.
- Parsing errors include vue, angular, and JavaScript errors.
- To obtain the specified js.map file, ensure that the packaged code and dependencies are the same version as those in use.
In the JS Error Type List area, click the blue text in the Error Type column to view the details of the error type. For details, see 4, 5, and 6.
In the JS Error Rate Ranking area, click a URL in the Page URL column. The detailed performance data of this URL is displayed. For details, see 4, 5, and 6.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot