Cherry-pick #23905 to 7.x: [Metricbeat][Kubernetes] Extend state_node with more conditions #24057
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 #23905 to 7.x branch. Original message:
What does this PR do?
This PR extends the
state_node
module of the Metricbeat's Kubernetes module with more status conditions, such asMemoryPressure
,DiskPressure
,OutOfDisk
andPIDPressure
.Refactor the
opFilter
Prometheus metric helper to allow the declaration of multiple Metricbeat fields from a single Prometheus metric, based on allowed label values.Why is it important?
Adding more status conditions of Kubernetes nodes is useful for monitoring and alerting purposes as it allows one to use conditions like:
Checklist
I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
Use cases
Screenshots
Logs