Skip to main content
Inspector

Get Traces

Get actor trace spans in OTLP JSON format.

The inspector API powers the Rivet dashboard and is subject to change without notice. Do not build production integrations on it.

Trace collection is not implemented yet, so this route currently returns an empty result.

GET https://api.rivet.dev/gateway/{actor}/inspector/traces

Examples

Authentication

Inspector endpoints do not accept namespace tokens. Send the actor’s inspector token as a bearer token in the Authorization header. Each actor generates its own inspector token on first start and stores it in its KV storage under the single byte 0x03. Read it through the control plane with GET /actors/{actor_id}/kv/keys/Aw==?namespace={namespace} using a namespace token; the response value is the token, base64-encoded. The dashboard does this for you.

Path Parameters

NameTypeRequiredDescription
actorstringYesActor ID, actor ID with an inline token ({actor_id}@{token}), or actor name combined with the rvt-* query parameters.

Query Parameters

NameTypeRequiredDescription
startMsintegerNoStart of time range in epoch milliseconds
endMsintegerNoEnd of time range in epoch milliseconds. Defaults to now.
limitintegerNoMaximum number of spans to return

Headers

NameTypeRequiredDescription
AuthorizationstringNoBearer token for inspector authentication. Required in production, optional in development.

Actor Selector

{actor} accepts an actor ID, an actor ID with an inline routing token ({actor_id}@{token}), or an actor name combined with the rvt-* query parameters below. See Actor Routing for the full rules.

Responses

200

Trace data and whether the requested range was clamped.

FieldTypeDescription
otlpobject
clampedboolean
{
  "otlp": {},
  "clamped": false
}

401

The inspector token is missing or invalid.