observe_traces_search

Tool

observe_traces_search

Search the traces of the current product, newest first.

Search the traces of the current product, newest first. 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.

Behavior

HTTP: GET /observe/traces/search

Arguments

Name	Type	Required	Description
to	string	—	Newest span start to include, ISO 8601
from	string	—	Oldest span start to include, ISO 8601
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

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:

{}