Azure Alarm Rules

Azure Alarm Rules

Setup Guide

Configuring Alarm Rules for Azure

Set up alarms to be notified when your Azure resources exceed defined thresholds. Alarms can be configured at a group level or directly on individual monitored resources.

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.

There are two ways to configure alarm rules for Azure resources:

  • Group level: applies the alarm rule across multiple resources of the same type. Navigate to Settings → Configurations → Alarm Rules → Add.
  • Individual resource: applies the alarm rule to a single specific resource. Navigate to Cloud → Azure → [Select Account] → [Select Resource] → Settings → Alarm Rule → Add Trigger.

How to Configure an Alarm

Each alarm is built around a simple IF/THEN model, where you select a metric, set a threshold, and define what happens when it is breached. 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

Once saved, all triggers for a resource are listed in the Triggers table under the Alarm Rule section. Each row shows the trigger title, alarm severity, whether notifications are configured, and whether a script is set to run. You can edit or delete any trigger at any time using the action icons on the right.

    • Related Articles

    • Azure Monitoring

      Microsoft Azure Azure Cloud Monitoring with Cloudmon Connect your Azure account once and get full visibility into your Virtual Machines, storage services, and subscriptions — with real-time metrics, Advisor Recommendations, and historical performance ...
    • AWS Alarm Rules

      Setup Guide Configuring Alarm Rules for AWS Set up alarms to be notified when your AWS resources exceed defined thresholds. Alarms can be configured at a group level or directly on individual monitored resources. Overview Cloudmon alarm rules work on ...
    • When is an alarm triggered in cloudmon?

      An alarm is triggered based on the configuration of the corresponding alarm rule when an IP endpoint or device exceeds the threshold value that has been set. In other words, when the monitored metric goes beyond the defined limit, the alarm will be ...
    • How does the user get notified when an alarm is triggered in cloudmon?

      We provide the following options for notifying the user when an alarm is triggered, Email Microsoft Teams Slack Zoho Desk SMS Webhook
    • Actions in Azure Monitoring

      Setup Guide Actions in Azure Monitoring Manage your connected Azure Accounts — edit configuration, re-run discovery, enable or disable monitoring, or remove an account entirely. Overview All actions in Azure monitoring are performed from the probe ...