Atlas: tune alerts so real problems page and noise does not

TL;DR: Default alerts either spam or miss the incident. Set thresholds from your baseline, route by severity, and use maintenance windows. For each firing alert ask: did a human need to act? Confirm Check the metric baseline first.

The error

alert fatigue (ignored pages) or silent incidents (no alert fired).

The fix

1. Thresholds from baseline: e.g. connections above 80% of tier cap sustained 5 minutes, disk above 75%, replication lag above your SLA.
2. Route by severity: page for data-loss risks (replication, backup failures), notify chat for early warnings (disk 75%, slow query uptick).
3. Maintenance windows during deploys and index builds so planned work does not page.
4. Every alert needs a runbook link: what to check first. An alert nobody knows how to answer is noise.

When to use this

• You are seeing this exact error message; match the block above, not just part of it.
• The failing call matches the scenario in the title: Atlas.
• You want the fastest verified fix before digging through logs.

When not to use this

• Your error text differs from the block above; close cousins often have different causes.
• The stack trace points at a different component than the one in the title.
• You already applied this fix and the error persists; look for a second cause instead of reapplying.

Compatibility

• Not pinned to a specific version; follows current Atlas behavior.

Atlas alert configuration (conditions, thresholds, notifications, maintenance windows) per https://www.mongodb.com/docs/atlas/alerts/, verified 2026-09-26.