All this means a lot less guesswork! You can now prioritize your error troubleshooting based on the most valuable user impact.
For example, let’s say that you run an e-commerce site and most of your revenue comes from desktop users who make purchases from the Chrome browser. However, Browser is showing that Chrome users are encountering unusually high error rates, to the extent that some potential customers aren’t able to complete their purchases.
Using error profiles for proactive troubleshooting
With error profiles, the web team will be able to determine answers to key questions such as:
- What percentage of errors come from various browsers?
- What URLs are experiencing the most errors?
- What percentage of errors were caused by a third-party app or service?
- From which device types did most errors occur?
Error profiles use statistical measures to highlight the errors that deviate most dramatically from non-error transactions. They show you where to focus your attention instead of having to manually click through all the dimensions. Stack traces for each error are available, as well as filterable attributes to help narrow down errors by attributes collected.
With this information, web teams teams are now better equipped to troubleshoot the most impacted areas of their applications—in the most efficient ways possible.
Join the public beta