v0.16.0

What's Changed

• Breaking: upgrade to opentelemetry version 0.30
• add development README by @francoposa in #25

Full Changelog: v0.15.0...v0.16.0

v0.15.0

What's Changed

• Feat: custom metric attributes via request/response extractors by @tomharmon in #24

Full Changelog: v0.14.0...v0.15.0

v0.14.0

What's Changed

• Breaking: upgrade to opentelemetry version 0.29
• examples: stop pulling in rt-tokio feature by @flokli in #22

Full Changelog: v0.13.0...v0.14.0

v0.13.0

What's Changed

• Breaking: Changes to http.server.request.duration buckets
  • change default bucket boundaries to capture longer requests - this part likely does not break most things, but consumers with request durations > 10 seconds will see new, higher values in their upper percentiles for this histogram.
  • update constructor to allow consumers to override bucket boundaries - constructor now more closer follows builder pattern of other OTEL libraries
• Breaking: implement http.server.response.body.size metric - in order to do this, the response body is now constrained to http_body::Body. This should not cause problems for the vast vast majority of cases, but the response body type was previously unconstrained.

Full Changelog: v0.12.0...v0.13.0

v0.12.0

• Breaking: Upgrade to axum version 0.8
  • The latest axum is a significant breaking change as noted in the announcement blog. For consumers of this library, this affects the axum MatchedPath extractor used to determine the http.route label when applying this middleware to an axum server. - Using version 0.11.x of this middleware (which uses axum 0.7) with an axum 0.8 server will not extract the http.route label, and vice versa for the reverse version mismatch.

Full Changelog: v0.11.0...v0.12.0

v0.11.0

What's Changed

• upgrade to opentelemetry version 0.28 by @flokli in #17
• add network.protocol.name and network.protocol.versionattributes tohttp.server.request.body.size` metric
• impl Default trait for HTTPMetricsLayerBuilder (using pre-existing default method).

Full Changelog: v0.10.0...v0.11.0

v0.10.0

v0.10.0 is stamped to be compatible with opentelemetry dependencies version 0.27

Thanks & credit to @flokli for the contribution

v0.9.0

v0.9.0 is stamped for:

• addition of http.server.active_requests and http.server.request.body.size
• Breaking: fixing explicit bucket boundaries on http.server.request.duration histogram after the OTEL units changed from ms to s
• add OTEL spec metric names and units to instrument descriptors

Thanks & credit to @hardbyte for the contributions.

v0.8.0

v0.8.0 is stamped to be compatible with the opentelemetry dependency version 0.26

v0.7.1

v0.7.1 is stamped to be compatible with the tower version 0.5

not bumping the minor version because I have not been able to find any incompatibilities in the tower 0.4 -> 0.5 upgrade that are utilized by this library

note: opentelemetry 0.25 libraries still use tonic 0.12 which is still utilizing tower 0.4, so this may result in multiple tower versions in your dependency tree