scriptoriumadmin/litellm
1
0
Fork 0
mirror of https://github.com/BerriAI/litellm.git synced 2026-10-10 03:28:53 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 85

docs(otel): state why a disabled backend still routes its own span

Browse source
This commit is contained in:
Yucheng He 2026-09-05 06:15:20 -07:00
parent 8fc2ff1f27
commit 9f871f6895
1 changed files with 5 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
litellm/proxy/litellm_pre_call_utils.py
View file

@ -1044,9 +1044,11 @@ def resolve_tenant_otel_destinations(
A backend the request disabled dynamically, through the key's
``litellm_disabled_callbacks`` or the ``x-litellm-disable-callbacks`` header in
``request_headers``, resolves to no destination: dispatch skips that callback, so
the request keeps the operator's exporters for it exactly as it did before
destinations existed.
``request_headers``, resolves to no destination, so the fan-out never carries the
request tree to that account and the operator's exporter is never suppressed for
it. That leaves the request exactly where it stood before destinations existed:
the OTel V2 logger itself is not on the disable list's class registry, so its own
span still routes to the tenant's credentials the way it did then.
"""
from litellm.integrations.otel.model.config import is_otel_v2_enabled
from litellm.integrations.otel.presets.destinations import destination_for