Configure Azure Alarm Rules | Cloudmon

Azure Alarm Rules

Setup Guide

Configuring Alarm Rules for Azure

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.

Overview

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:

  • Create the rule. Navigate to Settings → Configurations → Alarm Rules → Add and build the IF/THEN trigger: select a metric, set a threshold, and define what happens when it is breached.
  • Attach it to a resource. Navigate to Cloud → Azure → [Your Azure Account], open the relevant service (Virtual Machines, Storage Account, Blob Storage, Table Storage, File Share, or Queue Storage), select the resource, and click its edit icon. Under Alert Settings, choose the rule from the Alarm Rule dropdown and click Save.

How to Configure an Alarm

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.

Common Use Cases

Below are recommended alarm configurations for the most common Azure monitoring scenarios:

Use CaseMetricSuggested ThresholdWhy
VM high CPUCPU UtilisationAbove 90% for 1 intervalCatches VMs under sustained heavy load before performance degrades
Storage low availabilityAvailabilityBelow 100% for 1 intervalImmediately flags any degradation in storage service availability
High ingress trafficIngressAbove expected baselineIdentifies unusual data write spikes that could indicate unexpected usage or misconfigured applications
High server latencySuccess Server LatencyThe above-defined ms threshold for 2 intervalsDetects storage performance degradation before it impacts dependent applications
Storage capacity is nearly fullUsed CapacityAbove-defined Bytes thresholdPrevents storage limits from being exceeded unexpectedly
Cost threshold exceededActual Total CostAbove budget amount for the MONTHLY periodAlerts when Azure spending exceeds a defined monthly budget before the billing cycle closes

Viewing and Managing Triggers

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.