Search log lines
search_logsApplication log lines from the backend SDK, newest first, or counts with group_by. Use it to see what happened around an error: pass trace_id for one request's lines, or q and level to search. Lines are kept 14 days, and the default range is the last 24 hours.
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_logs"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Text in the message, any case | |
| to | No | An ISO time, or how long ago | |
| from | No | An ISO time, or 30m, 24h, 7d | |
| level | No | trace, debug, info, warning, error or fatal; commas for several | |
| limit | No | Lines (default 50) | |
| route | No | ||
| cursor | No | next_cursor from the last answer | |
| logger | No | ||
| release | No | ||
| user_id | No | ||
| group_by | No | Counts per value instead of lines | |
| trace_id | No | One trace's lines, however old | |
| environment | No | ||
| message_chars | No | Characters of each message (default 500) |