Search Issue Events
search_issue_eventsSearch and filter individual events within a Sentry issue, newest first, by environment, release, user, trace, or time using natural language or Sentry event search syntax.
Instructions
Search and filter the individual events (occurrences) of one Sentry issue, newest first, by environment, release, user, trace, or time. Accepts natural language or Sentry event search syntax. Use search_issues to search across issues.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "search_issue_events"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Sort for the Sentry link only, e.g. `-timestamp`; returned events are always newest first. | |
| fresh | No | Bypass cached reads. | |
| limit | No | Maximum events to return. | |
| query | No | Natural language or Sentry event search syntax, e.g. `environment:production release:1.0.0 user.email:alice@example.com trace:<id>`. | |
| period | No | Relative time window, e.g. `30m`, `24h`, `7d`, `90d`. | |
| issueId | No | The issue short ID, e.g. `PROJECT-123`. Give this or issueUrl. | |
| issueUrl | No | The Sentry issue URL. | |
| regionUrl | No | ||
| projectSlug | No | The project slug. Helps translate project-specific tags. | |
| organizationSlug | No | The organization slug, from `find_organizations`. Not needed with an issue URL. | |
| includeExplanation | No | Return how the query was translated or repaired. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Opens these results in Sentry. | |
| notes | Yes | ||
| query | Yes | ||
| events | Yes | Newest first; the issue events endpoint has no sort. | |
| issueUrl | Yes | ||
| explanation | Yes | ||
| executedSearch | Yes | ||
| presentationHint | Yes | ||
| suggestedActions | Yes |