Monitor MongoDB Atlas.Hear only when it matters.
Watch the clusters your application depends on.
What Beaam does with MongoDB Atlas
Beaam connects with a read-only Atlas service account and polls the Atlas Admin API every minute — reading each watched cluster's state plus key process and disk measurements. Following the 'curate alarms, be generous with data' principle (ADR-0018), it alerts on a small attention-worthy set and collects more for context and debugging.
What raises an incident
Curated deliberately: a short list worth your attention, not every metric that exists. Signals that can blip need repeated evidence before Beaam calls them; a reading that is definitive by nature — the provider reporting a failure outright — alerts on the first observation.
| Signal | When Beaam speaks up |
|---|---|
| Cluster missing | Atlas no longer has the cluster → broken. Deliberately paused clusters stay quiet by default. |
| Disk used % | ≥ 90% → broken (the cluster can go read-only). |
| Connections % of limit | ≥ 80% of your tier's limit → degraded. |
| Replication lag | ≥ 120s → broken (failover risk, stale reads). |
| CPU % | ≥ 90% sustained → degraded. |
| Native availability alerts | An open Atlas host/replica-set availability alert → broken. |
| Native backup alerts | An open Atlas backup, oplog, snapshot, export, or restore alert → broken. |
Also collected, but quiet
Charted on the service page and there for context when something does break — but it will not wake you unless you ask it to.
- Memory used %
- Query targeting
- Disk queue depth
- WiredTiger tickets
- Disk latency
- Execution queues
- Oplog headroom
- Disk headroom and IOPS
- Operation latency
- CPU steal
What connecting needs
- An Atlas service account (client ID and secret) with the Project Read Only role — or Organization Read Only to discover every project. Not a legacy API key.
- If your organization restricts API access by IP, allow Beaam's egress addresses.
- Shared tiers (M0, M2, M5 and Flex) expose fewer measurements: disk, memory and oplog generally need M10 or above, and shared tiers report no disk at all.
What Beaam will not tell you
Stated rather than discovered later. Some of these are deliberate — an alert that is not about your system is noise — and some are simply where this integration's view ends.
- Sharded and geo-sharded clusters cannot be monitored.
- A paused cluster stays quiet by default.
- Measurements more than 20 minutes old are discarded rather than shown as current.
- Memory, query targeting, queue, IOPS, oplog and disk-free alerts are off by default.
setup
Designed to stay small
Create an Atlas service account with organization read access and paste its client ID and secret. The secret is shown once by Atlas and stored encrypted here.
Beaam applies sensible defaults. Threshold configuration is optional, not onboarding.
access
Never writes, and revocable
Beaam never writes to MongoDB Atlas. Credentials are encrypted with AES-256-GCM using a key held as a deploy secret, and are deleted immediately when you disconnect.
Questions
What does Beaam alert on for MongoDB Atlas?
7 signals can raise an incident: Cluster missing, Disk used %, Connections % of limit, Replication lag, CPU %, Native availability alerts, Native backup alerts. Everything else is collected for context but stays quiet until you opt in.
How long does it take to connect MongoDB Atlas?
Create an Atlas service account with organization read access and paste its client ID and secret. The secret is shown once by Atlas and stored encrypted here. Most connections are watching within a few minutes, and you can send a test alert immediately to prove the path works end to end.
Does Beaam need write access to MongoDB Atlas?
No. Beaam only ever performs read operations — there is no code path that writes to a connected provider. Worth separating from that: what Beaam *does* and what a token *permits* are different things. Where MongoDB Atlas offers a read-scoped credential, use it; some providers only issue tokens carrying broader rights than Beaam uses, which is a property of their API rather than of Beaam's behaviour. Scope it as narrowly as the provider allows. Credentials are encrypted with AES-256-GCM before storage and deleted the moment you disconnect.
What does MongoDB Atlas monitoring cost?
The free plan covers two integrations and five watched services, with email, Slack and webhook alerts. Solo is $19/month flat for unlimited integrations, services and organizations, with collaborators included — there is no per-host, per-check or per-alert metering.
Watching more than MongoDB Atlas?
Most stacks are several services with seams between them, and the seams are where the damaging failures hide. Beaam correlates across every connected integration, so a database problem reads as one incident rather than five alarms from five tools.
Other integrations
Hostinger
Catch Hostinger VPS, website, mail and subscription trouble before customers do.
DigitalOcean
Know when a Droplet is powered off, archived or destroyed — pair it with an HTTP check for the rest.
Vercel
Hear about a failed production deploy — and nothing at all about your preview builds.
All integrations
Everything Beaam watches today, and what is on the roadmap.