// MongoDB Atlas integration
Watch the clusters your application depends on.
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.
Curated deliberately: a short list worth your attention, not every metric that exists. Each one needs repeated evidence before Beaam calls it — a single bad reading is not an incident.
| Signal | When Beaam speaks up |
|---|---|
| Cluster up/down | Paused or unreachable → broken. |
| 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. |
Charted on the service page and there for context when something does break — but it will not wake you unless you ask it to.
setup
Connect an Atlas API key with organization read access.
Beaam applies sensible defaults. Threshold configuration is optional, not onboarding.
access
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.
5 signals can raise an incident: Cluster up/down, Disk used %, Connections % of limit, Replication lag, CPU %. Everything else is collected for context but stays quiet until you opt in.
Connect an Atlas API key with organization read access. Most connections are watching within a few minutes, and you can send a test alert immediately to prove the path works end to end.
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.
The free plan covers two integrations and five watched services, with email, push, Slack and webhook alerts. Solo is $19/month flat for unlimited integrations and services, adding SMS — there is no per-host, per-check or per-alert metering.
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.
Find out your VPS was suspended before your customers do.
Know when a Droplet is powered off, archived or destroyed — pair it with an HTTP check for the rest.
Hear about a failed production deploy — and nothing at all about your preview builds.
Everything Beaam watches today, and what is on the roadmap.