Skip to content

feat(telemetry): propagate X-Qwen-Code-Session-Id on outbound LLM requests (part 2 of #4384) #4393

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
doudouOUC wants to merge 2 commits into from
Closed

feat(telemetry): propagate X-Qwen-Code-Session-Id on outbound LLM requests (part 2 of #4384) #4393

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0f5fb5a
feat(telemetry): propagate X-Qwen-Code-Session-Id on outbound LLM req…
doudouOUC May 21, 2026
a11b5f6
fix(telemetry): harden OTLP feedback-loop guard + slim lockfile diff
doudouOUC May 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 37 additions & 0 deletions docs/developers/development/telemetry.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -291,6 +291,43 @@ URLs matching the configured `telemetry.otlpEndpoint` /
`telemetry.otlpMetricsEndpoint` prefixes. In file-outfile mode there are no
outbound HTTP uploads, so the hook is a no-op.

### Session correlation header

Alongside `traceparent`, Qwen Code injects a custom HTTP header on every
outbound LLM request when telemetry is enabled:

```
X-Qwen-Code-Session-Id: <session id>
```

Pattern matched from Claude Code's `X-Claude-Code-Session-Id` (see
`src/services/api/client.ts:108` in the claude-code repo). The header is
product-namespaced to avoid collision with generic `X-Session-Id` headers
other tools may inject. Server-side ingestion (e.g. a custom DashScope
proxy or an OTLP-aware API gateway) can use this header to stitch its
observation of an LLM request back to the originating Qwen Code session
without having to parse trace context.

The header value comes from `Config.getSessionId()`, read fresh on every
outbound request (not captured at SDK construction time). After a session
reset triggered by `/clear`, subsequent LLM requests carry the new session
id automatically — see the "Known limitation" note below for the one
exception.

Empty session ids are not emitted (some HTTP middleware rejects empty
header values). The header is omitted entirely when telemetry is disabled.

**Known limitation: Gemini provider.** `@google/genai`'s `HttpOptions`
interface does not expose a `fetch` hook (only static `headers`), so the
Gemini provider can only inject the session-id header at SDK construction
time. After a `/clear`-triggered session reset, outbound Gemini requests
carry the OLD session id in `X-Qwen-Code-Session-Id` until the underlying
content generator is recreated (the current code does not recreate it on
reset). All other providers (`openai`-family, `anthropic`) use a fetch
wrapper and are immune to this. Tracked as a follow-up; in the meantime,
spans and logs still carry the live session id, so trace/log backends can
correctly attribute requests to the new session.

## Aliyun Telemetry

### Manual OTLP Export
Expand Down
Loading