Skip to content

Releases: micrometer-metrics/tracing

v1.0.0-M3

15 Mar 22:02
v1.0.0-M3
d6a923d
Compare
Choose a tag to compare
v1.0.0-M3 Pre-release
Pre-release

This release of Micrometer Tracing depends on micrometer-core:2.0.0-M3, you can find the documentation here.

  • Added more assertions and tests
  • Move micrometer-tracing to micrometer-tracing-api #7
  • Make integration tests take in micrometer-test #8
  • Use non blocking queue for ArrayListSpanProcessor
  • Align with the latest micrometer changes
  • Update OTel to 1.12.0 and Instrumentation to 1.11.1 #10

v1.0.0-M2

15 Feb 08:49
Compare
Choose a tag to compare
v1.0.0-M2 Pre-release
Pre-release

This release of Micrometer Tracing depends on micrometer-core:2.0.0-M2, you can find the documentation here.

  • We're providing an improved SampleTestRunner for your integration tests that also include in memory tests (in addition to Zipkin and Wavefront).
  • Added AssertJ extensions to assert a FinishedSpan and Collection<FinishedSpan>
  • Upgraded to OTel 1.10.1
  • Updated the DocumentedSpan abstraction
  • Better unit testing mechanisms for Tracer

1.0.0-M1

11 Jan 02:51
v1.0.0-M1
64ea7f7
Compare
Choose a tag to compare
1.0.0-M1 Pre-release
Pre-release

This is the first release of micrometer-tracing, it depends on micrometer-core:2.0.0-M1, you can find the documentation here.

Micrometer Tracing provides a simple facade for the most popular tracer libraries, letting you instrument your JVM-based application code without vendor lock-in. It is designed to add little to no overhead to your tracing collection activity while maximizing the portability of your tracing effort.

It also provides a tracing extension to Micrometer’s TimerRecordingHandler (starting from Micrometer 2.0.0-M1 version). Whenever a Timer.Sample is used, a corresponding span will be created, started, stopped and reported.