Ingest OTLP traces
Ingest OpenTelemetry trace data and associate it with a simulation output or a monitoring conversation.
The request body must be a standard OTLP ExportTraceServiceRequest,
in protobuf binary (application/x-protobuf, the default for stock
OTLP HTTP exporters) or JSON (application/json) format. See the
OTLP/HTTP specification
and opentelemetry-proto
for the wire format.
Identify the target by providing exactly one of X-Simulation-Id or
X-Conversation-Id (not both).
Authorizations
Organization API key for authentication
Headers
Simulation output ID to associate the spans with. Use for
simulation-based flows. Mutually exclusive with X-Conversation-Id.
Conversation (Run) ID returned by POST /v1/conversations:submit.
Use for monitoring flows. Mutually exclusive with X-Simulation-Id.
Body
OTLP ExportTraceServiceRequest payload — protobuf or JSON.
OTLP/HTTP protobuf-encoded ExportTraceServiceRequest. This
is the default content type emitted by the OpenTelemetry HTTP
exporter (opentelemetry-exporter-otlp-proto-http).