Export OpenDunes traces and metrics to any OTLP-compatible backend via an OpenTelemetry Collector.
Not yet available. This destination is on the roadmap.
The OpenTelemetry Collector destination lets you export OpenDunes telemetry in the OpenTelemetry Protocol (OTLP) to any compatible backend — Jaeger, Zipkin, Tempo, a vendor-hosted collector, or your own pipeline. It is the most flexible broadcast destination for teams that already run an OTEL-based observability stack.
OpenDunes emits each request as an OTLP trace span with the following attributes:
| Attribute | Value |
|---|---|
gen_ai.system | opendunes |
gen_ai.request.model | model slug, e.g. google/gemini-2.5-pro |
gen_ai.usage.input_tokens | prompt token count |
gen_ai.usage.output_tokens | completion token count |
opendunes.cost_micro_da | DA cost |
opendunes.request_id | X-Request-Id UUID |
Custom metadata fields from the request are attached as additional span attributes.
Once available, configure the OpenTelemetry Collector destination from your dashboard under Broadcast. You will need:
https://otel.example.com:4318)grpc or http/protobufBack to Broadcast overview.