Create and manage alarm rules for any monitored entity in Cloudmon. Define threshold-based triggers, configure notifications and automated remediation, associate rules to device groups, and manage default alarm profiles.
Alarm rules in Cloudmon work on a trigger model. You define a condition (the IF) and an action (the THEN). When the condition is met for a specified number of consecutive polling intervals, Cloudmon fires the alarm and executes the configured actions. The consecutive interval requirement prevents momentary spikes from generating alerts, keeping the alarm list focused on genuine, sustained problems.
Alarm rules can be configured at the group level to apply uniform settings across all entities of the same monitoring type, or at the individual entity level for fine-grained control. Cloudmon also includes default alarm profiles that are automatically assigned to monitored entities to provide basic alerting from day one. These default profiles can be cloned and customised, but cannot be edited directly or deleted.
| Field | Description |
| Metric (IF) | The metric to monitor. Available metrics depend on the entity type selected for the alarm rule. Use the search box to locate a metric quickly. |
| Condition | The comparison operator. Select Above or Below to define whether the alarm fires when the metric exceeds or falls below the threshold. |
| Threshold | The value the metric must breach to activate the trigger, entered in the unit shown next to the field. |
| Consecutive Intervals | The number of back-to-back polling cycles the condition must hold before the alarm fires. Setting this above 1 prevents transient spikes from generating unnecessary alerts. |
| Severity (THEN) | The severity level of the alarm. Options are Critical, Trouble, and Attention. |
| Notify To | The users or user groups who will receive a notification when this trigger fires. |
| Third Party Services | Forwards the alarm to a configured integration such as Microsoft Teams, Slack, ServiceNow, SMS via Twilio, or a Custom Hook. Learn more |
| Run Script | Executes a configured runbook automatically when the alarm fires. Select whether to run the script on the controller or on the agent, then select the runbook from the dropdown. Only available for agent-monitored entities. |
| Close automatically if condition not met | When enabled, Cloudmon closes the alarm automatically once the metric no longer meets the trigger condition, with no manual intervention required. |
An alarm rule can be associated with one or more device groups to apply it across all entities of the same type within those groups simultaneously. This eliminates the need to configure the same rule on each entity individually.
To view which entities a rule is currently applied to, click the entities icon next to the rule in the Alarm Rules table.
Cloudmon includes default alarm profiles that are automatically assigned to monitored entities to provide baseline alerting without any manual setup. These profiles cannot be edited directly. To customise a default profile, click the clone icon next to the rule to create an editable copy which can be edited via the edit icon, make the required changes, and save and apply the cloned rule as needed. The cloned alarm rules can also be deleted via the delete icon present among the options.
Cloning is also useful for creating variations of an existing rule for different device types or severity requirements without starting from scratch.
Device dependencies suppress alarm notifications for dependent devices when their parent device is down, preventing a single upstream failure from generating dozens of downstream alerts. To configure a dependency, navigate to Settings → Configurations → Device Dependencies, select the dependent device, specify the device it depends on, and map its dependent monitors to the relationship. Once saved, alerts for the dependent device will be suppressed whenever the parent is unavailable.