> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt # Review Alert Conditions This page describes the conditions for which you can trigger alerts. You specify conditions and thresholds when [configuring alerts](https://www.mongodb.com/docs/atlas/configure-alerts.md#std-label-configure-alerts). To learn more, see [Alerts Workflow.](https://www.mongodb.com/docs/atlas/alerts.md#std-label-alerts-workflow) For the alert conditions available on Atlas Infinite clusters, see [Atlas Infinite Alerts.](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-atlas-infinite-alerts) **Note:** Free clusters and Flex clusters only trigger alerts related to the metrics supported by those clusters. For complete documentation on Free clusters and Flex clusters alert and metric limitations, see [Atlas Free Cluster Limits](https://www.mongodb.com/docs/atlas/reference/free-shared-limitations.md#std-label-atlas-free-tier), and [Atlas Flex Limitations.](https://www.mongodb.com/docs/atlas/reference/flex-limitations.md#std-label-flex-cluster-limitations) ## Host Alerts The conditions in this section apply if you select Host as the alert target when configuring the alert. You can apply the condition to all hosts or to specific type of host, such as [primaries](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-primary) or [config servers.](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-config-server) Atlas triggers certain host alerts based on cluster monitoring, and are thus subject to variations in granularity. To learn more, see [Monitoring Data Storage Granularity.](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitoring-storage-granularity) ### Advisor Raised if [Performance Advisor](https://www.mongodb.com/docs/atlas/performance-advisor.md#std-label-performance-advisor) has index suggestions for the host. If the [query targeting ratio](https://www.mongodb.com/docs/atlas/reference/alert-resolutions/query-targeting.md#std-label-query-targeting-resolution) for a host is greater than 8000 and if Performance Advisor determines that the host benefits from one or more indexes to improve performance of inefficient queries, this alert triggers and directs you to create the suggested indexes. This alert is only available for `M10+` clusters, and is enabled by default for `M10+` clusters that have [Performance Advisor](https://www.mongodb.com/docs/atlas/performance-advisor.md#std-label-performance-advisor) enabled. This alert does not trigger for clusters where Performance Advisor is disabled. ### Asserts The following alert conditions measure the rate of asserts for a MongoDB process, as collected from the MongoDB `serverStatus` command's [`asserts`](https://www.mongodb.com/docs/manual/reference/command/serverStatus.md#mongodb-serverstatus-serverstatus.asserts) document. You can view asserts through [cluster monitoring.](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics) Raised if the rate of message asserts meets the specified threshold. Message asserts are internal server errors. Stack traces are logged for these. Raised if the rate of regular asserts meets the specified threshold. Raised if the rate of errors generated by users meets the specified threshold. Raised if the rate of warnings meets the specified threshold. ### Auto-Scaling You can configure alerts for the following cluster events. [View the activity feed](https://www.mongodb.com/docs/atlas/tutorial/activity-feed.md#std-label-view-activity-feed) to review all auto-scaling events that occurred. For each event in this section, to receive alerts, you must first configure an alert to notify you or members of your organization of this type of an auto-scaling event. To learn how Atlas scales a cluster up or down, see [Auto-Scaling for Atlas Clusters.](https://www.mongodb.com/docs/atlas/cluster-autoscaling.md#std-label-cluster-autoscaling) Raised if Atlas starts compute auto-scaling for any of the [operational nodes](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-operational-node) in your dedicated cluster. Atlas can scale disk capacity as part of this event. Raised if Atlas starts compute auto-scaling for any of the [analytics nodes](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-analytics-node) in your dedicated cluster. Atlas can scale disk capacity as part of this event. Raised if Atlas couldn't start compute auto-scaling for any of the [operational nodes](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-operational-node) in your dedicated cluster as the configured storage size isn't supported by the target cluster tier. Raised if Atlas couldn't start compute auto-scaling for any of the [analytics nodes](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-analytics-node) in your dedicated cluster as the configured storage size isn't supported by the target cluster tier. Raised if Atlas couldn't scale up an [operational node](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-operational-node) because your cluster reached a maximum cluster tier configured for auto-scaling. Raised if Atlas couldn't scale up an [analytics node](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-analytics-node) because your cluster reached a maximum cluster tier configured for auto-scaling. Raised if Atlas couldn't scale up an [operational node](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-operational-node) due to insufficient [oplog](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-oplog) size. To learn more, see [Set Minimum Oplog Window.](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-set-oplog-min-window) Raised if Atlas couldn't scale up an [analytics node](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-analytics-node) due to insufficient [oplog](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-oplog) size. To learn more, see [Set Minimum Oplog Window.](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-set-oplog-min-window) Raised if Atlas starts predictive compute auto-scaling for any of the [operational nodes](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-operational-node) in your dedicated cluster. Raised if Atlas couldn't predictively scale up an [operational node](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-operational-node) because your cluster reached a maximum cluster tier configured for auto-scaling. Raised if Atlas couldn't predictively scale up an [operational node](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-operational-node) due to insufficient [oplog](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-oplog) size. To learn more, see [Set Minimum Oplog Window.](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-set-oplog-min-window) Raised if Atlas starts auto-scaling disk capacity. Raised if Atlas couldn't scale up the disk size because the cluster has reached maximum available disk size. Raised if Atlas couldn't scale up the disk size because the cluster's [oplog](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-oplog) size isn't sufficient. ### Write-Blocking The following alert conditions apply to [write-blocking behavior](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md#std-label-iwm-always-on-protections) in Atlas. Raised when the percentage of used disk on the primary node has exceeded [write-blocking thresholds](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md#std-label-iwm-always-on-protections). Atlas [blocks writes](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md#std-label-iwm-always-on-protections) to the cluster node to maintain read availability. To resolve this alert, increase your cluster's storage capacity manually or by enabling storage auto-scaling. To learn more, see [Disk Space % Used Alert Resolution.](https://www.mongodb.com/docs/atlas/reference/alert-resolutions/disk-space-used.md#std-label-disk-space-used) To prevent future write-blocking events, we recommend that you monitor your cluster's disk usage. To learn more, see [Preventing Write-Blocking.](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md#std-label-iwm-always-on-protections) Raised when the percentage of used disk on the primary nodes of the affected shards in a [sharded cluster](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-sharded-cluster) has exceeded [write-blocking thresholds](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md#std-label-iwm-always-on-protections). Atlas [blocks writes](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md#std-label-iwm-always-on-protections) to the affected shards to maintain read availability. To resolve this alert, increase your cluster's storage capacity manually or by enabling storage auto-scaling. To learn more, see [Disk Space % Used Alert Resolution.](https://www.mongodb.com/docs/atlas/reference/alert-resolutions/disk-space-used.md#std-label-disk-space-used) To prevent future write-blocking events, we recommend that you monitor your cluster's disk usage. To learn more, see [Preventing Write-Blocking.](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md#std-label-iwm-always-on-protections) Raised when the percentage of used disk on the primary node has fallen below the [unblocking thresholds](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md#std-label-iwm-always-on-protections), and Atlas automatically [unblocks writes](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md#std-label-iwm-always-on-protections) to the cluster. You can view disk metrics through [Real-Time Performance Panel Set](https://www.mongodb.com/docs/atlas/real-time-performance-panel.md#std-label-real-time-metrics-status-tab). This is an information-only alert that doesn't require any action on your part. However, to prevent future write-blocking events, we recommend that you monitor your cluster's disk usage. To learn more, see [Preventing Write-Blocking.](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md#std-label-iwm-always-on-protections) ### Intelligent Workload Management The following alert conditions measure [Intelligent Workload Management (IWM)](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md#std-label-intelligent-workload-management) protections that protect your cluster from overload. Atlas enables these alerts by default for all Dedicated clusters running MongoDB 9.0 or later. Atlas manages the conditions, thresholds, and durations for these alerts. You can't change them. You can change the notification recipients and delivery methods, and you can disable the alert setting. To learn more, see [Configure Alert Settings.](https://www.mongodb.com/docs/atlas/configure-alerts.md#std-label-configure-alerts) Raised if Atlas rejects operations or connections for at least 10 minutes to protect the cluster from sustained overload. Atlas evaluates operations and connections independently, and raises the alert when rejected admissions in a rolling 60-second window are both at least 100 and at least 5% of attempted admissions. To resolve this alert, review cluster load, client retry behavior, connection or operation storms, and capacity. Consider enabling or increasing [auto-scaling](https://www.mongodb.com/docs/atlas/cluster-autoscaling.md#std-label-cluster-autoscaling). To learn configure the Load Shedding setting, see [Configure Intelligent Workload Management.](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-load-shedding-setting) Raised if incoming operations wait an average of 50 milliseconds or more in the ingress queue for at least 10 minutes. To resolve this alert, review client retry behavior and traffic bursts, reduce unnecessary background load, or add capacity. Raised if the 95th percentile of time that operations wait in execution-control queues is 100 milliseconds or more for at least 10 minutes. To resolve this alert, reduce background or expensive work, investigate slow operations, or add capacity. ### MongoDB Search The following alert conditions measure the amount of CPU and memory used by MongoDB Search processes. You can view MongoDB Search metrics through [cluster monitoring.](https://www.mongodb.com/docs/atlas/review-atlas-search-metrics.md#std-label-review-atlas-search-metrics) Raised if the approximate number of milliseconds that MongoDB Search is behind in replicating changes from the [oplog](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-oplog) of [`mongod`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#mongodb-binary-bin.mongod) is above or below the threshold. Raised if the total size of all MongoDB Search indexes on disk in bytes is above or below the threshold. Raised if initial sync is interrupted by the MongoDB Search `mongot` process due to high disk utilization. Raised if disk usage on a search node is greater than or equal to 85%. Raised if the maximum number of unique fields (including metadata) found in any single MongoDB Search index on a replica set or shard is above or below the specified number of fields (default is above 1,000 fields). Raised if the maximum number of fields indexed using `nGram` or `edgeGram` tokenizers (including [autocomplete](https://www.mongodb.com/docs/search/indexes/field-types/autocomplete-type.md#std-label-bson-data-types-autocomplete) type fields and [custom analyzers](https://www.mongodb.com/docs/search/indexes/analyzers/custom.md#std-label-custom-analyzers)), on a replica set or shard, is above or below the specified number of fields (default is above 100 fields). Raised if the upper bound on the number of Lucene docs used to store MongoDB Search indexes for a given replica set or shard is above the threshold. This count includes documents marked for deletion in Lucene, but not yet removed by the index deletion process. Raised if the replication is interrupted by the MongoDB Search `mongot` process due to high disk utilization. Raised if the number of queries for which MongoDB Search is unable to return a response is above or below the threshold. Raised if the number of queries for which MongoDB Search successfully returned a response is above or below the threshold. Raised if the number of queries submitted to MongoDB Search is above or below the threshold. Raised if the total number of documents or fields (specified in the index definition) removed per second is above or below the threshold. Raised if the total number of `getmore` commands run on all MongoDB Search queries per second is above or below the threshold. Raised if the total number of documents or fields (specified in the index definition) that MongoDB Search indexes per second is above or below the threshold. Raised if the total number of documents or fields (specified in the index definition) that MongoDB Search updates per second is above or below the threshold. Raised if your cluster runs out of enough free disk space to support your MongoDB Search indexes. Raised if the total bytes of resident memory occupied by the MongoDB Search process is above or below the threshold. Raised if the total bytes of shared memory occupied by the MongoDB Search process is above or below the threshold. Raised if the total bytes of virtual memory occupied by the MongoDB Search process is above or below the threshold. Raised if the percentage of time the CPU spent servicing operating system calls for the MongoDB Search process is above the threshold. Raised if the percentage of time the CPU spent servicing the MongoDB Search process is above the threshold. Raised if the total bytes of disk space used by the MongoDB Search process is above the threshold. **Note:** If you apply the condition to all hosts, it applies to [dedicated Search Nodes](https://www.mongodb.com/docs/search/deployment/deployment-options.md#std-label-what-is-search-node) as well. Raised if the search process (`mongot`) runs out of memory. If the search process runs out of memory, indexing and queries fail. Default alert that raises a WARNING. This alert occurs when the rate of search queries that exceed the search node's admission control queue threshold is greater than 0. When this alert is raised, the MongoDB Search process (`mongot`) is overloaded and search queries are being queued and could be rejected. Queries might be slower than usual until load decreases. The alert is raised after the condition persists for 5 minutes. **Suggested Actions:** - Upgrade to a [Search Nodes](https://www.mongodb.com/docs/search/deployment/deployment-options.md#std-label-what-is-search-node) tier with more vCPUs. If you are not using Search Nodes, add them for workload isolation. - Reduce concurrent queries or spread queries out over time. - Optimize queries by implementing filtering, reducing leading wildcards and heavily nested clauses, and retrieving only necessary data. To learn how Atlas queues and rejects search queries during overload, and how to handle rejected queries in your application, see [Query Load Shedding and Query Rejection.](https://www.mongodb.com/docs/search/performance/load-shedding.md#std-label-search-load-shedding) ### Average Execution Time The following alert conditions measure the average execution time of reads, writes, or commands for a MongoDB process, as collected from the MongoDB `serverStatus` command's [`opLatencies`](https://www.mongodb.com/docs/manual/reference/command/serverStatus.md#mongodb-serverstatus-serverstatus.opLatencies) document. You can view asserts through [cluster monitoring.](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics) Average execution time for command operations meets your specified threshold. Average execution time for read operations meets your specified threshold. Average execution time for write operations meets your specified threshold. ### Disk Throughput The following alert conditions measure the disk read and write throughput for a MongoDB process. You can view these metrics on the Atlas Disk Throughput chart, accessed through [cluster monitoring.](https://www.mongodb.com/docs/atlas/review-available-metrics.md#std-label-review-available-metrics) *Applicable for Atlas Core Only* Raised if the rate at which data is read from disk in Megabytes per second meets the specified threshold. Raised if the rate at which data is written to disk in Megabytes per second meets the specified threshold. ### Opcounter The following alert conditions measure the rate of database operations on a MongoDB process since the process last started, as collected from the MongoDB `serverStatus` command's [`opcounters`](https://www.mongodb.com/docs/manual/reference/command/serverStatus.md#mongodb-serverstatus-serverstatus.opcounters) document. You can view opcounters through [cluster monitoring.](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics) Raised if the rate of commands performed meets the specified threshold. Raised if the rate of deletes meets the specified threshold. Raised if the rate of `getmore` operations to retrieve the next cursor batch meets the specified threshold. **See also:** To learn more, see [Cursor Batches](https://www.mongodb.com/docs/manual/core/cursors/#cursor-batches) in the MongoDB manual. Raised if the rate of inserts meets the specified threshold. Raised if the rate of queries meets the specified threshold. Raised if the rate of updates meets the specified threshold. ### Opcounter - Repl The following alert conditions measure the rate of database operations on MongoDB [secondaries](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-secondary), as collected from the MongoDB `serverStatus` command's [`opcountersRepl`](https://www.mongodb.com/docs/manual/reference/command/serverStatus.md#mongodb-serverstatus-serverstatus.opcountersRepl) document. You can view these metrics on the Opcounters - Repl chart, accessed through [cluster monitoring.](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics) *Applicable for Atlas Core Only* Raised if the rate of replicated commands meets the specified threshold. Raised if the rate of replicated deletes meets the specified threshold. Raised if the rate of replicated inserts meets the specified threshold. Raised if the rate of replicated updates meets the specified threshold. Raised if the rate of total operations meets the specified threshold. ### Operations Scan and Order You might set alerts for the scan and order operations for a MongoDB process. Average rate per second over your specified threshold of queries that return sorted results that can't perform the sort operation using an index. **Note: How It's Measured** MongoDB reports on the Replication Oplog using the `metrics.operation.scanAndOrder` document that the [serverStatus](https://www.mongodb.com/docs/manual/reference/command/serverStatus/) command returns. On an Atlas Infinite cluster, this metric describes the compute node rather than the storage layer. To learn more, see [MongoDB Atlas Infinite: Architecture.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-architecture.md#std-label-atlas-infinite-architecture) ### Atlas Free Clusters Raised if the total size of the data and indexes is outside the specified threshold. *Applicable for Atlas Free Clusters Only* ### Memory The following alert conditions measure memory for a MongoDB process, as collected from the MongoDB `serverStatus` command's [`mem`](https://www.mongodb.com/docs/manual/reference/command/serverStatus.md#mongodb-serverstatus-serverstatus.mem) document. You can view these metrics on the Atlas Memory and Non-Mapped Virtual Memory charts, accessed through [cluster monitoring.](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics) Raised if the size of virtual memory that is not accounted for by memory-mapping meets the specified threshold. If this number is very high (multiple gigabytes), it indicates that excessive memory is being used outside of memory mapping. **See also:** To learn how to use this metric, view the Non-Mapped Virtual Memory chart and click the chart's i icon. Raised if the size of the resident memory meets the specified threshold. It is typical over time, on a dedicated database server, for the size of the resident memory to approach the amount of physical RAM on the box. Raised if the size of virtual memory for the [`mongod`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#mongodb-binary-bin.mongod) process meets the specified threshold. You can use this alert to flag excessive memory outside of memory mapping. **See also:** To learn more, click the Memory chart's i icon. Raised if the amount of available system memory drops below the specified threshold. Raised if the maximum amount of available system memory drops below the specified threshold. Raised if the maximum system memory usage value meets the specified threshold. Raised if the total system memory used minus buffers, cached, and free memory meets the specified threshold. ### Connections The following alert condition measures connections to a MongoDB process, as collected from the MongoDB `serverStatus` command's [`connections`](https://www.mongodb.com/docs/manual/reference/command/serverStatus.md#mongodb-serverstatus-serverstatus.connections) document. You can view this metric on the Atlas Connections chart, accessed through [cluster monitoring.](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics) Raised if the number of active connections to the host meets the specified average. Raised if the number of open connections to the host exceeds the specified percentage. Raised when the cluster experiences sustained connection rejections due to [Intelligent Workload Management](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md#std-label-intelligent-workload-management) connection rate limiting. This alert indicates that the rate of incoming connection requests exceeds the cluster's configured limits, and the system is protecting itself from overload. When this alert triggers, consider the following actions: - Throttle connection establishment in your application code. - Reduce the `maxPoolSize` setting in your connection string to limit concurrent connections per client. - Scale up your cluster tier to increase connection capacity. To monitor connection rate limiting metrics, view the Connection Rate Limiting charts in the [cluster metrics view](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics). You can also track these metrics through [DataDog integration](https://www.mongodb.com/docs/atlas/tutorial/datadog-integration.md#std-label-datadog-integration) or other third-party integrations. ### Queues The following alert conditions measure operations waiting on locks, as collected from the MongoDB `serverStatus` command's [`globalLock`](https://www.mongodb.com/docs/manual/reference/command/serverStatus.md#mongodb-serverstatus-serverstatus.globalLock) document. You can view these metrics on the Atlas Queues chart, accessed through [cluster monitoring.](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics) *Applicable for Atlas Core Only* Raised if the number of operations waiting on a [read lock](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-read-lock) meets the specified average. Raised if the number of operations waiting on a [lock](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-lock) of any type meets the specified average. Raised if the number of operations waiting on a [write lock](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-write-lock) meets the specified average. ### Page Faults The following alert condition measures the rate of page faults for a MongoDB process, as collected from the MongoDB `serverStatus` command's [`extra_info.page_faults`](https://www.mongodb.com/docs/manual/reference/command/serverStatus.md#mongodb-serverstatus-serverstatus.extra_info.page_faults) field. *Applicable for Atlas Core Only* Raised if the rate of page faults (whether or not an exception is thrown) meets the specified threshold. You can view this metric on the Atlas Page Faults chart, accessed through [cluster monitoring.](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics) ### Database Profiler The following alert condition applies to the [Database Profiler](https://www.mongodb.com/docs/manual/tutorial/manage-the-database-profiler.md#std-label-database-profiler) configuration that can significantly impact performance. **Note:** This alert applies to the [Database Profiler](https://www.mongodb.com/docs/manual/tutorial/manage-the-database-profiler.md#std-label-database-profiler), not the Atlas [Query Profiler](https://www.mongodb.com/docs/atlas/tutorial/query-profiler.md#std-label-query-profiler). The Database Profiler is a MongoDB feature that writes profiling data to the `system.profile` collection. The Atlas Query Profiler is an Atlas UI feature that analyzes slow queries from your `mongod` logs. Raised when the [Database Profiler](https://www.mongodb.com/docs/manual/tutorial/manage-the-database-profiler.md#std-label-database-profiler) is configured to capture all operations on a host. This occurs when the profiler level is set to `2` (profile all operations), or when the profiler level is set to `1` (profile slow operations) with `slowms` set to `0` or less. Profiling all operations can cause significant performance degradation and increased disk usage due to writes to the `system.profile` collection. This alert is enabled by default for all projects. To resolve this alert, disable the Database Profiler or adjust it to profile only slow operations with an appropriate `slowms` threshold (typically 100 milliseconds or higher). Use [`db.setProfilingLevel()`](https://www.mongodb.com/docs/manual/reference/method/db.setProfilingLevel.md#mongodb-method-db.setProfilingLevel) to change the profiler settings. To learn more, see [Database Profiler.](https://www.mongodb.com/docs/manual/tutorial/manage-the-database-profiler.md#std-label-database-profiler) ### Cursors The following alert conditions measure the number of [cursors](https://www.mongodb.com/docs/manual/core/cursors/) for a MongoDB process, as collected from the MongoDB `serverStatus` command's [`metrics.cursor`](https://www.mongodb.com/docs/manual/reference/command/serverStatus.md#mongodb-serverstatus-serverstatus.metrics.cursor) document. You can view these metrics on the Atlas Cursors chart, accessed through [cluster monitoring.](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics) Raised if the number of cursors the server is maintaining for clients meets the specified average. Raised if the number of timed-out cursors the server is maintaining for clients meets the specified average. ### Network The following alert conditions measure throughput for MongoDB process, as collected from the MongoDB `serverStatus` command's [`network`](https://www.mongodb.com/docs/manual/reference/command/serverStatus.md#mongodb-serverstatus-serverstatus.network) document. You can view these metrics on a host's Network chart, accessed through [cluster monitoring.](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics) Raised if the number of bytes sent *to* MongoDB meets the specified threshold. Raised if the number of bytes sent *from* MongoDB meets the specified threshold. Raised if the number of requests sent to MongoDB meets the specified average. ### Replication Oplog The following alert conditions apply to the MongoDB process's [oplog](https://www.mongodb.com/docs/manual/core/replica-set-oplog/). You can view these metrics on the following charts, accessed through [cluster monitoring:](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics) - Oplog GB/Hour - Replication Headroom - Replication Lag - Replication Oplog Window **Note:** On an Atlas Infinite cluster, the oplog doesn't serve replication; the storage layer replicates your data instead. To learn more, see [Oplog on Atlas Infinite clusters.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-architecture.md#std-label-atlas-infinite-oplog) The following alert conditions apply to the oplog: Raised when the amount of data per hour being written to a primary's oplog meets the specified threshold. Raised when the difference between the sync source member's oplog window and the replication lag time on the secondary meets the specified threshold. Raised if the approximate amount of time that the [secondary](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-secondary) is behind the primary meets the specified threshold. Atlas calculates replication lag using the approach described in [Check the Replication Lag](https://www.mongodb.com/docs/manual/tutorial/troubleshoot-replica-sets.md#std-label-replica-set-replication-lag) in the MongoDB manual. Raised if the approximate amount of time available in the [primary's](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-primary) replication [oplog](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-oplog) meets the specified threshold. ### DB Storage The following alert conditions apply to database storage, as collected for a MongoDB process by the MongoDB [dbStats](https://www.mongodb.com/docs/manual/reference/command/dbStats/) command. For details on how Atlas handles reaching database storage limits, refer to the [FAQ page](https://www.mongodb.com/docs/atlas/reference/faq/storage.md#std-label-faq-storage-limit). These conditions are based on the summed total of **all databases** on the MongoDB process: **Note:** Atlas retrieves database metrics every 20 minutes by default but adjusts frequency when necessary to reduce the impact on database performance. Raised if approximate size of all documents (and their paddings) meets the specified threshold. Raised if the allocated storage meets the specified threshold. This alert condition can be viewed on a host's DB Storage chart, accessed through [cluster monitoring.](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics) *Applicable for Atlas Core Only* ### Atlas Infinite Alerts The following alert conditions are available on Atlas Infinite clusters. Storage conditions measure the cluster's storage layer, which Atlas manages independently of the compute nodes. All other conditions measure the compute nodes. To learn more, see [MongoDB Atlas Infinite: Architecture.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-architecture.md#std-label-atlas-infinite-architecture) Raised if the [logical data size](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-storage.md#std-label-atlas-logical-data-size) of an Atlas Infinite cluster, as a percentage of the cluster's [max storage limit](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-storage.md#std-label-atlas-infinite-max-storage-limit), exceeds the specified threshold. Atlas configures this alert condition by default at a threshold of 90% for new projects. To learn more about storage on Atlas Infinite clusters, see [Manage Storage on an Atlas Infinite Cluster.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-storage.md#std-label-atlas-infinite-storage) Raised if the percentage of the cluster's [max storage limit](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-storage.md#std-label-atlas-infinite-max-storage-limit) that remains free meets the specified threshold. Raised if the [logical data size](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-storage.md#std-label-atlas-logical-data-size) of an Atlas Infinite cluster, in bytes, meets the specified threshold. Raised if the amount of free storage space, in bytes, meets the specified threshold. Raised if the average rate of read operations per second against the storage layer meets the specified threshold. Raised if the average rate of write operations per second against the storage layer meets the specified threshold. Raised if the average latency of reads from the storage layer, in milliseconds, meets the specified threshold. Raised if the average latency of writes to the storage layer, in milliseconds, meets the specified threshold. Raised if the average rate, in bytes per second, of data read from the storage layer meets the specified threshold. Raised if the average rate, in bytes per second, of data written to the storage layer meets the specified threshold. Raised if the percentage of consumed throughput to the storage layer meets the specified threshold. Raised if the cache pressure that a compute node experiences, expressed as a percentage and capped at 100%, meets the specified threshold. Available for MongoDB 9.0 or later. Raised if the average time, in milliseconds, that write operations wait to satisfy their majority write concern meets the specified threshold. Elevated values indicate that replication acknowledgment is slow. To learn more about write concern on Atlas Infinite clusters, see [Write Concern on Atlas Infinite clusters.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-architecture.md#std-label-atlas-infinite-write-concern) Raised if the average time, in milliseconds, that operations wait in the ingress admission queue before processing meets the specified threshold. Available for MongoDB 9.0 or later. Raised if the amount of storage, in bytes, that query operations spilling to disk use meets the specified threshold. Available for MongoDB 9.0 or later. On Atlas Infinite clusters, queries spill to local storage on the compute node, not to the storage layer that holds your data. Atlas manages this local storage for you. Raised if the number of active collections and indexes meets the specified threshold. Raised if the number of currently active transactions meets the specified threshold. Raised if the number of currently inactive transactions meets the specified threshold. Raised if the number of currently open transactions meets the specified threshold. Raised if the number of aborted transactions meets the specified threshold. Raised if the number of committed transactions meets the specified threshold. Raised if the number of started transactions meets the specified threshold. ### Namespaces The following alert condition applies to the total number of namespaces across all non-system databases in a MongoDB process. You can view how many namespaces are in use for a MongoDB process by viewing the the Catalog [cluster metric.](https://www.mongodb.com/docs/atlas/review-available-metrics.md#std-label-review-available-metrics) Raised if the total number of collections and indexes across all non-system databases meets the specified threshold. Monitor this metric to avoid exceeding namespace limits, which can impact database performance and operations. For guidance on managing collections and indexes, see the [Data Modeling Introduction](https://www.mongodb.com/docs/manual/core/data-modeling-introduction/) and [Reduce the Number of Collections.](https://www.mongodb.com/docs/manual/data-modeling/design-antipatterns/reduce-collections/) ### WiredTiger Storage Engine The following alert conditions apply to the MongoDB process's [WiredTiger](https://www.mongodb.com/docs/manual/core/wiredtiger/) storage engine, as collected from the MongoDB `serverStatus` command's [`wiredTiger.cache`](https://www.mongodb.com/docs/manual/reference/command/serverStatus.md#mongodb-serverstatus-serverstatus.wiredTiger.cache) and [`queues.execution`](https://www.mongodb.com/docs/manual/reference/command/serverStatus.md#mongodb-serverstatus-serverstatus.queues.execution) documents. *Applicable for Atlas Core Only* You can view these metrics on the following charts, accessed through [cluster monitoring:](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics) - Cache Activity - Cache Usage - Tickets Available - Cache Fill Ratio The following are the alert conditions that apply to WiredTiger: Raised when the number of bytes read into the WiredTiger cache meets the specified threshold. Raised when the number of bytes written from the WiredTiger cache meets the specified threshold. Raised when the number of dirty bytes in the WiredTiger cache meets the specified threshold. Raised when the number of used bytes in the WiredTiger cache meets the specified threshold. Raised if the percentage of bytes in the cache relative to the total cache size meets the specified threshold. Raised if the percentage of dirty bytes relative to the total cache size meets the specified threshold. Raised if the number of read tickets available to the WiredTiger storage engine meet the specified threshold. Raised if the number of write tickets available to the WiredTiger storage engine meet the specified threshold. For clusters running on MongoDB version 7.0 and later, don't use the number of tickets as a metric for overload alerts. Starting in MongoDB version 7.0, Atlas dynamically adjusts the number of tickets. Instead, use the number of queued readers and writers as an overload metric. ### System and Disk Alerts The following alert conditions measure usage on your Atlas server clusters: **Note:** Currently, Atlas uses a single partition for data, index, and journal files. Even though the alerts reference individual partitions, they point to the same metric. **Atlas Core only**: The disk alert conditions in this section measure node-level disk performance and are not available for Atlas Infinite. Atlas Infinite uses a decoupled storage architecture with different metrics and alerts. For the metrics available for Atlas Infinite, see [Atlas Infinite Metrics.](https://www.mongodb.com/docs/atlas/review-available-metrics.md#std-label-atlas-infinite-metrics) **Note:** All hardware metrics have burst reporting equivalents with distinct configurable alerts. To learn more, see [Burst Reporting.](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-burst-metrics) Raised if the average length of the queue of requests issued to the data partition that MongoDB uses exceeds the specified threshold. Raised if the average number of disk read operations per second exceeds the specified threshold. Raised if the amount of latency on disk read operations exceeds the specified threshold. The percentage of disk space used on any partition that contains the MongoDB collection's data. To find possible solutions for this alert, see [Alert Resolutions.](https://www.mongodb.com/docs/atlas/reference/alert-resolutions/disk-space-used.md#std-label-disk-space-used) Raised if the average number of disk write operations per second exceeds the specified threshold. Raised if the amount of latency on disk write operations exceeds the specified threshold. Raised if the maximum average length of the queue of requests issued to the data partition that MongoDB uses exceeds the specified threshold. Raised if the maximum average number of disk read operations per second exceeds the specified threshold. Raised if the maximum amount of latency on disk read operations exceeds the specified threshold. Raised if the maximum percentage of disk space used on any partition that contains the MongoDB collection's data exceeds the specified threshold. Raised if the maximum average number of disk write operations per second exceeds the specified threshold. Raised if the maximum amount of latency on disk write operations exceeds the specified threshold. Raised if the maximum number of bytes sent *to* MongoDB meets the specified threshold. Raised if the maximum number of bytes sent *from* MongoDB meets the specified threshold. *Applicable when the EC2 cluster credit balance is exhausted.* The percentage by which the CPU usage exceeds the guaranteed baseline CPU credit accumulation rate. CPU credits are units of CPU utilization that you accumulate. The credits accumulate at a constant rate to provide a guaranteed level of performance. These credits can be used for additional CPU performance. When the credit balance is exhausted, only the guaranteed baseline of CPU performance is provided, and the amount of excess is shown as steal percent. **Note:** Atlas triggers this alert only for AWS EC2 clusters that support [AWS burstable instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-performance-instances.html). Currently, these are `M10` and `M20` cluster types. To learn how burstable performance affects auto-scaling thresholds, see [How Atlas Scales Cluster Tier.](https://www.mongodb.com/docs/atlas/cluster-autoscaling-compute-core.md#std-label-howitworks-scale-cluster-tier) The CPU usage of the processes on the node, normalized by the number of CPUs. This value is scaled to a range of 0-100%. Raised if the maximum percentage by which the CPU usage exceeds the guaranteed baseline CPU credit accumulation rate exceeds the specified threshold. Raised if the maximum CPU usage of the processes on the node, normalized by the number of CPUs, exceeds the specified threshold. Raised if the average rate of physical bytes received per second by the `eth0` network interface reaches the specified threshold. Raised if the average rate of physical bytes transmitted per second by the `eth0` network interface reaches the specified threshold. ### Restarts Raised if the number of times a host restarts within the previous hour exceeds the specified threshold. ### Host Down Raised if Atlas is unable to reach a host for several minutes. **Important:** You should only configure this alert if you depend on secondary reads. For more information on secondary reads, see [Query using Pre-Defined Replica Set Tags](https://www.mongodb.com/docs/atlas/reference/replica-set-tags.md#std-label-replica-set-tags) and [Read Preference.](https://www.mongodb.com/docs/manual/core/read-preference.md#std-label-replica-set-read-preference) This alert is generally triggered by one of the following conditions: - The cluster has experienced a failure and is being auto-healed. - The cluster could not be reached because of a network issue. MongoDB Atlas checks that the downtime did not occur because of your actions, such as [rolling index builds](https://www.mongodb.com/docs/manual/tutorial/build-indexes-on-replica-sets/). If MongoDB Atlas confirms that the downtime was not intentional, MongoDB Atlas attempts to replace the affected node. If failures occur, Atlas clusters maintain node availability for both reads and writes as long as a majority of nodes are running. To learn more, see [How does MongoDB Atlas deliver high availability?.](https://www.mongodb.com/docs/atlas/reference/faq/deployment.md#std-label-high-availability) ### Push-Based Log Export (PBLE) The following alert conditions apply to the [Push-Based Log Export feature:](https://www.mongodb.com/docs/atlas/push-logs.md#std-label-mongodb-logs-push) Raised if the log exporter is unable to send logs for an extended period. Raised if the log exporter drops a log line. This might indicate a very large log line that couldn't be sent. ### Log Export The following alert conditions apply to [log export:](https://www.mongodb.com/docs/atlas/export-logs.md#std-label-export-logs) Triggered immediately when log export encounters a non-retryable error, such as invalid credentials or a misconfigured sink. Triggered after retries are exhausted. Logs are queued in a Dead Letter Queue (DLQ) with 7-day retention and are automatically sent once connectivity is restored. Triggered when automatic replay from the DLQ fails after an automatic retry attempt. Undelivered records will be permanently deleted after 7 days. Contact MongoDB Support to request manual redelivery. ### Swap The following alert conditions apply to swap space usage: Raised if the amount of available swap space drops below the specified threshold. Raised if the maximum amount of available swap space drops below the specified threshold. Raised if the maximum total amount of swap space in use reaches the specified threshold. Raised if the total amount of swap space in use reaches the specified threshold. ### Sort The following alert conditions apply to sort operations: Raised if the number of writes to disk caused by [`$sort`](https://www.mongodb.com/docs/manual/reference/operator/aggregation/sort.md#mongodb-pipeline-pipe.-sort) stages meets the specified threshold. ### Inapplicable Host Conditions The following host conditions do not apply to Atlas. Atlas will not generate alerts for the following conditions: - Accesses Not In Memory: Total is - Background Flush Average is - B-tree: accesses is - B-tree: hits is - B-tree: misses is - B-tree: miss ratio is - Cursors: Client Cursors Size is - Effective Lock % is - Journaling Commits in Write Lock is - Journaling MB is - Journaling Write Data Files MB is - Memory: Mapped is - Page Fault Exceptions Thrown: Total is ## Query Targeting Alerts The following alerts apply to indexes on your collections. Either alert might indicate a missing or inefficient index. **See also:** To learn more about indexing to improve performance, see [Indexing Strategies.](https://www.mongodb.com/docs/manual/applications/indexes/) Raised if the ratio of index keys scanned to documents returned meets or exceeds the specified threshold. Raised if the ratio of documents scanned to documents returned meets or exceeds the specified threshold. The [change streams](https://www.mongodb.com/docs/manual/changeStreams/) cursors that the MongoDB Search process (`mongot`) uses to keep MongoDB Search indexes updated can contribute to the query targeting ratio and trigger [query targeting alerts](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-query-targeting-alerts) if the ratio is high. ## Cloud Backup Alerts The following alerts apply to Cloud Backup snapshots. Raised when a restore fails. Raised when a restore succeeds. Raised when a fallback snapshot fails. Raised when a regular backup fails, but Atlas was able to take a fallback snapshot. **See also:** [Fallback Snapshots.](https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore-from-snapshot.md#std-label-cps-fallback-snapshots) Raised when too much time has passed since the last successful snapshot. Raised when a download request fails. Raised when a snapshot hasn't been taken over configured period. Raised when a snapshot was taken successfully. ## Replica Set Alerts The following alert conditions apply to [replica sets:](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-replica-set) Raised when the number of elections that have occurred in the last hour exceeds the user-specified value of `X`. The value of `X` is set when you create the alert. This alert might indicate that the cluster's replication is not in a healthy state, as evidenced by constant elections. Raised when a replica set elects a new [primary.](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-primary) Raised when a replica set does not have a [primary](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-primary). Specifically, when none of the members of a replica set have a status of `PRIMARY`, the alert triggers. For example, this condition might arise when a set has an even number of voting members resulting in a tie. If Atlas collects data during an [election](https://www.mongodb.com/docs/manual/core/replica-set-elections.md#std-label-replica-set-elections), this alert might send a false positive. To prevent such false positives, set the alert configuration's after waiting interval (in the configuration's Send to section). To find possible solutions for this alert, see [Alert Resolutions.](https://www.mongodb.com/docs/atlas/reference/alert-resolutions/no-primary.md#std-label-no-primary) ## Sharded Cluster Alerts The following alert condition applies to [sharded clusters:](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-sharded-cluster) Raised if Atlas cannot reach any [`mongos`](https://www.mongodb.com/docs/manual/reference/program/mongos.md#mongodb-binary-bin.mongos) for the cluster. ## Flex Alerts The following alert conditions apply to Flex clusters: - [`Connections is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Connections-is) - [`Connections % of configured limit is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Connections---of-configured-limit-is) - [`DB Data Size is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-DB-Data-Size-is) - [`Network: Bytes In is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Network--Bytes-In-is) - [`Network: Bytes Out is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Network--Bytes-Out-is) - [`Network: Num Requests is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Network--Num-Requests-is) - [`Opcounter: Cmd is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Opcounter--Cmd-is) - [`Opcounter: Delete is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Opcounter--Delete-is) - [`Opcounter: Getmores is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Opcounter--Getmores-is) - [`Opcounter: Insert is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Opcounter--Insert-is) - [`Opcounter: Query is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Opcounter--Query-is) - [`Opcounter: Total is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Opcounter--Total-is) - [`Opcounter: Update is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Opcounter--Update-is) Raised if any of the following conditions apply: - The number of open connections to the host exceeds 80% of the total open connections allowed. - The approximate size of all documents (and their paddings) and the index exceeds 4 gigabytes. - The total operations per second exceeds 200 for 24 hours and realerts every 6 hours. ## App Services Alerts The following alert conditions apply to [Atlas App Services.](https://www.mongodb.com/docs/atlas/app-services/) Raised when the number of concurrent requests exceeds the limit. This alert indicates that an app might be making an unexpectedly high number of requests. Raised if the number of failed client login requests per second meets the specified threshold. Raised if the HTTPS endpoints [compute time](https://www.mongodb.com/docs/atlas/app-services/billing/#app-services-compute) per second meets the specified threshold. Raised if the HTTPS endpoints [data egress](https://www.mongodb.com/docs/atlas/app-services/billing/#data-transfer) bytes per second meets the specified threshold. Raised if the number of HTTPS endpoints requests that fail per second meets the specified threshold. Raised if the number of GraphQL requests that fail per second meets the specified threshold. (GraphQL support for Atlas App Services is deprecated. To learn more, see the [Atlas App Services documentation](https://www.mongodb.com/docs/atlas/app-services/migrate-hosting-graphql/).) Raised if the number of total requests that fail per second meets the specified threshold. Raised if the number of SDK Function requests that fail per second meets the specified threshold. Raised if the number of failed [Atlas Device Sync](https://www.mongodb.com/docs/atlas/app-services/sync/learn/overview/) requests per second meets the specified threshold. Raised if the number of Triggers requests that fail per second meets the specified threshold. Raised if the GraphQL [compute time](https://www.mongodb.com/docs/atlas/app-services/billing/#app-services-compute) per second meets the specified threshold. (GraphQL support for Atlas App Services is deprecated. To learn more, see the [Atlas App Services documentation](https://www.mongodb.com/docs/atlas/app-services/migrate-hosting-graphql/).) Raised if the GraphQL [data egress](https://www.mongodb.com/docs/atlas/app-services/billing/#data-transfer) bytes per second meets the specified threshold. (GraphQL support for Atlas App Services is deprecated. To learn more, see the [Atlas App Services documentation](https://www.mongodb.com/docs/atlas/app-services/migrate-hosting-graphql/).) Raised if the 95th percentile of duration in milliseconds for GraphQL requests meets the specified threshold. (GraphQL support for Atlas App Services is deprecated. To learn more, see the [Atlas App Services documentation](https://www.mongodb.com/docs/atlas/app-services/migrate-hosting-graphql/).) Raised if the 95th percentile of duration in milliseconds for HTTPS endpoint requests meets the specified threshold. Raised if the 95th percentile of duration in milliseconds for MQL requests meets the specified threshold. Raised if the overall [compute time](https://www.mongodb.com/docs/atlas/app-services/billing/#app-services-compute) per second meets the specified threshold. Raised if the overall [data egress](https://www.mongodb.com/docs/atlas/app-services/billing/#data-transfer) bytes per second meets the specified threshold. Raised if the SDK Functions [compute time](https://www.mongodb.com/docs/atlas/app-services/billing/#app-services-compute) per second meets the specified threshold. Raised if the SDK Functions [data egress](https://www.mongodb.com/docs/atlas/app-services/billing/#data-transfer) bytes per second meets the specified threshold. Raised if the 95th percentile of duration in milliseconds for SDK function requests meets the specified threshold. Raised if the SDK MQL [compute time](https://www.mongodb.com/docs/atlas/app-services/billing/#app-services-compute) per second meets the specified threshold. Raised if the SDK MQL [data egress](https://www.mongodb.com/docs/atlas/app-services/billing/#data-transfer) bytes per second meets the specified threshold. Raised if the number of sessions ended per second during [Atlas Device Sync](https://www.mongodb.com/docs/atlas/app-services/sync/learn/overview/) meets the specified threshold. Raised if the 95th percentile of the bootstrap time for the [Atlas Device Sync](https://www.mongodb.com/docs/atlas/app-services/sync/learn/overview/) client meets the specified threshold. Raised if the number of uploads that failed per second on the [Atlas Device Sync](https://www.mongodb.com/docs/atlas/app-services/sync/learn/overview/) client meets the specified threshold. Raised if the number of invalid uploads per second on the [Atlas Device Sync](https://www.mongodb.com/docs/atlas/app-services/sync/learn/overview/) client meets the specified threshold. Raised if the approximate amount of time that the [Atlas Device Sync](https://www.mongodb.com/docs/atlas/app-services/sync/learn/overview/) is behind the MongoDB [oplog](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-oplog) meets the specified threshold. Raised if the [Atlas Device Sync](https://www.mongodb.com/docs/atlas/app-services/sync/learn/overview/) [data egress](https://www.mongodb.com/docs/atlas/app-services/billing/#data-transfer) bytes per second meets the specified threshold. Raised is the number of App Services [unsyncable documents](https://www.mongodb.com/docs/atlas/app-services/mongodb/internal-database-usage/#std-label-unsynced-documents) meets the specified threshold. Raised if the triggers [compute time](https://www.mongodb.com/docs/atlas/app-services/billing/#app-services-compute) per second has meets the specified threshold. Raised if the approximate amount of time that the App Services triggers is behind the MongoDB [oplog](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-oplog) meets the specified threshold. Raised if the triggers [data egress](https://www.mongodb.com/docs/atlas/app-services/billing/#data-transfer) bytes per second meets the specified threshold. Raised if the 95th percentile of duration in milliseconds for triggers meets the specified threshold. ## User Alerts The following alert conditions apply to Atlas users. Raised when one or more users in an organization do not have [multi-factor authentication](https://www.mongodb.com/docs/atlas/security-multi-factor-authentication.md#std-label-atlas-enable-mfa) enabled. Raised when an Atlas user's project or organization roles have changed. Raised when a new user joins the Atlas organization. Raised when a new user joins the Atlas project. Raised when a user leaves the Atlas organization. Raised when a user leaves the Atlas project. ## Project Alerts The following alert conditions apply to your Atlas project. Raised if the project's or organization's security checkup alerts are updated. Raised if you or your team have added or changed project's [tags.](https://www.mongodb.com/docs/atlas/tags.md#std-label-configure-resource-tags) Raised if the project or organization has users who have not set up multi-factor authentication. ## Billing Alerts The following alert conditions apply to Atlas billing. You can configure billing alerts from the Atlas UI at the organization level or the project level. To configure organization-level alerts: 1. In Atlas, go to the Organization Alerts page. If it's not already displayed, select your desired organization from the Organizations menu menu in the navigation bar. In the top-right corner of the Atlas UI, click the Alerts icon. Click Alerts under the Organization header. The [Organization Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%23%2Forg%2F%3Corganization%3E%2Falerts%2Flist) page displays. 2. Configure the alerts. To configure project-level alerts: 1. In Atlas, go to the Project Alerts page. If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar. If it's not already displayed, select your desired project from the Projects menu in the navigation bar. In the top-right corner of the Atlas UI, click the Alerts icon. Click Alerts under the Project header. The [Project Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Falerts%2FopenAlerts) page displays. 2. Configure the alerts. **Note:** All amounts billed are in USD (United States Dollars). Raised if the organization or project's last daily amount billed exceeds your configured threshold. Atlas does not account for any credits applied for the previous day when calculating the billed amount. This condition applies to both organizations and projects. Raised if the credit card on file is about to expire. The alert is triggered at the beginning of the month that the card expires. Atlas enables this alert when a credit card is added for the first time. This condition applies to both organizations and projects. Raised if the monthly total for any project within the organization exceeds your configured threshold for all projects. When the current pending invoice closes, this alert resets. This alert condition applies to organizations only. Raised if the monthly total for the organization exceeds your configured threshold. When the current pending invoice closes, this alert resets. This alert condition applies to organizations only. Raised if the organization's daily gross spend has increased by more than your configured threshold percentage compared to the previous day. This alert condition applies to organizations only. Configure it from the Organization Alerts page. Raised if the organization's weekly gross spend has increased by more than your configured threshold percentage compared to the previous 7 days. This alert condition applies to organizations only. Configure it from the Organization Alerts page. Raised if the organization's monthly gross spend has increased by more than your configured threshold percentage compared to the previous 30 days. This alert condition applies to organizations only. Configure it from the Organization Alerts page. Raised if the project's daily billing has increased by more than your configured threshold percentage. This alert condition applies to projects only. Configure it from the Project Alerts page. Raised if the project's weekly billing has increased by more than your configured threshold percentage. This alert condition applies to projects only. Configure it from the Project Alerts page. Raised if the project's monthly billing has increased by more than your configured threshold percentage. This alert condition applies to projects only. Configure it from the Project Alerts page. ## Service Account Alerts The following alert conditions apply to Atlas [service accounts](https://www.mongodb.com/docs/atlas/api/api-authentication.md#std-label-service-accounts-overview). You can [configure these alerts](https://www.mongodb.com/docs/atlas/configure-alerts.md#std-label-configure-alerts) from the Atlas UI at the organization level. **Note: Service Accounts with the Organization Member Role** These alerts don't apply to service accounts that have only the [`Organization Member`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Organization-Member) role. Atlas evaluates these alert conditions only for service accounts that have an organization role with greater privileges than [`Organization Member`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Organization-Member). If you test these alerts with a service account that has only the [`Organization Member`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Organization-Member) role, Atlas doesn't raise them. Raised if a secret for any of your service accounts expires within seven days, or the number of days you specify if you [configure this alert](https://www.mongodb.com/docs/atlas/configure-alerts.md#std-label-configure-alert-settings). When all expiring secrets are removed or have expired, this alert resets. This alert condition applies to organizations only. Raised if a secret for any of your service accounts has expired. To generate a new secret, see [Update Programmatic Access to an Organization](https://www.mongodb.com/docs/atlas/configure-api-access-org.md#std-label-change-org-api-key-roles). When all expired secrets are removed, this alert resets. This alert condition applies to organizations only. ## Federation Alerts Raised when an IdP (Identity Provider) certificate associated with an organization for which you have the [`Organization Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Organization-Owner) role expires within 14 days. Atlas sends this alert daily until you acknowledge it. **Note:** Atlas creates this alert automatically when you [map an organization to an IdP provider](https://www.mongodb.com/docs/atlas/security/manage-org-mapping.md#std-label-atlas-map-org-idp). If you remove the mapping, Atlas deletes all instances of this alert. ## Encryption at Rest Alerts The following alert conditions apply to projects using [Encryption at Rest using Customer Key Management.](https://www.mongodb.com/docs/atlas/security-kms-encryption.md#std-label-security-kms-encryption) Raised if the AWS Customer Master Key (CMK) used by the Atlas project has been active for more than the configured number of days (90 by default). To modify the alert threshold: In Atlas, go to the Project Alerts page. If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar. If it's not already displayed, select your desired project from the Projects menu in the navigation bar. In the top-right corner of the Atlas UI, click the Alerts icon. Click Alerts under the Project header. The [Project Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Falerts%2FopenAlerts) page displays. Click the Alert Settings. If you [configure](https://www.mongodb.com/docs/atlas/configure-alerts.md#std-label-configure-alerts) the default 90 days [`alert`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-AWS-encryption-key-elapsed-time-since-last-rotation-is-above--n--days) to be greater than the AWS (Amazon Web Services) KMS (Key Management Service) CMK rotation, Atlas won't create the alert because AWS (Amazon Web Services) would have automatically rotated your CMK (customer-managed key). This alert resets automatically if you rotate the project CMK (Customer Master Key). For documentation on how to rotate your project CMK (customer master key), see [Rotate your AWS Customer Master Key.](https://www.mongodb.com/docs/atlas/security-aws-kms.md#std-label-security-aws-kms-rotate-key) Raised if the Azure Key Vault Key Identifier used by the Atlas project has been active for more than the configured number of days (90 by default). To modify the alert threshold: In Atlas, go to the Project Alerts page. If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar. If it's not already displayed, select your desired project from the Projects menu in the navigation bar. In the top-right corner of the Atlas UI, click the Alerts icon. Click Alerts under the Project header. The [Project Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Falerts%2FopenAlerts) page displays. Click the Alert Settings. This alert resets automatically if you rotate the project Key Identifier. For documentation on how to rotate your project Key Identifier, see [About Rotating Your Azure Key Identifier.](https://www.mongodb.com/docs/atlas/security-azure-kms.md#std-label-azure-kms-rotate-key) Raised if the GCP Key Version Resource ID used by the Atlas project has been active for more than the configured number of days (90 by default). To modify the alert threshold: In Atlas, go to the Project Alerts page. If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar. If it's not already displayed, select your desired project from the Projects menu in the navigation bar. In the top-right corner of the Atlas UI, click the Alerts icon. Click Alerts under the Project header. The [Project Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Falerts%2FopenAlerts) page displays. Click the Alert Settings. This alert resets automatically if you rotate the project Key Version Resource ID. To learn how to rotate your project Key Version Resource ID, see [Rotate your GCP Key Version Resource ID.](https://www.mongodb.com/docs/atlas/security-gcp-kms.md#std-label-gcp-kms-rotate-key) Raised if the KMS credentials for your cloud provider are invalid due to network access restrictions. This alert runs automatically for all new projects to communicate any KMS network access failures. To modify or remove the alert: In Atlas, go to the Project Alerts page. If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar. If it's not already displayed, select your desired project from the Projects menu in the navigation bar. In the top-right corner of the Atlas UI, click the Alerts icon. Click Alerts under the Project header. The [Project Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Falerts%2FopenAlerts) page displays. Click the Alert Settings. This alert is enabled by default for all new projects. Raised if the encryption at rest configuration for your project is no longer valid. This condition can occur when the: - KMS (Key Management Service) key is deleted, disabled, expired, or pending deletion. - IAM (Identity and Access Management) role or credentials are revoked or unable to assume the role. - Role exists but lacks encrypt or decrypt permissions. Review your KMS (Key Management Service) key and role or credentials and update them to restore a valid configuration. To learn more, see [Encryption at Rest using Customer Key Management.](https://www.mongodb.com/docs/atlas/security-kms-encryption.md#std-label-security-kms-encryption) ## Maintenance Window Alerts The following alert conditions apply to projects with [configured maintenance windows.](https://www.mongodb.com/docs/atlas/tutorial/manage-project-settings.md#std-label-atlas-modify-project-settings) **Note:** You can only [configure maintenance window alerts](https://www.mongodb.com/docs/atlas/configure-alerts.md#std-label-configure-mw-alert) if a project has an active maintenance window. Raised 72 hours prior to scheduled maintenance for a project. Raised if scheduled maintenance is no longer needed for a project. Raised when maintenance starts for a project. Raised if maintenance has been deferred. ## MongoDB Support Access Grant Alerts Raised when MongoDB support staff has infrastructural access. You can view the access grant type and the expiration date of the granted event. Raised when MongoDB support staff no longer has infrastructural access. You can view the access grant type. ## Atlas Stream Processing Alerts The following alert conditions apply to projects running Stream Processing Workspaces. Raised if a target stream processor exits with a failed state. **Note:** If you change the name of a stream processor for which you had [configured](https://www.mongodb.com/docs/atlas/configure-alerts.md#std-label-configure-alerts) the [Stream Processor State is failed](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-atlas-sp-alerts) alert by using an Operator (which contains matcher expressions like `is`, `contains`, and more), Atlas won't trigger alerts for the renamed stream processor if the matcher expression doesn't match the new name. To monitor the renamed stream processor, [reconfigure](https://www.mongodb.com/docs/atlas/configure-alerts.md#std-label-configure-alerts) the alert. Raised if the lag time between an event on a change stream [source](https://www.mongodb.com/docs/atlas/atlas-stream-processing/sp-agg-source.md#std-label-atlas-sp-agg-source) and the ingestion time of that event on a target stream processor is above or below the threshold. Raised if the rate of messages per second the target stream processor writes to the [Dead Letter Queue](https://www.mongodb.com/docs/atlas/atlas-stream-processing/architecture.md#std-label-atlas-sp-dlq) is above or below the threshold. Raised if the offset lag total on a Kafka [source](https://www.mongodb.com/docs/atlas/atlas-stream-processing/sp-agg-source.md#std-label-atlas-sp-agg-source) is above or below the threshold. Raised if the rate of messages per second the target stream outputs through its [$emit](https://www.mongodb.com/docs/atlas/atlas-stream-processing/sp-agg-emit.md#std-label-atlas-sp-agg-emit) or [$merge](https://www.mongodb.com/docs/atlas/atlas-stream-processing/sp-agg-merge.md#std-label-atlas-sp-agg-merge) stage is above or below the threshold.