[receiver/elasticsearch] add jvm heap percentage usage metric #16173
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
djaglowski
reviewed
Nov 9, 2022
aboguszewski-sumo
force-pushed
the
elastic-jvm-heap-percent
branch
from
24fe6fe
to
4e72434
Compare
djaglowski
approved these changes
Nov 10, 2022
MovieStoreGuy
pushed a commit
to atlassian-forks/opentelemetry-collector-contrib
that referenced
this pull request
Nov 16, 2022
…elemetry#16173) * feat: add jvm heap percentage usage metric
shalper2
pushed a commit
to shalper2/opentelemetry-collector-contrib
that referenced
this pull request
Dec 6, 2022
…elemetry#16173) * feat: add jvm heap percentage usage metric
Closed
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:
A metric responsible for jvm heap usage in percents has been added.
Related comment: #14635 (comment)
Link to tracking Issue: #14635
Testing:
unit
Documentation:
mdatagen