kamon-io / kamon-scala   0.6.7

Website GitHub

Kamon Scala Integration

Scala versions: 2.12 2.11 2.10

Scala Integration

Build Status Gitter Maven Central

Getting Started

Kamon scala module is currently available for Scala 2.10, 2.11 and 2.12.

Supported releases and dependencies are shown below.

kamon-scala status jdk scala akka
0.6.7 stable 1.7+, 1.8+ 2.10, 2.11, 2.12 2.3.x, 2.4.x

To get started with SBT, simply add the following to your build.sbt file:

libraryDependencies += "io.kamon" %% "kamon-scala" % "0.6.7"

Automatic TraceContext Propagation with Futures

The kamon-scala module provides bytecode instrumentation for both Scala, Scalaz and Twitter Futures that automatically propagates the TraceContext across the asynchronous operations that might be scheduled for a given Future.

The kamon-scala module require you to start your application using the AspectJ Weaver Agent. Kamon will warn you at startup if you failed to do so.

Future's Body and Callbacks

In the following piece of code, the body of the future will be executed asynchronously on some other thread provided by the ExecutionContext available in implicit scope, but Kamon will capture the TraceContext available when the future was created and make it available while executing the future's body.

Tracer.withNewContext("sample-trace") {
    // The same TraceContext available here,

    Future {
      // is available here as well.
      "Hello Kamon"

      .flatMap(len => Future(len.toString))
      .map(s => Tracer.currentContext)
      // And through all async callbacks, even while
      // they are executed at different threads!

Also, when you transform a future by using map/flatMap/filter and friends or you directly register a onComplete/onSuccess/onFailure callback on a future, Kamon will capture the TraceContext available when transforming the future and make it available when executing the given callback. The code snippet above would print the same TraceContext that was available when creating the future, during it's body execution and during the execution of all the asynchronous operations scheduled on it.