Skip to content

observe_traces_search

Search the traces of the current product, newest first.

Tool

Search the traces of the current product, newest first.

Search the traces of the current product, newest first. Reads the last hour unless from/to say otherwise, and answers windows of up to 24 hours unless traceId pins the read. One row per trace: its root span, how long the whole trace took, how many spans it has and whether any of them failed. Filters are structured; there is no SQL surface. Page with nextCursor.

HTTP
GET /observe/traces/search

Arguments

Name
Type
Required
Description
to
string
—
Newest span start to include, ISO 8601. Defaults to now
from
string
—
Oldest span start to include, ISO 8601. Defaults to 1 hour before `to`. A window longer than 24 hours is rejected unless `traceId` pins the read, in which case it may reach back to the edge of span retention, and does so by default
name
string
—
Only traces one of whose spans carries this exact span name, e.g. "GET /users"
limit
integer
—
How many traces to return, 1-1000, default 100
cursor
string
—
The nextCursor of the previous page; omit for the first page
status
string
—
Only traces in this state: "error" when any span failed, "ok" when none did and at least one reported OK, "unset" when no span reported a status
service
string
—
Only traces one of whose spans belongs to this service, e.g. "api"
traceId
string
—
Only this trace, by its 32-character hex id
environment
string
—
Only traces of this environment, e.g. "production"
maxDurationMs
number
—
Only traces that took at most this many milliseconds end to end
minDurationMs
number
—
Only traces that took at least this many milliseconds end to end

Response

Field
Type
Always
Description
traces
array
•
The matching traces, newest first
nextCursor
string
•
Pass back as cursor for the next page; null when the last page was reached

Try it

Search the traces of the current product, newest first.

When to use

Search the traces of the current product, newest first. Reads the last hour unless from/to say otherwise, and answers windows of up to 24 hours unless traceId pins the read. One row per trace: its root span, how long the whole trace took, how many spans it has and whether any of them failed. Filters are structured; there is no SQL surface. Page with nextCursor.

Example

Ask your agent something like this:

Search the traces of the current product, newest first.

The agent will invoke observe_traces_search with these arguments:

{}

Esc

Start typing to search the docs.

↑↓navigate↵select