View, acknowledge, and close active alarms from the Alarms section. Review closed alarm history and filter by entity, severity, customer, or time range to track incidents and support post-incident analysis.
The Alarms section in Cloudmon is the central place for managing all active and historical alarms across every monitored entity. Alarms are surfaced here as soon as a trigger condition is met, and remain visible until they are acknowledged and closed. All alarms raised for any monitored entity, regardless of monitoring type, appear together in a single unified view.
Navigate to the Alarms menu in the top navigation bar to access the alarms view. The view is split into Open Alarms and Closed Alarms, selectable from the Open/Closed dropdown.
Open Alarms lists all currently active alarms that have not yet been closed. Each alarm entry shows the entity name, description, severity, and the time the alarm was raised. Alarms are colour-coded by severity to make the most critical issues immediately visible.
From the Open Alarms view you can perform the following actions:
| Action | Description |
| Acknowledge | Click the thumbs-up icon on an alarm to acknowledge it, signalling that the issue is being investigated. Clicking the icon again undoes the acknowledgement. Acknowledged alarms remain open until explicitly closed. |
| Close | Close an alarm once the underlying issue has been resolved. When closing, a reason can optionally be entered to support post-incident analysis, auditing, and reporting. Closed alarms move to the Closed Alarms view. |
| Filter | Filter open alarms by entity type, severity level, time range, or customer (in MSP deployments) to focus on a specific subset of alerts. |
| Search | Use the search bar to find specific alarms by entity name or alarm description. |
Closed Alarms lists all alarms that have been resolved and closed, along with the time they were opened, the time they were closed, and any closure reason that was entered. This view is useful for post-incident analysis, compliance auditing, and identifying recurring issues across monitored entities.
Closed alarms can be filtered by entity type, severity, time range, and customer in MSP deployments, making it straightforward to review the alarm history for a specific device, site, or time period.
If an alarm rule trigger is configured with the Close the alarm automatically if condition not met option enabled, Cloudmon will close the alarm automatically when the metric returns to within acceptable limits, without requiring manual intervention. This is particularly useful for transient conditions such as temporary CPU spikes or brief connectivity losses, where the alarm should clear itself once normal operation resumes. Alarms closed automatically appear in the Closed Alarms view alongside manually closed alarms.