See what your alerts are really telling you

One page for all your alerts: which ones are the same problem, which fire together, which are still open, and which are just noise. No dashboards to build, no login to share it.

Add Slack Bot

Get your own alert report. Add the Sherlocks bot to your Slack alert channels. Nothing to install.

Alert report

Sample data
Generated Thu 12 Nov 2026, 10:00
Alerts come fromCloudWatchlast alert 2 min agoAlertmanagerlast alert 6 min agoGrafanalast alert 4 min agoSlack #prod-alerts30 days of history addedEmaillast alert 1 day ago
Alerts789Last 7 days
Kinds of problem8Grouped from 23 alert names
Still open6Oldest open for 3 days
Closed by itself in 5 min61%Likely noise
Fire together2 groupsLikely shared causes

When alerts happened

Each row is one kind of problem. Sherlocks puts alerts with different names in the same row when they mean the same thing. Darker cells mean more alerts in that time slot.

Fewer to more alertsStill openHover a slot to see the count and time.
ProblemAlerts
Database connection limits4 alert names, from CloudWatch and Grafana
76
API slow responses3 alert names, from Alertmanager
74
5xx error spikes2 alert names, from Alertmanager and Grafana
47
Queue backlog2 alert names, from CloudWatch
48
Disk filling up3 alert names, from Alertmanager
70
Cron job missedHeartbeat checks by Sherlocks
5
Node CPU high5 alert names, from CloudWatch and Grafana
466
SSL certificate expirySite checks by Sherlocks
3
Fri 6 NovSat 7 NovSun 8 NovMon 9 NovTue 10 NovWed 11 NovThu 12 Nov

Alerts that fire together

Alerts that start within a few minutes of each other usually share one cause.

Database connection limitsAPI slow responses5xx error spikesQueue backlog

These four fired together 3 times in the last 7 days. Each time, all four started within 4 minutes.

Sat 7 Nov, 13:02Mon 9 Nov, 20:11Wed 11 Nov, 21:06
Disk filling upCron job missed

These two fired together 4 times. Each time, they fired between 02:00 and 03:00.

Most repeated problems

Last 7 days
AlertTimesLast seen
CPU over 85% on worker nodes466this hour
Connection pool full on orders-db768 h ago
p95 latency over 2 s on payments-api7412 h ago
Disk over 80% on 10.0.4.1770this hour
5xx rate over 1% on edge-lb4712 h ago

Still open

6 alerts
Certificate for checkout.shop.example.com expires in 9 daysSite check by Sherlocks
3 days
Queue depth over 10,000 on order-eventsCloudWatch
13 h
Backup job heartbeat missedHeartbeat check by Sherlocks
8 h
Disk over 80% on 10.0.4.17Alertmanager
8 h
CPU over 85% on worker-7Grafana
4 min
Payment webhook errorsEmail. Status unknown, because email alerts do not say when they close.
?

Noise

61%of alerts closed by themselves within 5 minutes. Nobody needed to act on them.
CPU over 85% on worker nodes94% closed by itself
Replica lag over 5 s on orders-db-replica88% closed by itself
5xx rate over 1% on edge-lb71% closed by itself

Tip: add a 5 minute wait before these alerts fire. Most of them will stop.

Flapping alerts

These opened and closed many times today.

CPU over 85% on worker-323 times
5xx rate over 1% on edge-lb11 times
Replica lag over 5 s on orders-db-replica8 times

Time of day

All alerts in the last 7 days, by hour. Busiest hours: 02:00, 13:00, 21:00.

Site checks

Sherlocks checks these every 5 minutes.

SSLcheckout.shop.example.comExpires in 9 days
SSLapi.shop.example.comExpires in 71 days
DNSshop.example.comNo change in 7 days
URLshop.example.com/healthUp · 212 ms
URLapi.shop.example.com/v1/statusDown 4 min on Wed

Get your own alert report

Add the Sherlocks bot to your Slack alert channels. It reads the alerts already posted there and builds this report from them, with no agents to install.

Works with alerts from CloudWatch, Alertmanager, Grafana, Datadog and PagerDuty.

Add Slack BotSherlocks AI is SOC 2 Type 2 certified.

We use cookies

Only the strictly necessary ones are set when you arrive. Analytics and marketing cookies are set solely if you allow them, and you can change your mind at any time. See our Privacy Policy.