Cloudmon's alarm system provides early warning across your entire monitored infrastructure. Configure threshold-based rules, reduce alert noise with consecutive interval logic, automate remediation, and manage open and closed alarms from a single view.
Cloudmon significantly reduces alarm noise by only firing when a condition persists across a defined number of consecutive polling intervals, not on every momentary spike. This approach reduces IT operator fatigue and keeps the alarm list focused on real, sustained problems. Default alarm profiles are automatically assigned to monitored entities to provide basic alerting from day one, and can be cloned and customised as needed.
Where to find it: Active and historical alarms are accessible from the Alarms menu in the top navigation bar. Alarm rules are configured under Settings → Configurations → Alarm Rules.
Threshold-based rules Define IF/THEN triggers on any metric across any monitored entity. Set severity, notification recipients, third party services, and automated runbook execution. | Noise reduction Consecutive interval logic ensures alarms fire only on sustained conditions, not transient spikes. Default profiles can be cloned and tailored to your environment. | Automated remediation Attach runbooks to alarm triggers to automatically restart services, clear caches, or run any custom script when an alarm fires on an agent-monitored device. |
Group-level coverage Associate alarm rules with device groups to apply consistent settings across all entities of the same type without configuring each one individually. | Acknowledgement and closure Acknowledge active alarms to signal they are being worked on, and close them with an optional reason for post-incident tracking and audit. | Device dependencies Suppress notifications for dependent devices when their parent device is down, preventing cascading alarm noise from a single upstream failure. |