Currently, venator collects traces on the route /v1/trace:
|
.route("/tracing/v1", post(self::tracing::post_tracing_handler)) |
|
.route("/v1/logs", post(self::otel::post_otel_logs_handler)) |
|
.route("/v1/metrics", post(self::otel::post_otel_metrics_handler)) |
|
.route("/v1/trace", post(self::otel::post_otel_trace_handler)) |
But for http/protobuf/http/json, the path should be /v1/traces1
So users setting OTEL_EXPORTER_OTLP_ENDPOINT to localhost:8362 will not see traces using either protocols, unless they set OTEL_EXPORTER_OTLP_TRACES_ENDPOINT manually (different per proto).
Currently, venator collects traces on the route
/v1/trace:venator/venator-app/src-tauri/src/ingress/mod.rs
Lines 145 to 148 in 311f674
But for
http/protobuf/http/json, the path should be/v1/traces1So users setting
OTEL_EXPORTER_OTLP_ENDPOINTtolocalhost:8362will not see traces using either protocols, unless they setOTEL_EXPORTER_OTLP_TRACES_ENDPOINTmanually (different per proto).Footnotes
see OpenTelemetry OTLP spec and SDK - OTLP Exporter Configuration doc ↩