View Cluster Metrics¶
Atlas collects and displays metrics for your servers, databases, and MongoDB processes.
The number of servers that Atlas displays on the
Metrics page at any given time depends on the browser
screen size. Use the Toggle Members section to control
which servers Atlas displays. Hover over the
icons to find out which servers they represent.
You can view metrics in the following ways:
- Project Overview
- The Clusters view displays all clusters in an Atlas project and features core metrics per cluster.
- Atlas Replica Sets
- View the metrics for a specific replica set in an Atlas project.
- Atlas Sharded Clusters
- View the metrics for a specific sharded cluster in an Atlas project.
- MongoDB Processes
- View the metrics for a specific MongoDB process in an Atlas cluster.
- Real Time
- View Real Time metrics for a specific Atlas cluster in a project.
- Atlas Search
- View Atlas Search metrics for Atlas clusters with at least one active Atlas Search index.
Monitoring Data Storage Granularity¶
Atlas stores metrics data at increasing granularity levels. For each increasing granularity level, Atlas computes the metrics data based on the averages from the previous granularity level. The length of retention depends on the granularity. Atlas computes the metrics data based on the averages from the previous granularity level.
After 48 hours' worth of data is collected, each group of 60 minutes is compacted into a single unit of an hour. After 63 days, each group of 24 hours is compacted into a single unit of a day.
Metrics data is gathered at a 1-minute granularity. Atlas retains different granularities of metric data for different periods of time:
|Data Period||Duration of Retention|
|1 minute||48 hours|
|5 minutes||48 hours|
|1 hour||63 days|
Atlas retains all database-specific statistics. MongoDB log data is retained at a maximum rate of 2000 lines per 2 minutes.
Free Tier and Shared Cluster Monitoring Considerations¶
M0Free Tier and
M2/M5Shared clusters support a subset of the metrics and charts available. For complete documentation on the limitations of
M0/M2/M5clusters, see Atlas M0 (Free Tier), M2, and M5 Limitations.
- Atlas pauses monitoring for
M0Free Tier clusters which have had no connection activity for 7 days. Monitoring resumes once a successful connection occurs through the Atlas API , Driver,
mongoshell, or Data Explorer.