Dear community, yesterday Diego and Ivan had a call to discuss a bit of what we think the future of Kamon should look like and we wanted to summarize the ideas and share with the community.

In part one of the OpenTracing blog series we provided a good OpenTracing overview, explaining what OpenTracing is and does, how it works and what it aims to achieve. One of the key aspects of OpenTracing is that it is vendor neutral, and also that OpenTracing is just a specification. In order to instrument an application via OpenTracing API, it’s necessary to have an OpenTracing-compatible tracer correctly deployed and listening for incoming span requests.

Today we are announcing Kamon 1.1.0 with a couple bugfixes and a small but important improvement on context propagation, plus several minor updates on other modules that sort of went under the table for Akka, Akka Remote, Akka HTTP, Play Framework, Http4s and our sbt-aspectj-runner plugin.

Stackify’s APM+ product, Retrace, helps provide important insights into your code, and one of the important pieces to understand is the Traces view. Learn the benefits of the "traces" tab and see examples within Retrace.