Overview
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 the severity of the issue.
Explore your issues
Each item listed in the Error Tracking Explorer surfaces high-level information about the issue, including the following:
- 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.
- The number of error occurrences in the selected time period.
- A graph of error occurrences over time in the selected time period.
Time range
Adjust the time range selector to display issues that have error occurrences within the selected time period.
You can specify a specific range or select a preset range from the dropdown menu.
Facets
Error Tracking automatically indexes a predefined list of attributes from underlying error occurrences and creates facets for them. Use facets to pivot or filter your issues. 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.
The Error Tracking Explorer returns all issues with at least one error occurrence in the selected time period that match the set of selected facets.
Inspect an issue
Click on any issue in the issue list to open the issue panel and access additional error information about your backend service.
Get a high-level overview
The issue panel contains high-level information you need when troubleshooting an issue.
You can learn about the issue’s lifecycle such as its first and last occurrence dates, related code versions, and total error occurrences since its 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
Explore error samples that are grouped into the issue such as the following:
Each error sample displays the information needed to understand why an error 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.
Connect your repository to enable code snippets
Set up the GitHub integration to see code snippets in your stack traces.
To get started with configuring your repository, see the Source Code Integration documentation.
Further Reading
Additional helpful documentation, links, and articles:
