Replies: 1 comment
-
|
Seems to be a problem with the propagation on the ADK api server side. With the following code hacked into I get the following output: If I'm not mistaken, the fact that the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm trying to get distributed tracing working between the ADK api server and a client application of the api server.
The client application is sending the traceparent header, and it is being received in the run_sse endpoint of the api server. I know this is working, because I have modified the adk_web_server.py code to print the fastapi headers and I see the traceparent header.
I have enabled OTel data to the Google Cloud Observability services via the
adk api_server --otel_to_cloudflag.I also have these env vars set:
The traces from both the client application and the adk api server are being received in Google Cloud Tracing, but unfortunately the Trace IDs are different between the client and server services, so the waterfall charts are not complete.
Does ADK api server not respect the traceparent header? Or am I missing some configuration to make this work?
Beta Was this translation helpful? Give feedback.
All reactions