You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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: