You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Correctly mark the "Received Proxy Server Request" span as SpanKind.SERVER, and optionally trace each downstream calls with a SpanKind.CLIENT OpenTelemetry span.
Motivation, pitch
In most OpenTelemetry systems, only "server" and "client" spans are considered as the starting point of a program. Currently LiteLLM Proxy Server emits all spans as "internal", which makes it dropped or hidden from the UI without explicit trace parent.
Marking the entry points (http receive) as server and the suspension points (http request) as client should resolve the problem.
Are you a ML Ops Team?
Yes
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered:
The Feature
Correctly mark the "Received Proxy Server Request" span as
SpanKind.SERVER
, and optionally trace each downstream calls with aSpanKind.CLIENT
OpenTelemetry span.Motivation, pitch
In most OpenTelemetry systems, only "server" and "client" spans are considered as the starting point of a program. Currently LiteLLM Proxy Server emits all spans as "internal", which makes it dropped or hidden from the UI without explicit trace parent.
Marking the entry points (http receive) as
server
and the suspension points (http request) asclient
should resolve the problem.Are you a ML Ops Team?
Yes
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: