Cherry-pick #20649 to 7.x: Kubernetes state_daemonset metricset for Metricbeat #20900
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 #20649 to 7.x branch. Original message:
What does this PR do?
Implements
state_daemonset
for the Metricbeat Kubernetes module, in the model ofstate_deployment
,state_replicaset
etc.Why is it important?
Allows monitoring (and alerting) of
DaemonSet
replica status. GivesDaemonSet
similar Metricbeat coverage to the other standard pod controllers (ReplicaSet
etc).Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
MODULE=kubernetes mage -v test
in themetricbeat
directory.Test result may be affected by #20627
Related issues
Use cases
Comprehensive alerting for all standard pod controllers. Alert when insufficient available pods exist for a
DaemonSet
, (not justDeployment
,ReplicaSet
, andStatefulSet
).