v1.3.0

1.3 is an LTS release line.

Known issues

• #1591 Statsd publishing broken on Linux network interfaces with multicast disabled. This will be fixed in a future patch release.

Notable changes

• A dependency Bill of Materials (BOM) artifact is now published as io.micrometer:micrometer-bom. This can be used to manage the version of all Micrometer artifacts.

• The New Relic registry now publishes all metrics with the eventType as MicrometerSample by default to align with New Relic best practices on eventType values. The previous behavior can be restored by setting the new config meterNameEventTypeEnabled to true. See #1588

---

See the 1.3.0 milestone for all included items.

This release includes all changes in the 1.1.7 release and the 1.2.2 release.

v1.2.2

This is the final planned release in the 1.2.x line. Upgrade to 1.3.x to continue to get patches.

This release contains all of the changes in the 1.1.7 release.

See issues included in the 1.2.2 milestone.

v1.1.7

Notable changes

An inadvertent use of slf4j in micrometer-core has been removed. Micrometer now uses an internal logging facade adopted from code in the Netty project.

---

See the milestone for all issues included in this release.

v1.2.1

NOTE: 1.2.x is a non-LTS release line that will not publish patch releases once 1.3.0 is released. See our support policy for more details.

---

See the milestone for included issues. Issues in the 1.1.6 milestone were also included in this version.

v1.1.6

See the milestone for included issues.

v1.2.0 (non-LTS)

NOTE: This is a non-LTS release. 1.2.x patches will be provided only until 1.3.0 is released. See the support policy for more details.

---

Notable changes

• #1254 Caffeine metrics support now requires Caffeine 2.7 or later
• #1315 Wavefront registry now ships cumulative values instead of rates; use the rate functions in Wavefront to derive rates
• #1446 InfluxDB registry will write the metric_type with the Meter.Id.Type for custom Meter implementations instead of unknown

---

See the 1.2.0 milestone for all included issues.

v1.1.5

Notable changes

#1421 If using the ElasticMeterRegistry, any existing metrics_template template needs to be deleted when upgrading so it can be recreated with the fix included in that change.

---

See the 1.1.5 milestone for full details on what was included in this release. All changes from the 1.0.11 release were also included in 1.1.5.

v1.0.11

NOTE: This is the last planned patch release of the 1.0.x version line. Please upgrade to a supported release line to get future patches.

---

See the 1.0.11 milestone for details on changes included in this release.

v1.1.4

See the 1.1.4 milestone for included changes. 1.0.10 changes are also included in this release.

Notable changes

Default PauseDetector

The default PauseDetector has been changed to NoPauseDetector from ClockDriftPauseDetector (see #1324). To restore the prior behavior, configure a ClockDriftPauseDetector on your MeterRegistry like:

registry.config().pauseDetector(new ClockDriftPauseDetector(Duration.ofMillis(100), Duration.ofMillis(100));

Fail fast on missing required configuration

MissingRequiredConfigurationException will be thrown when instantiating MeterRegistry implementations if required configuration values are not available from the given *Config class used.

Fixes

Enhancements

v1.0.10

See the 1.0.10 milestone for included items.

Notable changes

Default PauseDetector

The default PauseDetector has been changed to NoPauseDetector from ClockDriftPauseDetector (see #1324). To restore the prior behavior, configure a ClockDriftPauseDetector on your MeterRegistry like:

registry.config().pauseDetector(new ClockDriftPauseDetector(Duration.ofMillis(100), Duration.ofMillis(100));

Fixes

• Tomcat ThreadPool metrics reporting NaN values
• Handle NaN and infinity for New Relic Insights
• Replace invalid characters in events for New Relic naming convention
• Respect mode for FunctionTimer/FunctionCounter in SimpleMeterRegistry
• Respect time unit parameter in FunctionTimer.totalTime()
• Handle null MemoryUsage in JvmMemoryMetrics
• InfluxMeterRegistry sends tags with empty values which influx then rejects
• Use nanoseconds for Dropwizard timer snapshot mean
• Start line sink only when enabled in StatsD meter registry
• Use noop processor when publishing is disabled in StatsD meter registry
• Get Timed annotation from proxy target when failed
• Handle missing exceptions in WebMvcMetricsFilter
• Custom meters' fields are written incorrectly with InfluxMeterRegistry

Enhancements

• Add Infinity Buckets to the StatsD MeterRegistry for Meters with an SLA
• Use MissingRequiredConfigurationException consistently
• Datadog: log when applicationKey is not configured
• Use system-dependent line separator for logs
• Various documentation improvements
• Various test code polish