6 views
-/https://github.com/berriai/litellm/issues/30956
GitHub · issue

#30956 [Bug]: OTel V2 missing message contents in traces and no events emitted when using span_and_event

  • State: open
  • Author: @danbaierlacher
  • Labels: bug, proxy, llm translation

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

I am encountering an issue where message contents (prompts and completions) are completely missing from traces when using the OpenTelemetry V2 integration.

*(Note: This might be related to #30121, which reports missing messages for Anthropic routes. However, this seems to occur globally across providers when using V2).*

### Steps to Reproduce

To isolate the issue and rule out any OTLP collector/backend limitations, I am using the `console` exporter. I also explicitly omitted `"otel"` from my `config.yaml` callbacks to avoid running V1 and V2 simultaneously.

1. Start the proxy using the official docker container image (v1.89.2) with the following environment variables: ```yaml LITELLM_OTEL_V2: "true" OTEL_EXPORTER: "console" OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT: "span_and_event"

```

2. Send a standard chat completion request to the proxy. 3. Observe the output in the console.

### Expected Behavior Based on the documentation, the console output should include the message contents either as `gen_ai.input.messages` and `gen_a…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (3 events)
#0 of 0 · 31d18h36m44s ago — entered · #import:https:::github.com:berriai:litellm post #2246
The left issue spans cross-provider observability instrumentation, event generation, semantic attributes, exporter behavior, and regression coverage. The right issue is narrower, focused on database initialization and Prisma/container compatibility.
The right issue is harder because it involves tracing instrumentation, exporter behavior, event/span semantics, configuration interactions, and cross-provider validation. The left issue appears more localized to stream termination parsing with focused regression tests.
#0 of 0 · 31d18h30m4s ago — current · #import:https:::github.com:berriai:litellm post #2358
Issue 30956 is harder because it spans the cross-cutting OTel V2 instrumentation pipeline, content capture, event generation, exporter behavior, and compatibility across providers and modes. Issue 26701 is comparatively localized to preserving an existing parameter through a few request and callback paths, with narrower regression coverage.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search