Navigation

View Deployment Metrics

On this page

  • View Metrics
  • Important Metrics
  • Monitoring Data Storage Granularity
  • Free Cluster and Shared Cluster Monitoring Considerations
  • Serverless Instance Monitoring Considerations

Atlas collects and displays metrics for your servers, databases, and MongoDB processes.

Monitor database deployment metrics to identify performance issues and determine whether your current database deployment meets your requirements.

Note

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 S and P icons to find out which servers they represent.

You can view metrics in the following ways:

Project Overview
The Overview tab displays all the database deployments in an Atlas project and features core metrics per database deployment.
Atlas Serverless Instances
View the metrics for a specific serverless instance in an Atlas project.
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 Performance
View real-time performance metrics for a specific Atlas database deployment in a project.
Atlas Search
View Atlas Search metrics for Atlas clusters with at least one active Atlas Search index.

You can monitor the following metrics to quickly gauge the health of your database deployment.

Chart
Description
Connections

Number that indicates the total active connections to the database deployment.

Monitor connections to determine whether the current connection limits are sufficient. If necessary, upgrade the cluster tier.

To learn more, see Fix Connection Issues and Fix Lost Primary.

Disk IOPS

Number that indicates the input operations per second.

Monitor whether disk IOPS approaches the maximum provisioned IOPS. Determine whether the cluster can handle future workloads.

To learn more, see Fix IOPS Issues and Fix Lost Primary.

Disk Usage

Number that indicates the total bytes of used disk space for the cluster.

Monitor the combined size of your data and MongoDB operational data (buffer, journal, and log files) on the cluster.

To learn more, see Fix Storage Issues.

Query Targeting

Number that indicates the efficiency of read operations run on MongoDB.

Monitor query targeting metrics to identify inefficent queries.

To learn more, see Fix Query Issues.

Normalized System CPU

Number that indicates CPU usage of all processes on the node, scaled to a range of 0-100% by dividing by the number of CPU cores.

Monitor CPU usage to determine whether data is retrieved from disk instead of memory.

To learn more, see Fix IOPS Issues, Fix Lost Primary, and Fix CPU Usage Issues.

Oplog GB/Hour

Number that indicates the average rate in gigabytes of oplog data that the primary generates per hour.

Monitor oplog data to determine whether you have to increase the oplog size.

To learn more, see Fix Oplog Issues.

Util %

Percentage of time that requests are issued to and serviced by disk. This metric includes requests from any process, not just MongoDB processes.

Monitor whether utilization is high. Determine whether to increase the provisioned IOPS or upgrade the cluster.

To learn more, see Fix IOPS Issues.

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.

Example

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
1 day
Forever

Atlas retains all database-specific statistics. MongoDB log data is retained at a maximum rate of 2000 lines per 2 minutes.

  • M0 free clusters and M2/M5 shared clusters support a subset of the metrics and charts available. For complete documentation on the limitations of M0/M2/M5 clusters, see Atlas M0 (Free Cluster), M2, and M5 Limitations.
  • Atlas pauses monitoring for M0 free clusters which have had no connection activity for 7 days. Monitoring resumes once a successful connection occurs through the Atlas API, Driver, mongosh, or Data Explorer.
  • Serverless instances support a subset of the metrics and charts available. For complete documentation on the limitations of serverless instances, see Serverless Instance Limitations.
Give Feedback

On this page

  • View Metrics
  • Important Metrics
  • Monitoring Data Storage Granularity
  • Free Cluster and Shared Cluster Monitoring Considerations
  • Serverless Instance Monitoring Considerations