v1.3.11

This patch release contains the changes from the 1.1.16 release and the 1.3.11 milestone.

v1.1.16

See the 1.1.16 milestone for included changes in this patch release.

v1.5.2

This patch release contains the changes from the 1.5.2 milestone, the 1.1.15 release, and the 1.3.10 release.

---

Known issues

micrometer-registry-statsd

• #2177 StatsD UDP reconnect bug. We are working to get a fix for this in the next patch release.

micrometer-registry-graphite

#2069 Users wishing to use the Graphite tag support added in but broken since Micrometer 1.4, a workaround is now available. Specifically, you should upgrade your metrics-graphite dependency to 4.1.8 or later and provide a GraphiteReporter to the GraphiteMeterRegistry constructor with the new addMetricAttributesAsTags option set, such as will be done in the default GraphiteReporter in Micrometer 1.6.0:

GraphiteReporter.forRegistry(metricRegistry)
    .withClock(new DropwizardClock(clock))
    .convertRatesTo(config.rateUnits())
    .convertDurationsTo(config.durationUnits())
    .addMetricAttributesAsTags(config.graphiteTagsEnabled()) // this fixes #2069
    .build(getGraphiteSender(config));

v1.3.10

This patch release contains the changes from the 1.1.15 release as well as the 1.3.10 milestone.

v1.1.15

See the 1.1.15 milestone for included changes in this patch release.

v1.5.1

This patch release contains the changes in the 1.1.14 release and the 1.3.9 release as well as the 1.5.1 milestone.

v1.3.9

This patch release contains the changes in the 1.1.14 release and the 1.3.9 milestone.

v1.1.14

This patch release contains the changes included in the 1.1.14 milestone.

v1.5.0

1.5.x is an LTS release line.

Thank you to all the people who contributed to this release.

---

Compatibility impacting

• [Atlas] The tag on histogram gauges for what was previously called sla is now named service.level.objective. Queries on this tag will need to be updated.
• [Graphite] #2007 to make the upgrade experience smoother, the default value for the configuration option for the recently added Graphite Tag support has been changed from true to being true if there are no tagsAsPrefix configured.
• [Wavefront] #1901 WavefrontMeterRegistry uses a WavefrontSender now instead of the Micrometer HttpSender to publish metrics to Wavefront. If you were customizing the HttpSender used for Wavefront, you should look at customizing the WavefrontSender instead now.

New metrics

• #1975 Jetty handshake metrics via JettySslHandshakeMetrics configured as an SslHandshakeListener
• #2019 Jetty HttpClient metrics via JettyClientMetrics configured as a Request.Listener
• #2041 ThreadPoolExecutor metrics for pool max and core configuration

Enhancements

• #1242 Automatic-Module-Name is now included in manifest files. Module path users will now have stable Automatic-Module-Names that match the previously derived file name-based names.
• #1697 HazelcastCacheMetrics has been updated to support both Hazelcast 3 and Hazelcast 4
• #1702 Align target tags on HTTP client implementations (Apache HttpComponents and OkHttp) to include target.host, target.port, and target.scheme
• #1912 OkHttpMetricsEventListener can be configured with a function to add a tag based on the Request and Response
• #1919 ExecutorServiceMetrics can now prefix the metric names used, which is particularly useful when instrumenting multiple Executors with different tag sets
• #2005 LongTaskTimer has been improved to allow additional measurements like max, percentiles, histogram
• #2001 sla configuration options have been renamed as serviceLevelObjectives to better align with their purpose
• #2008/#2009 CompletableFuture support for the @Timed and @Counted annotations
• #2011 Registry Config validation has been reworked to do more validation of configuration options

Registry-specific changes

Atlas

• The tag on histogram gauges for what was previously called sla is now named service.level.objective. Queries on this tag will need to be updated.

Graphite

• #2007 to make the upgrade experience smoother, the default value for the configuration option for the recently added Graphite Tag support has been changed from simply true to being true if there are no tagsAsPrefix configured.

Prometheus

• #1883 Support filtering by metric name on the CollectorRegistry used by the PrometheusMeterRegistry

Wavefront

• Wavefront SDK version 2.2 or later is now a required dependency for the Wavefront module
• #1901 WavefrontMeterRegistry uses a WavefrontSender now instead of the Micrometer HttpSender to publish metrics to Wavefront. If you were customizing the HttpSender used for Wavefront, you should look at customizing the WavefrontSender instead now.

---

See the 1.5.0 milestone for all included changes.

v1.4.2

This patch release includes changes from the 1.1.13 release, 1.3.8 release, and the 1.4.2 milestone.

Note: 1.4.x is a non-LTS release line that will have patch releases only until the next LTS release line 1.5.x starts with the 1.5.0 release. See the support policy for more details.

---

• #1993 has reverted the changes made in the 1.4.0 release for #1796. The behavior for Timer#max is now back to what it was before the 1.4.0 release.
• #1958 NewRelicClientProvider implementations mistakenly had public constructors that took a NamingConvention. These have been removed. NamingConvention should be configured via the NewRelicMeterRegistry.Builder.

#2002 There was a backwards incompatible change made in 1.4.0 to the DistributionStatisticsConfig.getMinimumExpectedValue() and DistributionStatisticsConfig.getMaximumExpectedValue(), changing their return type from Long to Double. If you are using these methods in a library that intends to support users on Micrometer 1.3.x and 1.4.x+, you should instead use the newly added getMinimumExpectedValueAsDouble and getMaximumExpectedValueAsDouble methods, available since 1.3.8 and 1.4.2 and 1.5.0.
Similarly, getSlaBoundaries return type was changed from long[] to double[], so a getServiceLevelObjectiveBoundaries() method has been added to 1.3.8 and 1.4.2 and 1.5.0.