BugSnag: Get Error
bugsnag_get_errorRetrieve full details for a specific error, including aggregated data, stack trace, breadcrumbs, and metadata. Use filters to narrow summaries and analyze root causes.
Instructions
Get full details on an error, including aggregated and summarized data across all events (occurrences) and details of the latest event (occurrence), such as breadcrumbs, metadata and the stacktrace. Use the filters parameter to narrow down the summaries further.
Toolset: Errors
Parameters:
projectId (string): Unique identifier of the project. This is optional if a current project is set and is used to set the current project for BugSnag tools.
errorId (string) required: Unique identifier of the error to retrieve
filters (record<string, array>): Apply filters to narrow down the error list. Use the List Project Event Filters tool to discover available filter fields. Time filters support extended ISO 8601 format (e.g. 2018-05-20T00:00:00Z) or relative format (e.g. 7d, 24h). (default: {"event.since":[{"type":"eq","value":"30d"}],"error.status":[{"type":"eq","value":"open"}]})
Output Description: JSON object containing: - error_details: Aggregated data about the error, including first and last seen occurrence - latest_event: Detailed information about the most recent occurrence of the error, including stacktrace, breadcrumbs, user and context - pivots: List of pivots (summaries) for the error, which can be used to analyze patterns in occurrences - url: A link to the error in the dashboard - this should be shown to the user for them to perform further analysis
Use Cases: 1. Investigate a specific error found through the List Project Errors tool 2. Understand which types of user are affected by the error using summarized event data 3. Get error details for debugging and root cause analysis 4. Retrieve error metadata for incident reports and documentation
Examples:
Get details for a specific error
{
"errorId": "6863e2af8c857c0a5023b411"
}Expected Output: JSON object with error details including message, stack trace, occurrence count, and metadata
Hints: 1. Error IDs can be found using the List Project Errors tool 2. Use this after filtering errors to get detailed information about specific errors 3. Use Get Event Details tool if you need detailed information about a specific event (occurrence) rather than the aggregated error 4. If you used a filter to get this error, you can pass the same filters here to restrict the results or apply further filters 5. The URL provided in the response points should be shown to the user in all cases as it allows them to view the error in the dashboard and perform further analysis
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| errorId | Yes | Unique identifier of the error to retrieve | |
| filters | No | Apply filters to narrow down the error list. Use the List Project Event Filters tool to discover available filter fields. Time filters support extended ISO 8601 format (e.g. 2018-05-20T00:00:00Z) or relative format (e.g. 7d, 24h). | |
| projectId | No | Unique identifier of the project. This is optional if a current project is set and is used to set the current project for BugSnag tools. |