-
Notifications
You must be signed in to change notification settings - Fork 435
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
question: Distributed tracing with contrib packages gorm and fiber #1222
Comments
Hello 👋! So if I understand correctly your service map looks like C calls A which Calls B? (C -> A -> B) In your usage of gorm are you providing the context when you make a query? e.g. Sorry this answer has been a bit slow getting to you. Feel free to also open a support ticket directly with datadog if the above doesn't help (and will ensure you get a more timely response) |
Hi there @ajgajg1134 thanks for the response. The service map looks like (C -> A ->B) correct, but I am not seeing proper propagation from C to A, nor from A to B. All I can confirm is that the required DD trace headers are been correctly sent from C to A. I'm at a loss as to what else to try. It would be really awesome if we could get correlated traces for these services. |
Hi @dominicfollett, this is tough to diagnose without seeing more code or looking at the spans themselves. I recommend you open a support ticket directly with datadog so a support agent can take a look at the spans themselves to see if it's a bug in our code somewhere or a subtle configuration issue |
Thank you @ajgajg1134 for your help all the same, I will do that. |
Hello there, I'm looking for a bit of guidance, with a caveat: that I am still learning about tracing and my use of these contrib packages is somewhat fresh to me, so I apologize in advance if any of my questions are a bit off the mark.
I have three services that are successfully reporting traces, but the traces are not correlated when they should be, and they are not 'connected' on the Datadog service map.
Services (Service C calls into A, which does a look up on B.):
I am wondering whether I need to do more than the basic setup of the contrib tracing packages. I am hoping to see correlation between C and A, and A and B.
This currently what I have:
Current fiber setup:
Gorm setup
Additionally I have set the propagation environment variables:
And I can confirm that service A is receiving the parent trace and span id's from service C on the headers:
Is it possible that I need to explicitly set the propagation style as a fibertrace middleware option or is having it set as an environment variable sufficient? And do I need to somehow pass fibertrace's span id onto the gorm tracer? And if so, how would I be able to do that? I have looked through the docs but I haven't found any examples that might help me.
Again, apologies if these question are unclear. And thank you for your help.
The text was updated successfully, but these errors were encountered: