OTel Collector

Fan out TheRouter.ai traces to any OTLP backend through one collector

Configure a generic OpenTelemetry destination when you need maximum flexibility. This works with Axiom, Jaeger, Tempo, Honeycomb, or your own collector pipeline.

broadcast-otel-config.json

{
  "destination": "otel-collector",
  "enabled": true,
  "endpoint": "https://otel.example.com/v1/traces",
  "headers": {
    "Authorization": "Bearer otlp_token",
    "X-Tenant": "therouter"
  },
  "sampling_rate": 1
}

cURL

curl https://api.therouter.ai/v1/chat/completions   -H "Authorization: Bearer $THEROUTER_API_KEY"   -H "Content-Type: application/json"   -H "X-TheRouter.ai-Broadcast: true"   -d '{
    "model":"anthropic/claude-sonnet-4.5",
    "messages":[{"role":"user","content":"Extract action items"}],
    "trace":{"trace_name":"OTel Pipeline Test","environment":"prod"}
  }'

Endpoint must accept OTLP/HTTP

Ensure your collector listens on `/v1/traces` and accepts OTLP JSON payloads. Incorrect protocol settings are the most common setup issue.