10 views
-/https://github.com/berriai/litellm/issues/34758
GitHub · issue

#34758 [Bug]: Bedrock tool_config cache injection point invisible in logging callbacks (Langfuse) — only message-level cache_control is logged

  • State: open
  • Author: @urainshah
  • 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?

When using Bedrock prompt caching with a tool-level cache injection point (cache_control_injection_points with location: "tool_config", see [LiteLLM docs — Anthropic Cache Control (Bedrock)](vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/workbench.html)), the cache marker is correctly sent to Bedrock — confirmed by real [cache_creation_input_tokens](vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/workbench.html) and [cache_read_input_tokens](vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/workbench.html) values in the API response, and this matches Bedrock's documented request format for caching tool definitions (see [AWS Bedrock — Prompt caching, "tools checkpoints" example](vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/workbench.…

GitHub resolver

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

Refresh page
vote history (2 events)
#0 of 0 · 31d18h15m20s ago — entered · #import:https:::github.com:berriai:litellm post #2581
The left issue is harder because it requires tracing provider-specific cache metadata through request transformation and callback/logging serialization while preserving existing observability behavior. The right issue appears narrower and more environment-specific, with likely limited diagnostic or configuration changes.
#0 of 0 · 31d18h45s ago — current · #import:https:::github.com:berriai:litellm post #2833
34076 requires cross-cutting authentication, configuration, dynamic loading, endpoint integration, compatibility, and security-focused testing, while 34758 is a narrower data-propagation and callback-observability fix within an existing provider path.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search