Can I use kamon tracing in other async framework?

[tutu...@gmail.com]

For example, I may choose to use vertx.io which is java based.
Shall I need to create extensions like kamon-play, kamon-akka?

Thanks
Leon

[Ivan Topolnjak]

Hey Leon, 

You can use Kamon on any JVM language and framework combination you want. The APIs in kamon-core should be enough for you to get metrics and tracing working and all the guidelines with regards to how to create and propagate a trace context are described in the docs [1]. Please go ahead and experiment and let us know how it goes, regards!

[1]: http://kamon.io/documentation/kamon-core/0.6.6/tracing/trace-context-manipulation/

[tutu...@gmail.com]

在 2017年5月3日星期三 UTC-7上午1:12:32，Ivan Topolnjak写道：

> Hey Leon, 
>
>
> You can use Kamon on any JVM language and framework combination you want. The APIs in kamon-core should be enough for you to get metrics and tracing working and all the guidelines with regards to how to create and propagate a trace context are described in the docs [1]. Please go ahead and experiment and let us know how it goes, regards!
>
>
>
>
> [1]: http://kamon.io/documentation/kamon-core/0.6.6/tracing/trace-context-manipulation/

Thanks a lot!

[tutu...@gmail.com]

在 2017年5月3日星期三 UTC-7上午1:12:32，Ivan Topolnjak写道：

> Hey Leon, 
>
>
> You can use Kamon on any JVM language and framework combination you want. The APIs in kamon-core should be enough for you to get metrics and tracing working and all the guidelines with regards to how to create and propagate a trace context are described in the docs [1]. Please go ahead and experiment and let us know how it goes, regards!
>
>
>
>
> [1]: http://kamon.io/documentation/kamon-core/0.6.6/tracing/trace-context-manipulation/

Hi, Ivan

Does Kamon follow open tracing spec?

What's the different between kamon and zipkin (or Jaeger) regarding on tracing part?

Thanks
Leon

[Ivan Topolnjak]

It doesn't follow it now, but we are currently working on some enhancements for Kamon that include making our tracer OpenTracing compliant. Currently working on top of a snapshot from this PR: https://github.com/opentracing/opentracing-java/pull/115, but that should be merged today and published sometime soon. Expect our first implementation of the tracer to be out for testing soon after!

I'm not sure about comparing Kamon with Zipkin/Jaeger.. those are complete solutions for distributed tracing that have both a client library and a full featured backend for storing, querying and visualizing the tracing data. In it's current state Kamon is a lot more biased towards recording highly detailed metrics collection and being backend agnostic. One of the goals we have on our new tracer implementation is to ship with a Zipkin and/or Jaeger reporter so that you should be able to use the Kamon tracer (and thus, take advantage of all the integrations we already have) and report the data to whatever backend you want. 

Probably I'll have a better answer for this comparison once we get the new tracer out :), stay tuned! I will ping you when we have some working version that could be tried out, regards!

[tutu...@gmail.com]

在 2017年5月4日星期四 UTC-7上午5:33:30，Ivan Topolnjak写道：

> It doesn't follow it now, but we are currently working on some enhancements for Kamon that include making our tracer OpenTracing compliant. Currently working on top of a snapshot from this PR: https://github.com/opentracing/opentracing-java/pull/115, but that should be merged today and published sometime soon. Expect our first implementation of the tracer to be out for testing soon after!
>
>
> I'm not sure about comparing Kamon with Zipkin/Jaeger.. those are complete solutions for distributed tracing that have both a client library and a full featured backend for storing, querying and visualizing the tracing data. In it's current state Kamon is a lot more biased towards recording highly detailed metrics collection and being backend agnostic. One of the goals we have on our new tracer implementation is to ship with a Zipkin and/or Jaeger reporter so that you should be able to use the Kamon tracer (and thus, take advantage of all the integrations we already have) and report the data to whatever backend you want. 
>
>
> Probably I'll have a better answer for this comparison once we get the new tracer out :), stay tuned! I will ping you when we have some working version that could be tried out, regards!

Cool! Thanks for the explanation!