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.3.3 to 1.5.3 #369

Closed dependabot-preview[bot] closed 4 years ago

dependabot-preview[bot] commented 4 years ago

Bumps micrometer.version from 1.3.3 to 1.5.3. Updates micrometer-registry-prometheus from 1.3.3 to 1.5.3

Release notes

Sourced from micrometer-registry-prometheus's releases.

v1.5.3

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

Known issues

micrometer-registry-statsd

Noteworthy

micrometer-registry-wavefront

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

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](https://github.com/micrometer-metrics/micrometer/issues/2069)
    .build(getGraphiteSender(config));

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.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.
Commits
  • a76af67 Upgrade to wavefront-sdk-java 2.6.0
  • b31c20f Merge branch '1.3.x' into 1.5.x
  • d0b62df Merge branch '1.1.x' into 1.3.x
  • 995d58a Polish
  • c6254bc Avoid async log4j2 log events to be counted multiple times (#2183)
  • 2689968 Merge branch '1.3.x' into 1.5.x
  • aa8fc83 Merge branch '1.1.x' into 1.3.x
  • 209d1f3 Fix classloading issue when using a Java EE container (#2205)
  • 3f07363 Polish JettyClientMetricsTest
  • 40cdf55 Fix a NPE with jetty client and no request body (#2204)
  • Additional commits viewable in compare view


Updates micrometer-registry-influx from 1.3.3 to 1.5.3

Release notes

Sourced from micrometer-registry-influx's releases.

v1.5.3

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

Known issues

micrometer-registry-statsd

Noteworthy

micrometer-registry-wavefront

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

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](https://github.com/micrometer-metrics/micrometer/issues/2069)
    .build(getGraphiteSender(config));

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.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.
Commits
  • a76af67 Upgrade to wavefront-sdk-java 2.6.0
  • b31c20f Merge branch '1.3.x' into 1.5.x
  • d0b62df Merge branch '1.1.x' into 1.3.x
  • 995d58a Polish
  • c6254bc Avoid async log4j2 log events to be counted multiple times (#2183)
  • 2689968 Merge branch '1.3.x' into 1.5.x
  • aa8fc83 Merge branch '1.1.x' into 1.3.x
  • 209d1f3 Fix classloading issue when using a Java EE container (#2205)
  • 3f07363 Polish JettyClientMetricsTest
  • 40cdf55 Fix a NPE with jetty client and no request body (#2204)
  • Additional commits viewable in compare view


Updates micrometer-registry-jmx from 1.3.3 to 1.5.3

Release notes

Sourced from micrometer-registry-jmx's releases.

v1.5.3

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

Known issues

micrometer-registry-statsd

Noteworthy

micrometer-registry-wavefront

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

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](https://github.com/micrometer-metrics/micrometer/issues/2069)
    .build(getGraphiteSender(config));

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.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.
Commits
  • a76af67 Upgrade to wavefront-sdk-java 2.6.0
  • b31c20f Merge branch '1.3.x' into 1.5.x
  • d0b62df Merge branch '1.1.x' into 1.3.x
  • 995d58a Polish
  • c6254bc Avoid async log4j2 log events to be counted multiple times (#2183)
  • 2689968 Merge branch '1.3.x' into 1.5.x
  • aa8fc83 Merge branch '1.1.x' into 1.3.x
  • 209d1f3 Fix classloading issue when using a Java EE container (#2205)
  • 3f07363 Polish JettyClientMetricsTest
  • 40cdf55 Fix a NPE with jetty client and no request body (#2204)
  • Additional commits viewable in compare view


Updates micrometer-registry-graphite from 1.3.3 to 1.5.3

Release notes

Sourced from micrometer-registry-graphite's releases.

v1.5.3

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

Known issues

micrometer-registry-statsd

Noteworthy

micrometer-registry-wavefront

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

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](https://github.com/micrometer-metrics/micrometer/issues/2069)
    .build(getGraphiteSender(config));

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.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.
Commits
  • a76af67 Upgrade to wavefront-sdk-java 2.6.0
  • b31c20f Merge branch '1.3.x' into 1.5.x
  • d0b62df Merge branch '1.1.x' into 1.3.x
  • 995d58a Polish
  • c6254bc Avoid async log4j2 log events to be counted multiple times (#2183)
  • 2689968 Merge branch '1.3.x' into 1.5.x
  • aa8fc83 Merge branch '1.1.x' into 1.3.x
  • 209d1f3 Fix classloading issue when using a Java EE container (#2205)
  • 3f07363 Polish JettyClientMetricsTest
  • 40cdf55 Fix a NPE with jetty client and no request body (#2204)
  • 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 #369 into develop will not change coverage. The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##             develop     #369   +/-   ##
==========================================
  Coverage      56.94%   56.94%           
  Complexity       208      208           
==========================================
  Files             21       21           
  Lines           1008     1008           
  Branches         182      182           
==========================================
  Hits             574      574           
  Misses           327      327           
  Partials         107      107

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 22ce58d...b46178c. Read the comment docs.

dependabot-preview[bot] commented 4 years ago

Superseded by #392.