Search error events
search_error_eventsSingle occurrences across issues, newest first, or counts with group_by. Use it to answer which release or route an error hits, whether a person hit it, or what failed in one trace. Open one with get_error_event.
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_error_events"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| level | No | ||
| limit | No | Rows (default 25) | |
| query | No | Text in the message, or the issue's title or culprit | |
| since | No | An ISO time, or 30m, 24h, 7d. Default 30 days, or all kept events with issue_id or trace_id | |
| cursor | No | next_cursor from the last answer | |
| source | No | Default all | |
| release | No | Text in the release: 2.0.77+185, or package@2.0.77+185 | |
| user_id | No | An account id, Fictura user id or device id | |
| group_by | No | Counts per release, route, level, environment or tag:name | |
| issue_id | No | Only this issue | |
| trace_id | No | ||
| environment | No | ||
| include_console | No | Also count console lines from the app. Always on with issue_id or trace_id |