v2.0.3 - Shutdown correctly on Java 9+

Fixes:

• The reporter wouldn't stop properly when running on Java 9+ due to the underlying OkHttp client keeping a non-daemon thread alive. There is more info here: square/okhttp#4029. This release allows for a full shutdown by evicting all connections from the underlying pool in the stopping procedure.

v2.0.2 - Fix Gauge Range

Fixes

• As reported on #15, gauges would fail to be reported when their value was bigger than the default histogram range which defaults to 3.6e+12 (one hour in nanoseconds). This was fixed by @mladens via #16.

v1.1.5 - Fix Gauge Range

Fixes

• As reported on #15, gauges would fail to be reported when their value was bigger than the default histogram range which defaults to 3.6e+12 (one hour in nanoseconds). This was fixed by @mladens via #17.

v2.0.1 - Fix Gagues Encoding

Fixes

• Gauges were being encoded as Counters and that lead to wrong aggregations across time and different time series. Fixed by @mladens via #14

v1.1.4 - Fix Gagues Encoding

Fixes

• Gauges were being encoded as Counters and that lead to wrong aggregations across time and different time series. Fixed by @mladens via #13

v2.0.0-RC3 - Scala 2.13 and More Upgrades

This release is also built for Scala 2.13 and includes all the new Span fields that were added in Kamon 2.0 (like kind, position, wasDelayed and so on).

v2.0.0-RC2 - Fix Artifacts

In RC1 some artifacts were empty due to some build configuration issues, that was fixed on this release.

v2.0.0-RC1 - Move to Kamon 2.0.0-RC1

Nothing new, other than the upgrade to Kamon 2.0.0-RC1

v1.1.1 - Span marks support

Deprecated

Connection leak detected, please refer to v1.1.2

Span marks support

Starting with this release span marks are reported to the tracing backend

v1.1.0 - Unified Reporter, Proxy Support and Latest Kamon

Unified Reporting

Starting with this release there is no longer a metrics and spans reporter, it is just the KaminoReporter class. Users can decide whether to enable tracing or not in two ways:

via configuration in your application.conf file:

kamino.enable-tracing = yes

or via code, when creating the Kamino reporter instance:

Kamon.addRepoter(new KaminoReporter(enableTracing = true))

Tracing is enabled by default from this release.

Proxy Support

Now you can use a proxy to reach Kamino. By default the Kamino reporter will take whatever proxy configuration is set for the JVM in which it runs and you can additionally tweak the settings by configuring a HTTPS or SOCKS proxy in the configuration file:

kamino.proxy {
  # you can choose between system (default), https and socks
  type = "https"   
  host = "10.0.2.1"
  port = 443
}

Improved Logging and Checks

The reporter will no longer attempt to post metrics or spans to Kamino if no proper API key has been configured and will be logging messages when this happens, as well as letting you know if data posted to Kamino is being dropped for any reason.

Upgrade to Kamon 1.1.3

This release requires Kamon 1.1.3+. The main reason for this upgrade was that the way in which the Kamino reporter was reading Kamon's snapshots could cause a BufferUnderflowException as described in #3. Rather than patching it in the Kamino reporter we made sure that Kamon snapshots cannot be corrupted by this reporter or any other, see kamon-io/Kamon#538 for more details.