4.x metrics tck fix #8054
Draft
4.x metrics tck fix #8054
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ference; update to dep on MP metrics 5.0.2
oracle-contributor-agreement
bot
added
the
OCA Verified
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Resolves #7578
Documentation
Bug fix, and there are no existing documentation references to the
gc.timesystem meter that identify it as a counter or refer to the Prometheus format.Release note information
The built-in
gc.timesystem meter is changing from aCounterto aGaugeas a result of an MP Metrics TCK bug fix (see the link in the resolved issue).In the Prometheus or OpenMetrics output from Helidon for
gc.time:gc_time_seconds_totaltogc_time_secondsTYPEline changes fromcountertogauge.