Closed aloababa closed 4 days ago
is this with OTEL @aloababa ? So when you pass a traceparent header in the request -> litellm should add the traceparent header in the response
Yes this is with OTEL, it successfully parse the Traceheader if there is one in the request so i can link my trace from frontend to LiteLLM, but after this Traceparent header is not forwarded to the backend (vllm) so my trace stops at LiteLLM and i got a new trace for vllm that is not linked to it.
got it -> so if a traceparent is in the request header -> we should forward this to vLLM ?
fix here @aloababa https://github.com/BerriAI/litellm/pull/4423
I can see it forwards the traceparent to the provider
@aloababa any chance we can hop on a call ? I'd love to learn how how we can improve litellm for you.
I reached out to you on Linkedin if DMs work. Sharing a link to my cal for your convenience: https://calendly.com/d/4mp-gd3-k5k/litellm-1-1-onboarding-chat
Thank you very much for your reactivity. It works well if i provide the Traceparent header in the request to LiteLLM. Is it also possible that you forward the Traceparent header even if the Traceparent header is not provided in the original request ? so you put the trace id generated by the LiteLLM otel integration in the Traceparent header.
What happened?
It seems that the Traceparent header is not forwarded to backends (vllm) when proxying with LiteLLM. It would be nice if it can be forwarded to the backends so the backend traces can have the LiteLLM traces as parent.
Relevant log output
Twitter / LinkedIn details
No response