Create trace destination
Send this organization's agent traces to an OpenTelemetry backend it owns.
Every finished agentic search, chat completion, and question-answering run is converted to OTLP spans and pushed to the destination: the agent's query, the tool calls it made with their arguments and results, the model turns with their token usage, and the chunks it returned, which is the same trace the dashboard shows. Mixedbread's own internal spans are never exported.
langfuse destinations take the host and the project key pair; otlp takes a traces endpoint and its auth headers, which covers any OTLP/HTTP collector. The credentials are checked against the destination before it is stored.
Request body
Example request
{
"host": "https://cloud.langfuse.com"
}Response
The connected trace destination
Changes
Changed in 2 of the 17 revisions of this API.12
- ●
added the new
qaenum value to the/response property for the response statusresponse-property-enum-value-added
- ○
added the new
qaenum value to the request property/request-property-enum-value-added
- ●
- ○
endpoint added
endpoint-added
- ○