Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add state_daemonset metricset to Kubernetes module #17010

Closed
jarpy opened this issue Mar 16, 2020 · 3 comments · Fixed by #20649
Closed

Add state_daemonset metricset to Kubernetes module #17010

jarpy opened this issue Mar 16, 2020 · 3 comments · Fixed by #20649
Labels
containers Related to containers use case enhancement Team:Platforms Label for the Integrations - Platforms team

Comments

@jarpy
Copy link
Contributor

jarpy commented Mar 16, 2020

Describe the enhancement:
Provide a metricset for the state of Daemonsets in the spirit of state_deployment and state_statefulset.

Describe a specific use case for the enhancement or feature:
Defining alerts that can cover the health of all the standard pod controllers.

@jarpy
Copy link
Contributor Author

jarpy commented Mar 16, 2020

cc @Crazybus @flaper87

@ChrsMark ChrsMark added containers Related to containers use case enhancement Team:Platforms Label for the Integrations - Platforms team labels Mar 16, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations-platforms (Team:Platforms)

@jarpy
Copy link
Contributor Author

jarpy commented Jul 22, 2020

Is this on the roadmap? I could try my hand at implementing it if nobody has it on their plate already.

jarpy added a commit to jarpy/beats that referenced this issue Aug 18, 2020
Implements state_daemonset for the Metricbeat Kubernetes module, in
the model of state_deployment, state_replicaset etc.

Closes: elastic#17010
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
containers Related to containers use case enhancement Team:Platforms Label for the Integrations - Platforms team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants