-
Notifications
You must be signed in to change notification settings - Fork 71
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
OTel Span in flagd Provider #620
Comments
Investigating connect go observability [1] |
This was referenced Apr 18, 2023
Kavindu-Dodan
moved this from In Progress
to Review
in 🔭 OFO/flagd Observability with OTel
Apr 19, 2023
Kavindu-Dodan
added a commit
that referenced
this issue
Apr 25, 2023
## This PR Partially address issue #620 Introduce connect interceptor[1] to add distributed tracing support for flagd. With interceptor and sdk tracing, we can get out of the box distributed tracing. Consider following screens, ![image](https://user-images.githubusercontent.com/8186721/232918928-c4c75290-d1fd-4021-9435-d5e079084bc7.png) ![image](https://user-images.githubusercontent.com/8186721/232918838-0dbb488b-e7df-4c42-9bd1-960879291541.png) note - follow up pr is ready at https://github.com/open-feature/go-sdk-contrib [1] - https://connect.build/docs/go/observability/ --------- Signed-off-by: Kavindu Dodanduwa <kavindudodanduwa@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The flagd provider should start an OTel span that will be passed to flagd to get cross-service tracing for evaluation.
The text was updated successfully, but these errors were encountered: