traces

Search traces (TraceQL, or the filter params)

Find traces: the platform emits one per node provision (queued → provisioning → ready) and one per job lifecycle (build, queue wait, each attempt) with zero setup - boot-phase and queue-wait diagnoses become a waterfall instead of snapshot archaeology - and your own OTLP spans land beside them. Filter by mission / run / min_duration for the common case, or pass full TraceQL. Returns trace summaries; get_trace fetches the span tree.

post/preview/traces/queries

Request

  • Base URL: https://autoresearch.sfcompute.com
  • URL: https://autoresearch.sfcompute.com/preview/traces/queries
  • Auth: HTTP bearer

Query parameters

workspacestring

Act in this workspace (its slug). Omitted: the token's bound workspace, then the organization's default. Never ambient - there is no switch-workspace mutation on this door.

Request body

endstring nullable

Range end, RFC3339 (default: now).

limitinteger nullable

Max traces returned (default 20, cap 100).

min_durationstring nullable

Filter: minimum total trace duration, e.g. "5s", "500ms".

missionstring nullable

Filter: mission name.

querystring nullable

Full TraceQL (optional - the filter params below compose the query for the common case), e.g. { resource.mission = "x" } | count() > 2.

runstring nullable

Filter: one run - a job-/cmd-/ses- scope id.

startstring nullable

Range start, RFC3339 (default: one hour before end).

Response

The capability's JSON result.

objectstring

The resource type, when the result is one resource.

Changes

No recorded changes to this operation across all 1 revision of this API.