Search Traces
const url = 'https://example.com/observability/v1/workspaces/example/engines/example/traces:search';const options = { method: 'POST', headers: {'Content-Type': 'application/json'}, body: '{"workspace":"example","engine":"example","query":"example","start":"2026-04-15T12:00:00Z","end":"2026-04-15T12:00:00Z","page_size":1,"page_token":"example","filter":"example","order_by":"example","organisation":"example"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/observability/v1/workspaces/example/engines/example/traces:search \ --header 'Content-Type: application/json' \ --data '{ "workspace": "example", "engine": "example", "query": "example", "start": "2026-04-15T12:00:00Z", "end": "2026-04-15T12:00:00Z", "page_size": 1, "page_token": "example", "filter": "example", "order_by": "example", "organisation": "example" }'Searches for traces matching an expression within a window.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The workspace whose telemetry is queried, or ’-’ for an organisation-wide query across
every workspace under organisation the caller may read (AIP-159; read-only).
The provider: qibdo, aws, gcp, or azure.
Request Body required
Section titled “Request Body required ”SearchTracesRequest
Request for SearchTraces.
object
The workspace whose telemetry is queried, or ’-’ for an organisation-wide query across
every workspace under organisation the caller may read (AIP-159; read-only).
The provider: qibdo, aws, gcp, or azure.
The native trace search expression (TraceQL for the qibdo engine).
Start of the query window (inclusive).
End of the query window (exclusive).
Maximum traces per page.
A page token from a previous SearchTraces call.
AIP-160 filter expression.
AIP-132 order_by expression.
The organisation to federate across when workspace is ’-’. Required (and authorized at
organisation scope) for an organisation-wide query; ignored for a single-workspace query.
Example generated
{ "workspace": "example", "engine": "example", "query": "example", "start": "2026-04-15T12:00:00Z", "end": "2026-04-15T12:00:00Z", "page_size": 1, "page_token": "example", "filter": "example", "order_by": "example", "organisation": "example"}Responses
Section titled “ Responses ”OK
SearchTracesResponse
Response for SearchTraces.
object
The matching traces.
Trace
A full distributed trace.
object
The trace id.
The spans that make up the trace.
TraceSpan
A single span within a trace.
object
The span id.
The parent span id; empty for the root span.
The service that produced the span.
The operation the span represents.
When the span started.
How long the span took.
The continuation cursor, empty when this is the last page.
The provider that served the query.
Example
{ "engine": "ENGINE_UNSPECIFIED"}default
Section titled “default ”Default error response
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.
Example generated
{ "code": 1, "message": "example", "details": [ { "@type": "example" } ]}