search

reactiverse / es4x

🚀 fast JavaScript 4 Eclipse Vert.x
https://reactiverse.io/es4x/
Apache License 2.0
884 stars 75 forks source link

Bump micrometer.version from 1.5.5 to 1.6.0 #440

Closed dependabot-preview[bot] closed 3 years ago

dependabot-preview[bot] commented 4 years ago

Bumps micrometer.version from 1.5.5 to 1.6.0. Updates micrometer-registry-prometheus from 1.5.5 to 1.6.0

Release notes

Sourced from micrometer-registry-prometheus's releases.

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
  • 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").
  • [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.
  • [WavefrontMeterRegistry] micrometer-metrics/micrometer#2175 wavefront-sdk-java 2.4 or later is required now.

New Meter Registries

New metrics

Enhancements

Registry-specific changes

CloudWatch

Elasticsearch

Wavefront

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
  • 073946e Update locks to Kafka dependency versions in Central
  • 9fc71ce Write Gradle lock files to lock dependencies
  • a476dad Add counters for QueryPlanCacheHit and QueryPlanCacheMiss in HibernateMetrics...
  • b06f95c Use our canonical naming convention for KafkaMetrics tags (#2316)
  • 25f1208 Add option to disable illegal access in ExecutorServiceMetrics (#2185)
  • b585495 Change default index name prefix to "micrometer-metrics" (#2288)
  • 7b8eee5 Add tomcat connection metrics (#2248)
  • b444dd1 Use non-deprecated CacheRegionStatistics instead of SecondLevelCacheStatistics
  • d0da89c Fix HibernateMetricsTest to use non-deprecated method
  • e6ae7ba Pin Hibernate to 5.x and remove deprecated usage
  • Additional commits viewable in compare view


Updates micrometer-registry-influx from 1.5.5 to 1.6.0

Release notes

Sourced from micrometer-registry-influx's releases.

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
  • 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").
  • [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.
  • [WavefrontMeterRegistry] micrometer-metrics/micrometer#2175 wavefront-sdk-java 2.4 or later is required now.

New Meter Registries

New metrics

Enhancements

Registry-specific changes

CloudWatch

Elasticsearch

Wavefront

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
  • 073946e Update locks to Kafka dependency versions in Central
  • 9fc71ce Write Gradle lock files to lock dependencies
  • a476dad Add counters for QueryPlanCacheHit and QueryPlanCacheMiss in HibernateMetrics...
  • b06f95c Use our canonical naming convention for KafkaMetrics tags (#2316)
  • 25f1208 Add option to disable illegal access in ExecutorServiceMetrics (#2185)
  • b585495 Change default index name prefix to "micrometer-metrics" (#2288)
  • 7b8eee5 Add tomcat connection metrics (#2248)
  • b444dd1 Use non-deprecated CacheRegionStatistics instead of SecondLevelCacheStatistics
  • d0da89c Fix HibernateMetricsTest to use non-deprecated method
  • e6ae7ba Pin Hibernate to 5.x and remove deprecated usage
  • Additional commits viewable in compare view


Updates micrometer-registry-jmx from 1.5.5 to 1.6.0

Release notes

Sourced from micrometer-registry-jmx's releases.

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
  • 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").
  • [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.
  • [WavefrontMeterRegistry] micrometer-metrics/micrometer#2175 wavefront-sdk-java 2.4 or later is required now.

New Meter Registries

New metrics

Enhancements

Registry-specific changes

CloudWatch

Elasticsearch

Wavefront

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
  • 073946e Update locks to Kafka dependency versions in Central
  • 9fc71ce Write Gradle lock files to lock dependencies
  • a476dad Add counters for QueryPlanCacheHit and QueryPlanCacheMiss in HibernateMetrics...
  • b06f95c Use our canonical naming convention for KafkaMetrics tags (#2316)
  • 25f1208 Add option to disable illegal access in ExecutorServiceMetrics (#2185)
  • b585495 Change default index name prefix to "micrometer-metrics" (#2288)
  • 7b8eee5 Add tomcat connection metrics (#2248)
  • b444dd1 Use non-deprecated CacheRegionStatistics instead of SecondLevelCacheStatistics
  • d0da89c Fix HibernateMetricsTest to use non-deprecated method
  • e6ae7ba Pin Hibernate to 5.x and remove deprecated usage
  • Additional commits viewable in compare view


Updates micrometer-registry-graphite from 1.5.5 to 1.6.0

Release notes

Sourced from micrometer-registry-graphite's releases.

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
  • 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").
  • [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.
  • [WavefrontMeterRegistry] micrometer-metrics/micrometer#2175 wavefront-sdk-java 2.4 or later is required now.

New Meter Registries

New metrics

Enhancements

Registry-specific changes

CloudWatch

Elasticsearch

Wavefront

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
  • 073946e Update locks to Kafka dependency versions in Central
  • 9fc71ce Write Gradle lock files to lock dependencies
  • a476dad Add counters for QueryPlanCacheHit and QueryPlanCacheMiss in HibernateMetrics...
  • b06f95c Use our canonical naming convention for KafkaMetrics tags (#2316)
  • 25f1208 Add option to disable illegal access in ExecutorServiceMetrics (#2185)
  • b585495 Change default index name prefix to "micrometer-metrics" (#2288)
  • 7b8eee5 Add tomcat connection metrics (#2248)
  • b444dd1 Use non-deprecated CacheRegionStatistics instead of SecondLevelCacheStatistics
  • d0da89c Fix HibernateMetricsTest to use non-deprecated method
  • e6ae7ba Pin Hibernate to 5.x and remove deprecated usage
  • 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](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)
codecov[bot] commented 4 years ago

Codecov Report

Merging #440 into develop will not change coverage. The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##             develop     #440   +/-   ##
==========================================
  Coverage      58.31%   58.31%           
  Complexity       202      202           
==========================================
  Files             17       17           
  Lines           1022     1022           
  Branches         199      199           
==========================================
  Hits             596      596           
  Misses           302      302           
  Partials         124      124

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 2a8edf8...011f9eb. Read the comment docs.

dependabot-preview[bot] commented 3 years ago

Superseded by #451.