Integration · Databases
MongoDB
serverStatus, replication lag, oplog window.
What gets collected
A mongostat equivalent via serverStatus plus currentOp for long-running operations.
Requirements
- ✓MongoDB 4.4+
- ✓role: clusterMonitor
- ✓read-only user
Key metrics
Collected out of the box. Every metric is available in dashboards, alerts and PromQL.
mongo.ops.per_secmongo.replication.lagmongo.oplog.windowmongo.connectionsmongo.currentop.longSetup steps
- 1
db.createUser({user:"unimoni", roles:["clusterMonitor"]})
After install
- · Metrics show up on the dashboard within 15-30 seconds
- · Integration labels flow into filters automatically
- · Dashboard presets for common metrics are available in the editor
More in the docs
MongoDB
Frequently asked questions
- What does Unimoni collect from MongoDB?
- serverStatus, replication lag, oplog window. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across MongoDB and everything else in one place.
- How long does it take to connect MongoDB?
- Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
- What access does the MongoDB integration need?
- Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
- Is MongoDB monitoring available self-hosted and on the free plan?
- Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.