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 or
config servers.

The following alert conditions measure the rate of asserts for a MongoDB
process, as collected from the MongoDB serverStatus command’s
asserts document. You can view asserts through cluster
monitoring.

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 document. You can view
opcounters through cluster monitoring.

The following alert conditions measure the rate of database operations on
MongoDB secondaries, as collected from the MongoDB
serverStatus command’s opcountersRepl document. You can
view these metrics on the Opcounters - Repl chart, accessed
through cluster monitoring.

The following alert conditions measure memory for a MongoDB process, as
collected from the MongoDB serverStatus command’s mem
document. You can view these metrics on the Atlas Memory and
Non-Mapped Virtual Memory charts, accessed through cluster
monitoring.

Sends an alert 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.

Sends an alert if the size of virtual memory for the mongod process meets the specified threshold. You can
use this alert to flag excessive memory outside of memory mapping. For more
information, click the Memory chart’s i icon.

Sends an alert 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. For more information on how to use this metric,
view the Non-Mapped Virtual Memory chart and click the chart’s
i icon.

The following alert condition measures connections to a MongoDB process, as
collected from the MongoDB serverStatus command’s
connections document. You can view this metric on the
Atlas Connections chart, accessed through cluster
monitoring.

The following alert conditions measure operations waiting on locks, as
collected from the MongoDB serverStatus command’s
globalLock document. You can view these metrics on the
Atlas Queues chart, accessed through cluster monitoring.

Sends an alert 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.

The following alert conditions measure the number of cursors for a MongoDB process, as collected from the MongoDB
serverStatus command’s metrics.cursor document. You can
view these metrics on the Atlas Cursors chart, accessed
through cluster monitoring.

The following alert conditions measure throughput for MongoDB process, as
collected from the MongoDB serverStatus command’s network
document. You can view these metrics on a host’s Network chart,
accessed through cluster monitoring.

Sends an alert if the approximate amount of time that the secondary
is behind the primary meets the specified threshold. Atlas calculates
replication lag using the approach described in Check the Replication
Lag in the MongoDB manual.

The following alert conditions apply to database storage, as collected
for a MongoDB process by the MongoDB
dbStats command. For details on
how Atlas handles reaching database storage limits, refer to the
FAQ page. These conditions are based on the
summed total of all databases on the MongoDB process:

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 instances that
support Burstable Performance.
Currently, these are M10 and M20 instance types.

The percentage of time during which requests are being issued to the
partition that contains the MongoDB journal, if journaling is enabled. This
includes requests from any process, not just MongoDB processes.

Sends an alert when a replica set does not have a primary.
Specifically, when none of the members of a
replica set have a status of PRIMARY, the alert triggers. For
example, this condition may arise when a set has an even number of
voting members resulting in a tie.

If Atlas collects data during an election for primary, 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).

Sends an alert 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 may indicate
that the cluster’s replication is not in a healthy state, as
evidenced by constant elections.

Sends an alert 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.

The organization or project’s pending monthly invoice exceeds your
configured threshold. When the current pending invoice closes, this
alert resets.

This alert resolves automatically if you pay enough to bring the
pending invoice below the threshold. It may take up to 24 hours for
the payment to clear. This alert can repeat if the pending invoice
exceeds the threshold again before the invoice closes.

AWS encryption key elapsed time since last rotation is above (n) days¶

Sends an alert if the AWS Customer Master Key (CMK) used by the
Atlas project has been active for more than the configured
number of days (365 by default). You can modify the alert
threshold from the Alert Settings tab of the
Alerts view.

Azure encryption key elapsed time since last rotation is above (n) days¶

Sends an alert if the Azure Key Vault Key Identifier used
by the Atlas project has been active for more than the configured
number of days (365 by default). You can modify the alert
threshold from the Alert Settings tab of the
Alerts view.