Replies: 2 comments 1 reply
-
Yes, Kamon will support OpenTelemetry for sure! As you pointed out already, there are only two things we need to get done:
We don't have a clear timeline for it because we are pretty tight on time these days, but it is definitely in the near term roadmap. |
Beta Was this translation helpful? Give feedback.
1 reply
-
For completeness I refer to the ticket created on the subject #973, should anyone stumble on this conversation in the future |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been trying to find any discussion related to OpenTelemetry and whether Kamon intends to support it.
I'm assuming this PR (#949) needs to be in place first.
I.e. the support for W3C context propagation as it would allow a trace to flow without locking in to e.g. Zipkin B3 headers.
Kamon supports among other things Zipkin/Jaeger as trace exporters, it should be possible to have a OpenTelemetry exporter.
This would allow for vendor agnostic approach for traces. The number of APM's supporting OpenTelemetry is growing and I'd prefer to use a standard to export my traces rather than vendor locked in protocols.
Using Kamon for the instrumentation and letting it do the context propagation (w3c) and trace reporting (otlp) would be a nice setup imho.
Beta Was this translation helpful? Give feedback.
All reactions