Configuring Alarm Rules for Meraki Monitoring

Configuring Alarm Rules for Meraki Monitoring

Meraki Monitoring

Configuring Alarm Rules for Meraki Monitoring

Set up alarms for Meraki organizations and devices so Cloudmon notifies your team when availability drops, license status changes, or device health metrics breach defined thresholds.

Overview

Meraki devices are monitored through the Meraki API, and their real-time status, uplink health, and license information are polled at regular intervals. Alarm rules can be configured at the organization level or on individual Meraki devices. Cloudmon also surfaces an invalid API key warning banner on the organization overview page if the configured API key becomes invalid, allowing you to catch authentication issues before they result in stale monitoring data.

There are two ways to configure alarm rules for Meraki:

  • Organization level: Navigate to Network → Meraki → [Select Organization] → Alarms tab to view active alarms, or configure rules under Settings → Configurations → Alarm Rules → Add.
  • Individual device: Navigate to Network → Meraki → Devices → [Select Device] and click the edit icon to assign or update the alarm rule for that specific device.

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 Meraki monitoring scenarios:

Use CaseEntityMetricSuggested ThresholdWhy
Meraki device goes offlineDevice (any type)AvailabilityBelow 100% for 1 intervalA Meraki device showing as dormant or offline in the Meraki API means it has lost cloud connectivity, which impacts management and may indicate a WAN or power issue at the site.
Organization license expiring or expiredOrganizationLicense StatusStatus is not OKAn expired Meraki license causes devices to lose cloud management features. Early warning enables renewal before service disruption occurs.
Organization API connectivity lostOrganizationAvailability / DowntimeDowntime greater than 0 for 1 intervalIf the Meraki API becomes unreachable, Cloudmon stops receiving data for all devices in that organization. An alarm surfaces this immediately so the API key and connectivity can be checked.
Meraki appliance uplink downAppliance (MX)Uplink StatusStatus is not active for 1 intervalA failed WAN uplink on a Meraki MX appliance cuts off internet access for the entire site. Immediate alerting is critical for branch office environments.

Viewing and Managing Triggers

Active and historical alarms for a Meraki organization are visible under the Alarms tab within the organization detail page. Active and historical alarms for individual Meraki devices are visible under the Alarms tab within each device detail page. All alarms also appear in the global Alarms view under the Alarms menu in the navigation bar.