v2.0.3 - Keep HTTP Server Operation Names

Fixes

• If a HTTP operation name generator is configured on the server side the instrumentation will no longer override it. Fixed by @ivantopo via #73.

v1.1.3 - Keep Custom Name Operations

Fixes

• Keep any operation name assigned via a custom operation name generator. Previously the Path Directives instrumentation would override any user-provided name. Fixed by @ivantopo via #69.

v2.0.2 - Support for HTTP/2

Fixes

• Strict entities are kept Strict when going through the server flow instrumentation. This was reported as #60 and fixed by @crow-fff via #64.
• The HTTP Client instrumentation is now also working from the Java API. The issue was reported as #65 and fixed by @ivantopo via #66.

Improvements

• This module now supports HTTP/2! The initial request was tracked by #48 and fixed via #62.
• @kubukoz bumped versions to the latest Akka/Akka HTTP releases via #63.

v2.0.1 - Maintenance Release

Fixes:

• #57 Requests sent to routes with special characters like /path/** with throw exceptions. Fixed by @lustefaniak via #57 and previously by @wilaszekg via #55.
• #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 #61.

v2.0.0-RC3 - Fix Server Response Headers

Fixes

• Any custom headers added in the responses would be overwritten by Kamon's headers, that was fixed on this release.

v2.0.0-RC2 - Future Directives Instrumentation

Fixes

• Triggers operation name resolution (and, as a side effect, taking a sampling decision) when a request hits any of the FutureDirectives. We are doing this because one of the most common uses of FutureDirectives is to grab call external system for authentication or getting data that is actually useful for request processing, which would probably be traced as well and we need to have both a sampling decision and operation name at this point.
• Include instrumentation for FastFuture, which is used in several places on the default directives. This instrumentation ensures that the Context of the original Futures will be kept when turning it into a FastFuture.
• 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

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.2 - Path Matchers Instrumentation

Improvements

• This release ships with automatic instrumentation for the Path matchers, which can automatically convert a path like "/users/1234/documents/5678" into "/users/{}/documents/{}" as the default operation name. This is critical to avoid having high cardinality operation names and has been tested for a few months already. Contributed by @mladens via #45

v1.1.1 - Minor Fixes and Improved Server Span Finishing

Fixes

• The instrumentation not treating HTTP headers in a case insensitive manner which was causing issues joining distributed traces. This was fixed by @hughsimpson via #38.

Improvements

• Server spans are now finished when the entity data has been transferred to the client (previously it was finished when the response headers were ready). Contributed by @Falmarri via #37.

v1.1.0

New Features:

• Allow adding HTTP status codes as metric tags on both client and server sides. Contributed in #28 by @ptrlaszlo. This requeres kamon-io/Kamon#513 to be fixed first.