v2.0.5 - Maintenance Release

Fixes:

• core: Duplicated timers data was reported when a PeriodSnapshot.Accumulator was used. This would only happen if a reporter is expecting a different tick interval size than what Core has configured so not a very common situation. Fixed by @ivantopo via kamon-io/Kamon#628.
• core: Include the error.message tag when a Span is failed with a Throwable. Fixed by @mladens via kamon-io/Kamon#625.
• core: Properly handle calls to Config.pairs when the configuration has a key with special characters in it. Fixed by @mladens via kamon-io/Kamon#624.
• akka-http: If a HTTP operation name generator is configured on the server side the instrumentation will no longer override it. Fixed by @ivantopo via kamon-io/kamon-akka-http#73.

Improvements

• common: Now it is possible to provide a custom HttpOperationNameGenerator for the HTTP Server instrumentation class (previously it was only available to the client instrumentation). This features was contributed by @pnerg via kamon-io/kamon-instrumentation-common#3.

v2.0.4 - Maintenance Release

New

• mongo: Now including the new kamon-mongo module.

Fixes

• system-metrics: A "Failed to get statvfs. Error code: 13" error was being logged by OSHI but it should have been just a warning that it was impossible to get the storage usage via statvfs, but it was still possible to get it via other mechanisms. Fixed by @ivantopo via kamon-io/kamon-system-metrics@086fc21
• system-metrics: The JVM Threads metrics were missing since the upgrade to Kamon 2.0 and they were brought back. Contributed by @ivantopo via kamon-io/kamon-system-metrics@17dcb17. The new metrics are:
  • jvm.threads.total: Tracks the current number of live threads on the JVM.
  • jvm.threads.peak: Tracks the peak live thread count since the JVM started.
  • jvm.threads.daemon: Tracks the current number of daemon threads on the JVM.

Improvements

• core: Show the right error message when a metric redefinition is attempted. Fixes kamon-io/Kamon#608 and contributed by @ivantopo via kamon-io/Kamon#106
• core: Remove unused enabled setting in the Status Page reference configuration. Contributed by @pnerg via kamon-io/Kamon#621.
• akka: Support for Akka 2.6 and Artery remoting is included in this release.

v2.0.3 - Maintenance Release

Fixes

• logback: The ContextEntryConverter wasn't picking up default values correctly. Fixed by @amelnikov-mylivn via kamon-io/kamon-logback#31.
• executors: We removed the within configuration section completely from this module, so that it will only have effect on classes when explicitly activated by other modules that add values to the within list (e.g. the JDBC and Twitter Future modules). This works together with a bugfix on Kanela v1.0.2 that makes it possible to work fine. Contributed by @ivantopo via kamon-io/kamon-executors@66e1d26.
• kanela: Improved recognition of Scala-related ClassLoaaders. Some users were unable to get Kamon instrumenting their applications because scala-compiler.jar ended up in their production classpath. The criteria to identify a ClassLoader as a Scala-related one is now: less than 6 jars and contains both jline and scala-compiler. Contributed by @ivantopo via kamon-io/kanela#94.
• kanela: Do not clear the registry after reloads. This was making it look as if instrumentation modules are not working after a Play application on Development Mode was reloaded. Fixed by @ivantopo via kamon-io/kanela@f5b6412.
• kanela: Gracefully handle modules without a within setting in their configuration. Some modules like kamon-executors only ship with the instrumentation but do not apply it unless explicitly enabled by other modules by adding to the within configuration. The default value of within was causing problems when reading the configuration which ended up applying instrumentation to almost all matching classes. Fixed by @ivantopo via kamon-io/kanela#95

v2.0.2 - Maintenance Release

Fixes

• core: Some typos regarding configure the B3 Single Header propagation for Spans on the reference configuration. This was fixed by @schrepfler via kamon-io/Kamon#598 and kamon-io/Kamon#599.
• core: It wasn't possible to start any module after Kamon.stopModules() was called. This was fixed by @ivantopo via kamon-io/Kamon#605.
• logback: The MDC is completely restored to its original state after Kamon instruments the append method. Fixed by @carstenlenz via kamon-io/kamon-logback#25.
• logback: The instrumentation was moved from interceptors to advisors to ensure that it will work properly when using the -javaagent option and the kamon bundle. Fixed by @ivantopo via kamon-io/kamon-logback#29
• akka-http: Strict entities are kept Strict when going through the server flow instrumentation. This was reported as kamon-io/kamon-akka-http#60 and fixed by @crow-fff via kamon-io/kamon-akka-http#64.
• akka-http: The HTTP Client instrumentation is now also working from the Java API. The issue was reported as kamon-io/kamon-akka-http#65 and fixed by @ivantopo via kamon-io/kamon-akka-http#66.

Improvements

• core: Include the exception thrown by histograms when recording values outside of the configured range on the logged warning messages to help with debugging. Contributed by @ivantopo via kamon-io/Kamon@cc8d5bc
• core: Thanks to @melezov we have a cleaner code base! He cleaned up several warnings in the core module via kamon-io/Kamon#600.
• executors: Depending on the order in which configuration files were loaded, some Callable/Runnable targets for instrumentation wouldn't be taken into account because the default configuration was having an absolute assignment as within = [ ]. This was fixed by @boxsterman via kamon-io/kamon-executors#19.
• logback: The README was updated to include the right class names for the utils that ship with it. Contributed by @ElfoLiNk via kamon-io/kamon-logback#27.
• akka-http: This module now supports HTTP/2! The initial request was tracked by kamon-io/kamon-akka-http#48 and fixed via kamon-io/kamon-akka-http#62.
• akka-http: @kubukoz bumped versions to the latest Akka/Akka HTTP releases via kamon-io/kamon-akka-http#63.

v2.0.1 - Maintenance Release

Fixes:

• kamon-io/Kamon#601 The instrumentation on scala.util.Try was not being applied properly when using the Kamon bundle.
• kamon-io/kamon-akka-http#57 Requests sent to routes with special characters like /path/** with throw exceptions. Fixed by @lustefaniak via kamon-io/kamon-akka-http#59 and previously by @wilaszekg via kamon-io/kamon-akka-http#55.
• kamon-io/kamon-akka-http#58 The instrumentation will now keep updating the operation name with further patch matchers unless the user explicitly sets an operation name via the operationName directive or directly calling Kamon.currentSpan().name(...). Fixed by @ivantopo via kamon-io/kamon-akka-http#61.

New Features:

• kamon-io/kamon-jdbc#22 The JDBC instrumentation now targets the latest MySQL ConnectorJ and Amazon RedShift. Thanks to @alvaroc1 for the contribution!

Changes

• The ErrorOnFailedStatement processor on the JDBC module is no longer enabled by default. This is due to the fact that most people already have a mechanism to log JDBC statement failures so most people would end up with errors being logged twice.

v2.0.0-RC1 - First Release for Kamon 2.0.0-RC1

Releasing 2.0.0-RC1