- Applying our recommendations when prioritizing errors
- If you want to proactively monitor your site for errors, checking the Summary page is adequate most of the time.
Using the Top 10 error messages chart above, you can see one error has 6,460 instances. The frequency of this error could make it a prime candidate to resolve first, but that may not always be the case. You may need a wider view of all your errors to determine the order you need to fix them in. From the JS errors page, you can group errors by
deviceType. You can ask yourself these questions when planning your work:
- Does this affect business critical user journeys? If an error doesn't impact your customer's ability to sign up, log in, or make a purchase, then you might be able to deprioritize the issue.
- Has this error occured recently? Focusing on newer errors can prevent them from becoming larger issues later.
- Does this error result in high latency?
Once you've chosen an error, select it from the JS errors page. From here, you can open different views to investigate a specific error:
- Scroll through the Event Trail section to ensure you've found everything that needs to be fixed. If there's more to resolve, your event trail will let you know.