Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump io.micrometer.version from 1.3.1 to 1.5.1 #8

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot-preview[bot]
Copy link

@dependabot-preview dependabot-preview bot commented May 20, 2020

Bumps io.micrometer.version from 1.3.1 to 1.5.1.
Updates micrometer-core from 1.3.1 to 1.5.1

Release notes

Sourced from micrometer-core's releases.

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.

New metrics

  • #1975 Jetty handshake metrics via JettySslHandshakeMetrics configured as an SslHandshakeListener
  • #2019 Jetty HttpClient metrics via JettyClientMetrics configured as a Request.Listener
  • #2041 ThreadPoolExecutor metrics for pool max and core configuration

Enhancements

  • #1242 Automatic-Module-Name is now included in manifest files. Module path users will now have stable Automatic-Module-Names that match the previously derived file name-based names.
  • #1697 HazelcastCacheMetrics has been updated to support both Hazelcast 3 and Hazelcast 4
  • #1702 Align target tags on HTTP client implementations (Apache HttpComponents and OkHttp) to include target.host, target.port, and target.scheme
  • #1912 OkHttpMetricsEventListener can be configured with a function to add a tag based on the Request and Response
  • #1919 ExecutorServiceMetrics can now prefix the metric names used, which is particularly useful when instrumenting multiple Executors with different tag sets
  • #2005 LongTaskTimer has been improved to allow additional measurements like max, percentiles, histogram
  • #2001 sla configuration options have been renamed as serviceLevelObjectives to better align with their purpose
  • #2008/#2009 CompletableFuture support for the @Timed and @Counted annotations
  • #2011 Registry Config validation has been reworked to do more validation of configuration options

Registry-specific changes

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 simply true to being true if there are no tagsAsPrefix configured.

Prometheus

  • #1883 Support filtering by metric name on the CollectorRegistry used by the PrometheusMeterRegistry

Wavefront

  • Wavefront SDK version 2.2 or later is now a required dependency for the Wavefront module
  • #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.

See the 1.5.0 milestone for all included changes.

... (truncated)
Commits
  • 5984c10 Merge branch '1.3.x' into 1.5.x
  • ca234a5 Remove unused import
  • 8379390 Polish ExecutorServiceMetrics changes (#2053)
  • f4ae692 Polish ExecutorServiceMetricsTest
  • 25fdad8 Allow ExecutorServiceMetrics accepting metric name prefix (#1920)
  • f5ea2a6 StepTimer#mean should work regardless of other calls (fixes #1814)
  • 905341b Merge branch '1.3.x' into 1.5.x
  • c021368 Merge branch '1.1.x' into 1.3.x
  • 101a094 Fix for J9
  • 131cf37 Merge branch '1.3.x' into 1.5.x
  • Additional commits viewable in compare view

Updates micrometer-registry-prometheus from 1.3.1 to 1.5.1

Release notes

Sourced from micrometer-registry-prometheus's releases.

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.

New metrics

  • #1975 Jetty handshake metrics via JettySslHandshakeMetrics configured as an SslHandshakeListener
  • #2019 Jetty HttpClient metrics via JettyClientMetrics configured as a Request.Listener
  • #2041 ThreadPoolExecutor metrics for pool max and core configuration

Enhancements

  • #1242 Automatic-Module-Name is now included in manifest files. Module path users will now have stable Automatic-Module-Names that match the previously derived file name-based names.
  • #1697 HazelcastCacheMetrics has been updated to support both Hazelcast 3 and Hazelcast 4
  • #1702 Align target tags on HTTP client implementations (Apache HttpComponents and OkHttp) to include target.host, target.port, and target.scheme
  • #1912 OkHttpMetricsEventListener can be configured with a function to add a tag based on the Request and Response
  • #1919 ExecutorServiceMetrics can now prefix the metric names used, which is particularly useful when instrumenting multiple Executors with different tag sets
  • #2005 LongTaskTimer has been improved to allow additional measurements like max, percentiles, histogram
  • #2001 sla configuration options have been renamed as serviceLevelObjectives to better align with their purpose
  • #2008/#2009 CompletableFuture support for the @Timed and @Counted annotations
  • #2011 Registry Config validation has been reworked to do more validation of configuration options

Registry-specific changes

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 simply true to being true if there are no tagsAsPrefix configured.

Prometheus

  • #1883 Support filtering by metric name on the CollectorRegistry used by the PrometheusMeterRegistry

Wavefront

  • Wavefront SDK version 2.2 or later is now a required dependency for the Wavefront module
  • #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.

See the 1.5.0 milestone for all included changes.

... (truncated)
Commits
  • 5984c10 Merge branch '1.3.x' into 1.5.x
  • ca234a5 Remove unused import
  • 8379390 Polish ExecutorServiceMetrics changes (#2053)
  • f4ae692 Polish ExecutorServiceMetricsTest
  • 25fdad8 Allow ExecutorServiceMetrics accepting metric name prefix (#1920)
  • f5ea2a6 StepTimer#mean should work regardless of other calls (fixes #1814)
  • 905341b Merge branch '1.3.x' into 1.5.x
  • c021368 Merge branch '1.1.x' into 1.3.x
  • 101a094 Fix for J9
  • 131cf37 Merge branch '1.3.x' into 1.5.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.


Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

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)

Bumps `io.micrometer.version` from 1.3.1 to 1.5.1.

Updates `micrometer-core` from 1.3.1 to 1.5.1
- [Release notes](https://github.com/micrometer-metrics/micrometer/releases)
- [Commits](micrometer-metrics/micrometer@v1.3.1...v1.5.1)

Updates `micrometer-registry-prometheus` from 1.3.1 to 1.5.1
- [Release notes](https://github.com/micrometer-metrics/micrometer/releases)
- [Commits](micrometer-metrics/micrometer@v1.3.1...v1.5.1)

Signed-off-by: dependabot-preview[bot] <[email protected]>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label May 20, 2020
@dependabot-preview
Copy link
Author

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants