Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: Proxy server should fix OpenTelemetry span kind #7298

Open
stevapple opened this issue Dec 18, 2024 · 0 comments
Open

[Feature]: Proxy server should fix OpenTelemetry span kind #7298

stevapple opened this issue Dec 18, 2024 · 0 comments
Labels
enhancement New feature or request mlops user request

Comments

@stevapple
Copy link

stevapple commented Dec 18, 2024

The Feature

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

@stevapple stevapple added the enhancement New feature or request label Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request mlops user request
Projects
None yet
Development

No branches or pull requests

1 participant