Replies: 1 comment 5 replies
-
@FanneYang - You should see 3 spans (same traceId) (one for each, httpClient, SqlClient and Kafka(assuming it creates one)). All three of them should be linked to a parent span which will be created during incoming request (AddAspNetCoreInstrumentation()). Would recommend to use just these 4 instrumentations first and confirm if you are seeing the behavior noted above. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Team,
We are running a micro-service with three major functions - receive HTTP Client call, interact with Database (read/write) and also publish a Kafka message if write action to database is successful.
We add below code to add HttpClientInstrumentation, SqlClientInsstrumentation and ConfluentKafkaInstrumentation. We are able to see traces however they are separated without parent id linkage (so for one http call and the db connection/kafka message triggered by that http call, we have 3 traces instead of 1). Wonder if there is a way to link those traces as a whole instead of break apart?
Thanks a lot for helping!
Beta Was this translation helpful? Give feedback.
All reactions