litellm - 💡(How to fix) Fix feat: Custom x- headers not captured in spend logs on Vertex AI pass-through

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

We add custom headers to our app making LiteLLM calls. The custom headers are "x-" prefixed and we use them for spend and security attribution. It works great except for Gemini pass-through — none of the headers show up in request_tags on those spend log rows.

Our custom headers work fine when we hit /chat/completions or /v1/messages (Anthropic).

This means all of our Vertex/Gemini traffic ends up unattributable to a user and makes it difficult for various downstream systems, runbooks and processes.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

litellm - 💡(How to fix) Fix feat: Custom x- headers not captured in spend logs on Vertex AI pass-through