Project Overview¶
The Clusters view displays all clusters in an Atlas project and features core metrics per cluster. You can quickly view metrics in the available charts at a glance to assess cluster health. You can then click into other views and metrics to more specifically identify issues. For more information about the Clusters view, see View Cluster Details.
Monitor cluster metrics to identify performance issues and determine whether your current cluster tier meets your requirements.
Available Charts¶
Atlas displays up to four of the following charts for each cluster in the project:
Atlas stores metrics data at increasing granularity levels. For more information, see Monitoring Data Storage Granularity.
Chart | Data | Use Case |
|---|---|---|
Operations | Displays the aggregated read (R) and write (W) operations on the cluster. For a replica set, the chart shows operations for the primary. For a sharded cluster, the chart shows the sum of the operations on each primary in the cluster. | Monitor performance issues related to high workloads. |
Logical Size
| Displays the sum of total bytes of the documents and index data
across all databases in the cluster. | Monitor the size of the documents and index data on the cluster. |
Disk Usage
| The total bytes of used disk space for the cluster. For a replica set, the chart shows the disk usage of the primary host machine. For a sharded cluster, the chart shows the sum of disk usage on each primary host in the cluster. | Monitor the combined size of your data and MongoDB operational
data (buffer, journal, and log files) on the cluster. |
Total Index Size
| The total bytes of disk space used by indexes for every database
in the cluster. | Monitor the size of all indexes on your cluster. |
Connections | The total number of active connections to the cluster. For a replica set, the chart shows the number of active connections to the primary. For a sharded cluster, the chart shows the sum of all active connections to each primary in the cluster. | Monitor connections to determine whether the current connection limits are sufficient. If necessary, upgrade the cluster tier. |
Disk IOPS
| The sum of read and write input/output operations per second
(IOPS) for the cluster. | Monitor whether disk IOPS approaches the maximum provisioned IOPS. Determine whether the cluster can handle future workloads. |
Disk Latency 1 | The latency, in milliseconds, of the disk partition used
by MongoDB. | Monitor Disk Latency to determine the average amount
of time to read from or write to disk. |
Util % 1 | The percentage of time during which the partition is receiving
and servicing requests. This metric includes requests from all
processes, not just MongoDB processes. | Monitor whether utilization is high. Determine whether to increase the provisioned IOPS or upgrade the cluster. |
1 Clusters which use NVMe SSDs for
storage display Disk Latency and Disk Util % charts using the
maximum value across the physical drives that make up the
RAID. The following
cluster tiers display RAID-based
metrics if they use NVMe:
M80M200M400