FruxonDocs
AgentsExecution Records

Gets the execution trace in OTLP/HTTP JSON format.

Returns the trace as an `ExportTraceServiceRequest` compatible with the OpenTelemetry Collector, Jaeger, Grafana Tempo, and other OTLP-compatible backends.

GET
/v1/tenants/{tenant}/agents/{agent}/executionRecords/{executionRecord}/otlpTrace

Authorization

Bearer
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

agent*string

The unique identifier of the agent.

executionRecord*string

The execution record identifier.

tenant*string

The tenant identifier

Response Body

curl -X GET "https://api.fruxon.com/v1/tenants/string/agents/string/executionRecords/string/otlpTrace"
{
  "resourceSpans": [
    {
      "resource": {
        "attributes": []
      },
      "scopeSpans": []
    }
  ]
}
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

Gets the summary record for a single execution.

Returns the same ExecutionTraces.AgentExecutionRecordResponse shape every item in the list endpoint carries — start/end times, status, token counts, cost breakdown — just for one specific record id. Cheap follow-up to a streaming run: SSE emits the `executionRecordId` in the final `done` event so callers can fetch the canonical summary by id without paging through history.

Gets the execution trace projected at read time from the raw OTel spans archived during ingest.

Rebuilds the step tree from the execution's stored raw spans with the current trace mapper, so mapper improvements reach existing executions without a re-run. Returns a `rawSpanCount` of 0 and no traces when the execution produced no OpenTelemetry spans (native agents, or external runs that emitted none); use `/trace` in that case.