Bump micrometer-registry-statsd from 1.4.1 to 1.6.1

[dependabot-preview]

Bumps micrometer-registry-statsd from 1.4.1 to 1.6.1.

Release notes

Sourced from micrometer-registry-statsd's releases.

v1.6.1

This patch release contains the changes in the 1.6.1 milestone and 1.5.7 release.

v1.6.0

1.6.x is an LTS release line - see the support page for more information on LTS vs non-LTS releases. This release contains changes from the 1.6.0 milestone.

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

---

Compatibility impacting

• [ElasticMeterRegistry] micrometer-metrics/micrometer#2288 Default index name prefix has been changed from metrics to micrometer-metrics to avoid a conflict with a built-in index template for an xpack feature in Elasticsearch 7.9
• [GraphiteMeterRegistry] micrometer-metrics/micrometer#2083 Graphite tags should work out of the box now but requires the metrics-graphite dependency version 4.1.8 or later
• [GraphiteMeterRegistry] micrometer-metrics/micrometer#2164 In order to retain the final publish on close behavior, users should be using at least version 4.1.8 of the metrics-core dependency.
• HibernateMetrics requires Hibernate 5.3 or later now.
• Kafka metrics - micrometer-metrics/micrometer#2256 The tag for client id on Kafka metrics has been changed from client-id to client.id to match the previous version of Kafka metrics from KafkaConsumerMetrics and to follow our canonical format. Likewise kafka-version has been updated to kafka.version. A MeterFilter can be applied to undo the tag name change or to apply this change to 1.5.x versions of Micrometer. For example: Users who want client.id in 1.5.x should configure MeterFilter.renameTag("kafka", "client-id", "client.id") Users who want client-id in 1.6.x should configure the opposite filter: MeterFilter.renameTag("kafka", "client.id", "client-id").
• [WavefrontMeterRegistry] micrometer-metrics/micrometer#2175 wavefront-sdk-java 2.4 or later is required now.

New Meter Registries

• HealthMeterRegistry for SLO-based health indicators. See micrometer-metrics/micrometer#2055

New metrics

• micrometer-metrics/micrometer#1875 Metrics for OkHttp ConnectionPool
• micrometer-metrics/micrometer#1712 CommonsObjectPool2Metrics
• micrometer-metrics/micrometer#2097 Expose per-region statistics for Hibernate L2 cache
• micrometer-metrics/micrometer#2248 Tomcat connection metrics
• micrometer-metrics/micrometer#2199 Add counters for QueryPlanCacheHit and QueryPlanCacheMiss in HibernateMetrics

Enhancements

• micrometer-metrics/micrometer#1861 Support Shenandoah GC in JvmGcMetrics
• micrometer-metrics/micrometer#2305 Support ZGC in JvmGcMetrics
• micrometer-metrics/micrometer#2185 Add option to disable illegal access in ExecutorServiceMetrics
• micrometer-metrics/micrometer#2068 Add onMeterRegistrationFailed listener configuration to MeterRegistry

Registry-specific changes

CloudWatch

• micrometer-metrics/micrometer#2088 Support of high resolution metrics for CloudWatch

Elasticsearch

• micrometer-metrics/micrometer#2255 Default index pattern changed for compatibility with Elasticsearch 7.9 xpack metrics index template

Wavefront

• micrometer-metrics/micrometer#2175 Allow step intervals at finer than whole second granularity for Wavefront

v1.5.7

This patch release contains the changes in the 1.5.7 milestone.

v1.5.6

This patch release contains the changes in the 1.5.6 milestone, 1.3.15 release, and the 1.1.19 release.

Commits

• 98927d9 Check for null when testing the long-lived pool name (#2336)
• 9311390 Merge branch '1.5.x' into 1.6.x
• a13a0d2 Upgrade to reactor-netty 0.9.14 / reactor 3.3.11 / netty 4.1.53
• a62ffc1 Emit second level cache statistics per-region for valid regions (#2335)
• fff1009 Merge branch '1.5.x' into 1.6.x
• cf304d9 Merge branch '1.3.x' into 1.5.x
• 13913c8 Polish Javadoc for Search (#2328)
• 2b6e153 Avoid using GcInfo in method signature (#2332)
• e358ca3 Merge branch '1.5.x' into 1.6.x
• e44977d Fix deadlock in SysdigStatsdLineBuilder (#2327)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)