-
Notifications
You must be signed in to change notification settings - Fork 20
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
Adding opentelemety as a feature "otel" #92
Conversation
databroker/src/open_telemetry.rs
Outdated
.with_exporter( | ||
opentelemetry_otlp::new_exporter() | ||
.tonic() | ||
.with_endpoint("http://localhost:4317"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is 4317 a standard port for this type of functionality?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, It's a standard port for Jaeger backend. As Jaeger backend can also run on other device, I have made the endpoint configurable through env variable in my latest commit.
I have created a new pull request with a single signed commit including all my changes. Here is the link to my new pull request #97 |
With this feature "otel" enabled, it conditionally compiles the opentelemetry and the related tracing functionalities.