[Bug]: OpenTelemetry endpoint environment variable is incorrect

[edwarddamato]

What happened?

The OpenTelemetry documentation for HTTP and GRPC collectors refers to using the OTEL_EXPORTER_OTLP_ENDPOINT env var. As this is used to then log traces to OpenTelemetry, I believe this should actually use the OTEL_EXPORTER_OTLP_TRACES_ENDPOINT env var as per OpenTelemetry's docs.

Both OTLPSpanExporterGRPC and OTLPSpanExporterHTTP classes expect the /v1/traces env var to be present first, so LiteLLM should expect this as well.

Happy to open a PR for this, but I'd like to hear what others think first.

Relevant log output

Are you a ML Ops Team?

No

What LiteLLM version are you on ?

v1.75.9-nightly

Twitter / LinkedIn details

No response

[superpoussin22]

langfuse is using OTEL_EXPORTER_OTLP_ENDPOINT

[edwarddamato]

langfuse is using OTEL_EXPORTER_OTLP_ENDPOINT

@superpoussin22 the LiteLLM implementation uses OTLPSpanExporterGRPC and OTLPSpanExporterHTTP and they both expect OTEL_EXPORTER_OTLP_TRACES_ENDPOINT. See https://github.com/open-telemetry/opentelemetry-python/blob/ade1058f0aa3e383480607c2279bb3170732c7ec/exporter/opentelemetry-exporter-otlp-proto-grpc/src/opentelemetry/exporter/otlp/proto/grpc/trace_exporter/__init__.py#L128