litellm/ui
mrinal 4a92e3055f feat(otel v2): per-destination otel_internal_spans to hold back the proxy's SERVICE and DB_CALL spans from tenant exporters
A key or team that points langfuse_otel, arize, weave_otel or newrelic at its own account can now set
otel_internal_spans to exclude, and the TenantFanOutSpanProcessor stops forwarding the proxy's own auth,
Redis, Postgres and spend-write spans to that destination. The request root and the tenant's model, guardrail
and MCP spans still go, and the operator's exporter still receives the full tree. The default stays include,
with litellm_settings.otel_tenant_internal_spans (or LITELLM_OTEL_TENANT_INTERNAL_SPANS) as the system-wide
default for destinations that name no value. The team and key Logging Settings forms render the field as a
select; the global Add Callback form does not, since the operator exporter cannot honour it.

Resolves LIT-8245

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
2026-09-22 22:46:34 +00:00
..
litellm-dashboard feat(otel v2): per-destination otel_internal_spans to hold back the proxy's SERVICE and DB_CALL spans from tenant exporters 2026-09-22 22:46:34 +00:00
Dockerfile fix(docker): bump nginx runtime to 1.31.5-alpine3.24 and pin digest to resolve critical CVEs (#39561) 2026-09-03 08:46:07 -07:00
nginx.conf fix(ui): boot the UI image as an arbitrary uid by anchoring nginx writes under /tmp (#37982) 2026-08-24 11:57:36 -07:00