-
Notifications
You must be signed in to change notification settings - Fork 131
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
Expose metrics for MachineDeployment status #1767
Comments
For this use case https://github.com/kubernetes/kube-state-metrics/blob/main/docs/metrics/extend/customresourcestate-metrics.md could be enough? |
That's definitely a way to implement metrics for these values if you need them, thank you for bringing up this option. At best, we expose those natively in future releases, but if you (as in you stumbled over this issue because you are missing those metrics) need this asap, the CRD solution from kube-state-metrics should help. |
@embik Are there any plans to take this up? |
@rajaSahil machine-controller already has a metrics endpoint (see https://github.com/kubermatic/machine-controller/blob/main/cmd/machine-controller/main.go#L257 for the "entry point"). So we should just add more metrics there instead of writing a dedicated exporter. |
Okay. |
You can comment |
Sure, thank you! |
/assign |
We need metrics to track
MachineDeployments
managed by this machine-controller over time. Primarily, the MachineDeployments' status information wrapped in metrics would be helpful, so something like:machine_deployment_available_replicas
machine_deployment_ready_replicas
machine_deployment_replicas
machine_deployment_updated_replicas
With these metrics, alerts could be defined that e.g. alert on
machine_deployment_replicas > machine_deployment_updated_replicas
being true for more than 30 minutes (random example here).The text was updated successfully, but these errors were encountered: