Cherry-pick #22877 to 7.x: [libbeat] Mark additional log metrics as gauges #23032
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.
Cherry-pick of PR #22877 to 7.x branch. Original message:
What does this PR do?
This marks additional log metrics as gauges.
libbeat.output.events.active
andbeat.memstats.rss
are both gauges(rather than counters) so disable delta reporting for these two values.
Why is it important?
It's really hard to make sense the metrics over time since they are reported as deltas.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.