Determining what errors matter
Using the Top 10 error messages chart above, you can see one error has 6460 instances, which makes it a prime candidate for the first error you might want to fix. Sometimes the most frequently occuring error won't be the one you need to fix first. You may need a wider view of all your errors to determine the order you need to fix them in. The JS errors page, where you can group errors by a variety of factors, such as
deviceType, gives you that information. Some other things to consider when choosing the priority of your errors:
- Does this error effect your web application, if applicable? If so, improving it over others may improve both the experience and engagement of your users.
- Did this error occur recently? Sometimes focusing on errors that have occurred most recently can help prevent them from becoming larger issues that impact more customers.
- Does this error have impact on user experience? If an error doesn't negatively affect user experience, it may not be worth fixing over errors that do.
Fixing errors fast