Skip to content
This repository has been archived by the owner on Mar 29, 2020. It is now read-only.

Releases: kamon-io/kamon-play

v2.0.0-RC3 - Reloading on Dev Mode

21 Jun 13:19
Compare
Choose a tag to compare
Pre-release

Fixes

  • Do not stop modules when reloading an application on development mode. This issue was causing modules to stop after the first time an application was reloaded while running on development mode.

v2.0.0-RC2 - Client Operation Name Defaults

21 Jun 11:42
Compare
Choose a tag to compare

Changes

  • Remove a Kanela logging flag left on the reference configuration.
  • Change the default client operation name to use the HTTP method instead of host.

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

18 Jun 17:50
Compare
Choose a tag to compare
Pre-release

Highlights

HTTP Client and Server Instrumentation

Starting with this release, both the client and server instrumentations are based on the abstractions included on the kamon-instrumentation-common module, which means there are a bunch of configuration settings that can be applied to this module now!

If you want to find out just head over to the reference.conf file and see it there!

v1.1.3 - Minor Dependency Fixes

01 Apr 15:24
Compare
Choose a tag to compare

Fixes

  • Turns out that we re-introduced #38 when releasing v1.1.2, this release applies the same fix we had before (mark the dependencies as provided). This was reported by @kubukoz and fixed by @ivantopo via 044a10a

v1.1.1 - HTTP Headers Case Sensitivity and Dependencies Scope

22 Aug 06:54
Compare
Choose a tag to compare

Fixes:

  • Retrieving HTTP headers from requests was working on a case-sensitive way, starting on this release HTTP headers can be retrieved without worrying about case sensitivity. Fixed by @jtjeferreira via #21, thanks a lot!
  • It was happening that after adding this module, Play would switch to use the Netty server instead of the default AkkaHTTP server because of extra dependencies brought by this module. Now all Play-related dependencies are marked as provided. Fixed by @ivantopo via b36a064

v1.1.0 - Netty Server and Scala 2.11 Support for Play 2.6

22 Apr 18:32
Compare
Choose a tag to compare

Netty Server and Scala 2.11 Support

As of this version the instrumentation is able to handle HTTP requests using both the Netty and Akka HTTP Backends (only Akka HTTP was supported for Play 2.6).

Further more, this new version publishes an artifact for the Play 2.6/Scala 2.11 combination which was lacking before.

Thanks a lot to all contributors!

Improvements:

  • Instrumentation for the Netty server. Contributed by @chtefi on #19. Special thanks to @dpsoft and @jsw for helping on the review.
  • Support for Scala 2.11. Contribued by @dpsoft on #25 and further improved by @jtjeferreira on #27.
  • Tests now cover both the Netty and Akka HTTP backends. Contributed by @jtjeferreira on also on #27.

Fixes:

  • #28 WSClient instrumentation was running twice when a request filter was added to the requests. Reported by @jsw and fixed by @ivantopo on #32.

v1.0.2 - Context Propagation Fix

04 Mar 22:44
Compare
Choose a tag to compare

Fixes:

  • For Play 2.5 and 2.6 parts of the incoming context would be lost because the instrumentation was always creating a new Context instance that would only have the newly created Span inside, dropping any other context keys that might have been extracted from HTTP headers. Fixed by @ivantopo in #15.

v1.0.1 - Minor bugfix

27 Jan 11:56
Compare
Choose a tag to compare

Fixes:

  • As a convention, we are always adding the span.kind=server tag to both metrics and spans for all automatically generated on the HTTP server side, but it was only being added on the span, fixed by @dpsoft in 3732c9a