search

reactiverse / es4x

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

Bump micrometer.version from 1.5.5 to 1.6.2 #472

Closed dependabot-preview[bot] closed 3 years ago

dependabot-preview[bot] commented 3 years ago

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

Release notes

Sourced from micrometer-registry-prometheus's releases.

v1.6.2

This patch release contains changes from the 1.3.16 release, 1.5.8 release, 1.5.9 release, and the 1.6.2 milestone.

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

  • Timer.Sample's tags methods and the stop method that takes a Timer.Builder have been removed. Instead, tags should be specified on the Timer passed to the remaining stop method. This makes for consistency - tags are always configured on the Timer.

    Timer.Sample sample = Timer.start(meterRegistry);
// ... do some stuff
sample.tags("flag", flag);
sample.tags(Tags.of("other", "tag"));
sample.stop(meterRegistry, Timer.builder("sample.time"));

    Timer.Sample sample = Timer.start(meterRegistry);
// ... do some stuff
sample.stop(Timer.builder("sample.time")
         .tag("flag", flag)
         .tags(Tags.of("other", "tag"))
         .register(meterRegistry));

  • 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").

Registry-specific

  • [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.
  • [WavefrontMeterRegistry] micrometer-metrics/micrometer#2175 wavefront-sdk-java 2.4 or later is required now.
Commits
  • 1e1d69a Remove tags from Timer.Sample.stop javadoc (#2351)
  • 6c7dc52 Merge branch '1.5.x' into 1.6.x
  • e3da9e7 Upgrade to reactor 3.3.12, reactor-netty 0.9.15, netty 4.1.54
  • 50ecdc3 Revert "Upgrade to Reactor 3.4 and Reactor Netty 1.0 (#2359)"
  • c8f6742 Revert "Upgrade to Reactor 2020.0.2"
  • 64df1ac Consider Shenandoah Cycles as concurrent phase time
  • db00a22 Merge branch '1.5.x' into 1.6.x
  • e458fb1 Add implementation note to Javadoc for HibernateMetrics (#2376)
  • af599e4 Upgrade to Reactor 2020.0.2
  • 05877a3 Merge branch '1.5.x' into 1.6.x
  • Additional commits viewable in compare view


Updates micrometer-registry-influx from 1.5.5 to 1.6.2

Release notes

Sourced from micrometer-registry-influx's releases.

v1.6.2

This patch release contains changes from the 1.3.16 release, 1.5.8 release, 1.5.9 release, and the 1.6.2 milestone.

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

  • Timer.Sample's tags methods and the stop method that takes a Timer.Builder have been removed. Instead, tags should be specified on the Timer passed to the remaining stop method. This makes for consistency - tags are always configured on the Timer.

    Timer.Sample sample = Timer.start(meterRegistry);
// ... do some stuff
sample.tags("flag", flag);
sample.tags(Tags.of("other", "tag"));
sample.stop(meterRegistry, Timer.builder("sample.time"));

    Timer.Sample sample = Timer.start(meterRegistry);
// ... do some stuff
sample.stop(Timer.builder("sample.time")
         .tag("flag", flag)
         .tags(Tags.of("other", "tag"))
         .register(meterRegistry));

  • 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").

Registry-specific

  • [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.
  • [WavefrontMeterRegistry] micrometer-metrics/micrometer#2175 wavefront-sdk-java 2.4 or later is required now.
Commits
  • 1e1d69a Remove tags from Timer.Sample.stop javadoc (#2351)
  • 6c7dc52 Merge branch '1.5.x' into 1.6.x
  • e3da9e7 Upgrade to reactor 3.3.12, reactor-netty 0.9.15, netty 4.1.54
  • 50ecdc3 Revert "Upgrade to Reactor 3.4 and Reactor Netty 1.0 (#2359)"
  • c8f6742 Revert "Upgrade to Reactor 2020.0.2"
  • 64df1ac Consider Shenandoah Cycles as concurrent phase time
  • db00a22 Merge branch '1.5.x' into 1.6.x
  • e458fb1 Add implementation note to Javadoc for HibernateMetrics (#2376)
  • af599e4 Upgrade to Reactor 2020.0.2
  • 05877a3 Merge branch '1.5.x' into 1.6.x
  • Additional commits viewable in compare view


Updates micrometer-registry-jmx from 1.5.5 to 1.6.2

Release notes

Sourced from micrometer-registry-jmx's releases.

v1.6.2

This patch release contains changes from the 1.3.16 release, 1.5.8 release, 1.5.9 release, and the 1.6.2 milestone.

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

  • Timer.Sample's tags methods and the stop method that takes a Timer.Builder have been removed. Instead, tags should be specified on the Timer passed to the remaining stop method. This makes for consistency - tags are always configured on the Timer.

    Timer.Sample sample = Timer.start(meterRegistry);
// ... do some stuff
sample.tags("flag", flag);
sample.tags(Tags.of("other", "tag"));
sample.stop(meterRegistry, Timer.builder("sample.time"));

    Timer.Sample sample = Timer.start(meterRegistry);
// ... do some stuff
sample.stop(Timer.builder("sample.time")
         .tag("flag", flag)
         .tags(Tags.of("other", "tag"))
         .register(meterRegistry));

  • 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").

Registry-specific

  • [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.
  • [WavefrontMeterRegistry] micrometer-metrics/micrometer#2175 wavefront-sdk-java 2.4 or later is required now.
Commits
  • 1e1d69a Remove tags from Timer.Sample.stop javadoc (#2351)
  • 6c7dc52 Merge branch '1.5.x' into 1.6.x
  • e3da9e7 Upgrade to reactor 3.3.12, reactor-netty 0.9.15, netty 4.1.54
  • 50ecdc3 Revert "Upgrade to Reactor 3.4 and Reactor Netty 1.0 (#2359)"
  • c8f6742 Revert "Upgrade to Reactor 2020.0.2"
  • 64df1ac Consider Shenandoah Cycles as concurrent phase time
  • db00a22 Merge branch '1.5.x' into 1.6.x
  • e458fb1 Add implementation note to Javadoc for HibernateMetrics (#2376)
  • af599e4 Upgrade to Reactor 2020.0.2
  • 05877a3 Merge branch '1.5.x' into 1.6.x
  • Additional commits viewable in compare view


Updates micrometer-registry-graphite from 1.5.5 to 1.6.2

Release notes

Sourced from micrometer-registry-graphite's releases.

v1.6.2

This patch release contains changes from the 1.3.16 release, 1.5.8 release, 1.5.9 release, and the 1.6.2 milestone.

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

  • Timer.Sample's tags methods and the stop method that takes a Timer.Builder have been removed. Instead, tags should be specified on the Timer passed to the remaining stop method. This makes for consistency - tags are always configured on the Timer.

    Timer.Sample sample = Timer.start(meterRegistry);
// ... do some stuff
sample.tags("flag", flag);
sample.tags(Tags.of("other", "tag"));
sample.stop(meterRegistry, Timer.builder("sample.time"));

    Timer.Sample sample = Timer.start(meterRegistry);
// ... do some stuff
sample.stop(Timer.builder("sample.time")
         .tag("flag", flag)
         .tags(Tags.of("other", "tag"))
         .register(meterRegistry));

  • 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").

Registry-specific

  • [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.
  • [WavefrontMeterRegistry] micrometer-metrics/micrometer#2175 wavefront-sdk-java 2.4 or later is required now.
Commits
  • 1e1d69a Remove tags from Timer.Sample.stop javadoc (#2351)
  • 6c7dc52 Merge branch '1.5.x' into 1.6.x
  • e3da9e7 Upgrade to reactor 3.3.12, reactor-netty 0.9.15, netty 4.1.54
  • 50ecdc3 Revert "Upgrade to Reactor 3.4 and Reactor Netty 1.0 (#2359)"
  • c8f6742 Revert "Upgrade to Reactor 2020.0.2"
  • 64df1ac Consider Shenandoah Cycles as concurrent phase time
  • db00a22 Merge branch '1.5.x' into 1.6.x
  • e458fb1 Add implementation note to Javadoc for HibernateMetrics (#2376)
  • af599e4 Upgrade to Reactor 2020.0.2
  • 05877a3 Merge branch '1.5.x' into 1.6.x
  • 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 3 years ago

Codecov Report

Merging #472 (df1dfc9) into develop (4a27784) will not change coverage. The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##             develop     #472   +/-   ##
==========================================
  Coverage      55.67%   55.67%           
  Complexity       215      215           
==========================================
  Files             18       18           
  Lines           1162     1162           
  Branches         215      215           
==========================================
  Hits             647      647           
  Misses           386      386           
  Partials         129      129

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 4a27784...df1dfc9. Read the comment docs.