Endpoint
GET/v1/logs/search
Query Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
q | string | Required | Search query (min 2 characters) |
fields | string | message | Comma-separated fields to search |
limit | number | 50 | Number of results (max 500) |
offset | number | 0 | Results to skip |
level | string | - | Filter by log level |
source | string | - | Filter by source |
environment | string | - | Filter by environment |
dataset | string | - | Filter by dataset |
from | number | - | Start timestamp (Unix ms) |
to | number | - | End timestamp (Unix ms) |
Searchable Fields
message- Log message (default)errorName- Error class/nameerrorStack- Error stack tracedata- JSON data field
Search Syntax
Basic Search
Simple word search (case-insensitive):Multiple Terms (AND)
All terms must be present:Phrase Search
Match exact phrase:OR Search
Match any of the terms:Exclude Terms
Exclude logs containing a term:Combined
Response
Examples
Basic Search
Search Specific Fields
Phrase Search
Exclude Terms
Combined Filters
Time Range
Error Responses
401 Unauthorized - Invalid or missing API keyAuthorization or X-API-Key header is included and valid. See Authentication for details.
400 Bad Request - Invalid query
q parameter must be at least 2 characters long. Provide a longer search query.
500 Internal Server Error:
Search Tips
- Start specific - Use specific terms to narrow results
- Use phrases - Wrap multi-word searches in quotes for exact matches
- Exclude noise - Use
-termto filter out irrelevant results - Search errors - Add
errorStackto fields when debugging exceptions - Combine with filters - Use
level=errorto focus on errors only - Time scope - Use
from/toto search specific time periods
Performance
- Search defaults to the
messagefield for best performance - Adding more fields (especially
data) increases query time - Use filters (
level,source, etc.) to reduce the search space - For large result sets, use pagination with reasonable limits