CloudWatch Alarms Are Firing. You Open the Dashboard and See Nothing.

Ever been in this situation? You set an alarm. It fires. You open CloudWatch, check the metric — and the graph looks completely normal. No spike, no anomaly, nothing that explains why the alarm fired. You scroll back in time too. Still nothing.

There are many reasons this can happen. Here are three I have seen come up repeatedly.

1. Wrong metric on the dashboard

Your alarm is watching one specific metric, but the dashboard is displaying a different aggregation of that same metric.

For example: the alarm monitors a specific Lambda function's error rate. But the dashboard shows the average error rate across all functions. The spike on one function becomes invisible when averaged across many. You're looking at the right place, but the wrong view.

A useful sanity check — pull the alarm's exact statistic and compare it to your dashboard:

aws cloudwatch describe-alarms \
  --alarm-names "your-alarm-name" \
  --query 'MetricAlarms[0].{Metric:MetricName,Statistic:Statistic,Period:Period,Threshold:Threshold}'

If that returns Statistic: Sum and your dashboard is showing Average, you've found the disconnect.

2. Service went down completely and stopped publishing metrics

CloudWatch fired because of missing data — and the alarm did its job. But there's nothing to see on the metric graph because nothing was being published during that period.

In this case, don't look at the metric. Look at your service health directly. A pod that crashed, a Lambda that stopped being invoked, an ECS task that disappeared — the alarm caught the silence, not a spike.

3. Composite alarm misconfiguration

A composite alarm combines multiple underlying alarms. One of those underlying alarms fired briefly and recovered within seconds — triggering the composite. By the time you open the dashboard, everything is green again and the moment has passed.

Set retention or notification on the underlying alarms, not just the composite, so you can see what actually fired.

Why this matters more than it looks

Alarms that fire without a clear cause train engineers to stop taking them seriously — and that is exactly when a real incident gets missed.

The cost of a noisy alarm isn't the noise. It's the muscle memory it builds.

If you have ever encountered this, what did you do to identify the issue?