Error Tracking Explorer
Explore your issues
The Error Tracking Explorer shows you a list of ongoing issues. An issue is a group of similar errors that have the same fingerprint and which might need to be fixed depending on how critical it is. Each item listed in the explorer surfaces high-level information about the issue:
- The error type and the error message
- The path to the file in which underlying errors occurred
- Information about the issue’s lifetime:
- When it was first and last seen
- Number of error occurrences in the selected time period
- Graph of error occurrences over time in the selected time period
Adjust the time range selector in the top right corner of the Explorer to show issues that have error occurrences within the selected time period. You can specify a specific range or select a preset range from the dropdown.
Error Tracking automatically indexes a predefined list of attributes from the underlying error occurrences and creates facets for them. The facet list displays the members of an attribute for the selected time period and provides basic analytics, such as the number of corresponding issues. Use facets to pivot or filter your issues. The Explorer returns all issues having at least one error occurrence in the selected time period matching the set of selected facets.
Inspect an issue
Click on any issue to open the issue panel and see more information about it.
Get a high-level overview
The high-level details you need when troubleshooting an issue can be found in the upper part of the panel. From here, you can learn about the issue’s lifecycle, such as its first and last occurrence dates, related code versions, and total error occurrences since inception. The graph of error occurrences shows up to 14 days in the past to give you an overview of the trend of the issue.
Browse individual error occurrences
In the lower part of the issue panel, navigate error samples that are grouped into the issue:
Each error sample gives the information you need to understand why it happened and how to resolve it, for example:
- The error stack trace, which shows where the error happens in the source code.
- All the error span tags, such as the resource or operation name, with direct access to the related trace or to logs that are linked to it.
- Insights about the health of the underlying host or container when this particular error occurred.