RSQL documentation¶
Logarys uses an RSQL-style syntax to filter logs through the Console Manager API.
Basic syntax¶
field==value
field!=value
field>value
field>=value
field<value
field<=value
Logical operators¶
| Operator | Meaning | Example |
|---|---|---|
; |
AND | service==api;level==ERROR |
, |
OR | level==ERROR,level==WARN |
Examples¶
All errors¶
level==ERROR
Errors for one service¶
service==payment-api;level==ERROR
HTTP 5xx errors¶
statusCode>=500;statusCode<600
Logs during a time range¶
timestamp>=2026-04-01T00:00:00Z;timestamp<2026-04-02T00:00:00Z
Logs from production or staging¶
env==prod,env==staging
Recommended fields¶
| Field | Description |
|---|---|
timestamp |
Log event timestamp |
level |
Log level |
service |
Service or application name |
pipelineId |
Pipeline that processed the event |
message |
Log message |
requestId |
Request/correlation identifier |
statusCode |
HTTP status code |
env |
Environment name |
URL encoding¶
Raw filter:
service==api;level==ERROR
Encoded filter:
service%3D%3Dapi%3Blevel%3D%3DERROR
Pagination and sorting¶
/api/logs?filter=level%3D%3DERROR&page=1&limit=50&sort=-timestamp
Best practices¶
Filter by date range, filter by indexed fields first, paginate results, avoid unbounded exports, and validate fields server-side.