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 have examples for under utilized cpu and memory which could be an opportunity to move to a smaller instance size. The same could be said for moving data to a smaller volume without as much space provisioned which could lead to lower costs.
When I initially create the alerts, I was also considering adding an alert for underutilized disk space. However, in on-premise or cloud environments, reducing the volume/disk size is not as straightforward as it is for memory and CPU.
There seems to be alarms for over utilized disk space, but what about under utilized disk space?
https://samber.github.io/awesome-prometheus-alerts/rules#rule-host-and-hardware-1-8
We have examples for under utilized cpu and memory which could be an opportunity to move to a smaller instance size. The same could be said for moving data to a smaller volume without as much space provisioned which could lead to lower costs.
https://samber.github.io/awesome-prometheus-alerts/rules#rule-host-and-hardware-1-15
https://samber.github.io/awesome-prometheus-alerts/rules#rule-host-and-hardware-1-3
The text was updated successfully, but these errors were encountered: