-
Notifications
You must be signed in to change notification settings - Fork 69
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
Add support for OpenTelemetry tracing #1612
Conversation
9eb39cd
to
3eda869
Compare
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.
It all made rough sense to me. I haven't done OTel specifically but looks reasonable.
Recommend others weighing in as well :)
3eda869
to
c7184bd
Compare
922ded9
to
ac0b589
Compare
ac0b589
to
9c549fe
Compare
6ee3e2f
to
9698b15
Compare
@@ -48,6 +49,7 @@ defmodule NervesHub.Deployments.Orchestrator do | |||
As devices update and reconnect, the new orchestrator is told that the update | |||
was successful, and the process is repeated. | |||
""" | |||
@decorate with_span("Deployments.Orchestrator.trigger_update") |
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.
I haven't seen this before, very cool 🤤
Adds support for:
Further work will need to be done for DeviceChannel bits
The default behavior is to trace everything, but I have added support for a percentage based sampler.
To use this with honeycomb you would configure it with:
It also interesting to note that Sentry is coming out with Elixir tracing support soon
I'd like to merge this in while I work more on the Oban OpenTelemetry PR: open-telemetry/opentelemetry-erlang-contrib#400