ARNscopeDocs

CloudWatch alarms

Last updated 13 November 2026

The Alarms page lists every CloudWatch alarm in a profile and region, firing ones first. Open one to see why it fired, its rule in plain words, its metric against the threshold and its state history. Separately, ARNscope can check your alarms in the background across several profiles and regions and post a Mac notification when one trips. The AWS console has nothing like either.

A narrated tour, with captions: the alarm list and detail, background checks, notifications, muting, sign-ins, widgets and refresh. Sample data.

The alarm list

Alarms are sorted by state: In alarm, then Insufficient data, then OK. The state filter shows a count for each, and the search field filters by name. The list comes from one DescribeAlarms call for the region (metric and composite alarms).

Firing alarms first; filter by state or name.

What the states mean

State Shown as In plain words
ALARM In alarm, red The metric crossed the threshold for enough of the recent periods (for example 3 of the last 5). This is the one that needs you.
INSUFFICIENT_DATA Insufficient data, grey CloudWatch doesn’t have enough data points to decide either way. It is not a failure in itself, so ARNscope shows it in a neutral grey, not a warning colour.
OK No chip in the list; OK, green, elsewhere The metric is on the right side of the threshold.

Insufficient data usually means one of these:

When to worry: when the metric should report all the time (CPU of a running instance, a heartbeat your app sends every minute) and the alarm has dropped into insufficient data. Then data has stopped arriving, which can mean the thing it watches has stopped. Open the alarm and check the metric chart for where the line ends and the state history for when it changed. Whether missing data counts as breaching, OK or missing is the alarm’s own setting in CloudWatch.

One alarm

Why it fired, the metric against the threshold, and every change.

Background checks and Mac notifications

Settings → Alarm notifications turns on a light background check. ARNscope is not a monitoring service: this is one small API call per profile and region, run by the app on your Mac.

What is checked, how often, what it costs, and the status of each profile and region.
A click on the notification opens the alarm. (The notification in this clip is drawn: the web preview the clips are recorded from has no macOS notifications.)

Firing across profiles, muting and the rail badge

While checks are on, the top of the alarm list shows Firing across profiles: every firing alarm in every watched profile and region, whichever profile the page is on. Click one to open it. 4 watched opens the settings. Hover an alarm there, or use Notifying on an open alarm, to mute just that alarm; muted alarms never notify, count or show as firing. The rail’s Alarms icon shows how many are firing, on any page.

Firing alarms from every watched profile; mute one with a click.

Expired sign-ins

If a profile’s sign-in (usually an AWS SSO session) expires, its checks pause and its status reads Sign-in expired, paused. You get one notification per expired session, not one per check; clicking it, or Sign in in the settings, runs aws sso login for that session (this needs the AWS CLI) and checks again as soon as you are signed in. A sign-in from a terminal resumes the checks too.

Desktop widgets

ARNscope ships macOS desktop widgets (macOS 14 or later):

Pinning

Pin Where
An alarm The pin in an open alarm’s title bar, Add to macOS widget. On a pinned alarm it reads On the macOS widget: click to remove it.
A metric Hover a chart on the CloudWatch page and use its pin, Add to macOS widget… (one item per metric when a chart has several). The same menu removes it. Metric math can’t be pinned.

Before you add one, the dialog shows the alarm or metric (namespace, statistic and period, profile, region, dimensions), lets you give it a label for the widget, and says what it will read and roughly what it costs a month. A metric’s period is rounded to whole minutes, at least one. The same alarm or metric can’t be pinned twice.

You can have up to 50 pins across all profiles. At the limit the dialog says 50 pins is the limit. Remove one in Settings → Widgets first.

What pins read, and Settings → Widgets

Pinning is what turns on these reads; with nothing pinned, nothing is read. Every 5, 15 (the default) or 30 minutes, per profile and region, ARNscope makes one DescribeAlarms call for the pinned alarms and one GetMetricData call for the pinned metrics and each pinned alarm’s metric. This runs while ARNscope is running, even with its window closed; when it isn’t running, the widgets show when they were last updated. GetMetricData is billed per metric (US$0.01 per 1,000) and is not in the free tier.

Settings → Widgets lists every pin with its last reading, the interval, and the calls and cost a month. Open opens a pin in ARNscope; rename and remove pins there. Each pin’s status reads:

Status Meaning
A value, or an alarm state The last read worked.
Waiting for the first read Just pinned.
No data in the window The read worked but the metric had no recent point.
Sign in to <profile> The profile’s sign-in expired.
Profile not in ~/.aws, not read The pin’s profile is no longer in your AWS config. The pin is kept but not read.
An error message CloudWatch’s error for that read.
Add to widget says the cost first; pins are listed in Settings → Widgets.

Refreshing

The page reads alarms when you open it and when you press refresh. Auto-refresh is off until you pick an interval, and it pauses while the page or window is in the background.

Auto-refresh is opt-in and pauses in the background.

Limitations

Need another kind of alert? Write to [email protected] and tell us what you use.

Permissions

Action Used for
cloudwatch:DescribeAlarms The list, background checks, widget alarms
cloudwatch:DescribeAlarmHistory State history
cloudwatch:GetMetricData The alarm’s metric chart, widget metrics