Set up alarms to be notified when your Azure resources exceed defined thresholds. Alarm rules are created centrally and can be attached to any individual monitored resource.
Cloudmon alarm rules work on a trigger model. You define a condition (the IF) and an action (the THEN). When the condition is met for the specified number of consecutive intervals, Cloudmon fires the alarm and executes the configured actions, such as sending a notification or running a script.
Alarm rules for Azure resources are created and configured in one place, then attached wherever needed:
Each alarm rule is built around a simple IF/THEN model: select a metric, set a threshold, and define what happens when it's breached. This is done once when creating the rule under Settings → Configurations → Alarm Rules. Attaching that rule to one resource or to many is just a matter of selecting it from the Alarm Rule dropdown wherever it's needed. Learn more.
Below are recommended alarm configurations for the most common Azure monitoring scenarios:
| Use Case | Metric | Suggested Threshold | Why |
| VM high CPU | CPU Utilisation | Above 90% for 1 interval | Catches VMs under sustained heavy load before performance degrades |
| Storage low availability | Availability | Below 100% for 1 interval | Immediately flags any degradation in storage service availability |
| High ingress traffic | Ingress | Above expected baseline | Identifies unusual data write spikes that could indicate unexpected usage or misconfigured applications |
| High server latency | Success Server Latency | The above-defined ms threshold for 2 intervals | Detects storage performance degradation before it impacts dependent applications |
| Storage capacity is nearly full | Used Capacity | Above-defined Bytes threshold | Prevents storage limits from being exceeded unexpectedly |
| Cost threshold exceeded | Actual Total Cost | Above budget amount for the MONTHLY period | Alerts when Azure spending exceeds a defined monthly budget before the billing cycle closes |
All alarm rules, along with the triggers configured within them, are listed under Settings → Configurations → Alarm Rules. Each rule shows its name, severity, whether notifications are configured, and whether a script is set to run when triggered. You can edit or delete any rule at any time using the action icons on the right. To see which rule is currently attached to a specific Azure resource, open that resource's edit panel and check the Alarm Rule field under Alert Settings.