-
Notifications
You must be signed in to change notification settings - Fork 120
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
Opentelemetry - read baggage #400
Comments
Hi 👋 The middleware actually does context propagation: https://github.com/gofiber/contrib/blob/main/otelfiber/fiber.go#L100 Can you elaborate your issue? |
In general, we have 2 applications however, i don't see this full flow via the UI might be issue with the way we configure the http client, but i'm not sure
|
Can you share screenshots? It should be enough to add otel transport to your http client. I can see in Jaeger that our applications propagates spans. |
Are you sure about every service's HTTP clients add open telemetry span in their requests? |
Hi, are there any changes needs to be done to read the telemetry baggage?
so we would have full flow between services?
currently, if call comes to the server, from a different server which is also using opentelemetry, we cannot see this relation
thanks!
The text was updated successfully, but these errors were encountered: