For AI agents: a documentation index is available at https://www.mongodb.com/docs/llms.txt — markdown versions of all pages are available by appending .md to any URL path.
Docs Menu

Configure Alert Settings in Ops Manager

An alert configuration defines the conditions that trigger an alert and the alert's notification methods. This tutorial describes how to create and manage the alert configurations for a specified project. To create and manage global alert configurations, see Manage Global Alerts.

Many factors may affect alert delivery, including do not call lists, caps for messages sent or delivered, delivery time of day, and message caching.

Check with your telephone service contract for the costs associated with receiving text messages.

If you choose SMS, Ops Manager sends alert text messages to all users in the project who have a mobile number associated with their user account.

You can create multiple alert configurations with different frequencies. The minimum frequency for an alert is 5 minutes.

The time between re-notifications increases by the frequency amount every alert cycle up to a maximum of 24 hours. For example, if the frequency amount is 5 minutes, and the alert condition is first triggered at 9am, subsequent alerts occur at 9:05am, 9:15am, 9:30am, and so on.

You can set the time to elapse before Ops Manager sends an alert after an alert condition occurs. This helps eliminate false positives.

Ops Manager provides no default alerts for organizations.

To effectively monitor your deployment, consider configuring the following alerts:

  • Host is recovering: Triggers when a MongoDB instance enters RECOVERING mode.

  • Replication Lag is: Monitors the lag time of secondaries behind the primary.

  • Tickets Available: Writes/Reads: Flags potential performance issues for the WiredTiger storage engine.

  • Replication Oplog: Monitors the oplog window size.

  • Host is down: Triggers when a host becomes unreachable.

  • Queues: Readers/Writers is: Tracks operations waiting on locks.

  • Page faults is: Investigate if consistently high (> 1000 avg/sec).

  • Host is exposed to the public Internet: Triggers when authentication and firewall protection are missing.

  • Host does not have the latest version: Triggers when the MongoDB version is outdated by two or more revisions.

  • Replica set elected a new primary: Triggers during an election event.

  • Number of unhealthy members > n: Triggers when more than n members are unhealthy.

  • Cluster missing an active mongos
  • Monitoring Agent is down

  • Backup Agent is down

When you use the Backup component, configure the following alerts:

  • Backup oplog is behind

  • Backup requires a resync

Note

Tune these alerts for your specific workload and usage patterns.

You can configure default settings for the following notification options:

  • Ops Manager Organization

  • Ops Manager User

  • Email

  • SMS

  • HipChat

  • Slack

  • PagerDuty

  • Datadog

  • VictorOps

  • Opsgenie

To configure default settings for one of the above notification options, click Integrations under Projects in the sidebar. Locate the notification option and enter the default values.

Ops Manager fills in the default values automatically when a user selects that option when creating an alert configuration. If the key, token, or URL that is used to send the notification becomes invalid, Ops Manager sends an email to the project owner and eventually removes the key, token, or URL.

When you create a new alert, you can clone an existing alert.

1
  1. If it is not already displayed, select your desired organization from the Organizations menu in the navigation bar.

  2. Click Alerts in the sidebar.

2

To create a new alert:

  1. Click Add Alert.

To clone an existing alert setting:

  1. Click the Alert Settings tab.

  2. Locate the alert setting you want to clone.

  3. Click then Clone in that alert setting's row.

3

Click User or Billing under Select a Target.

4
5

Under the Add Notification Method heading, click the button for the particular notification method you want to use.

Notification Option
User Alerts
Billing Alerts
Description

Ops Manager Organization

Sends the alert by email or text message to users with specific roles in the Organization.

  1. Select the Organization roles that receive the alerts from the Select Role(s) check boxes or select All Roles for all users in the Organization to receive the alert.

  2. Select SMS to send these alerts to the mobile number configured for each Ops Manager Organization user in their Account page.

  3. Select Email to send these alerts to the email address configured for each Ops Manager Organization user in their Account page. Email is checked by default.

Ops Manager User

Sends the alert to a Ops Manager user, either by email or text message.

  • Select SMS to send these alerts to the mobile number configured for the Ops Manager user's account.

  • Select Email to send these alerts to the email address configured for the Ops Manager user's account. Email is checked by default.

Email

Sends the alert to any email address you provide.

Mobile Number

Sends the alert to a phone number. Ops Manager removes all letters and punctuation except the +.

For international (non-U.S.) phone numbers, format phone numbers using the E.164 standard. For example, for New Zealand, enter +64 before the phone number.

Ops Manager uses the U.S.-based Twilio to send text messages.

If you want to use a non-U.S. phone number, try using a Google Voice phone number.

Configure Ops Manager for Twilio integration to use SMS.

Slack

Sends the alert to a Slack channel in the authorized Slack workplace for the organization.

  • Enter the channel name and either an API token or a Bot token.

  • To create an API token, see the API page in your Slack account.

To learn more about Bot users in Slack, see the Slack documentation.

PagerDuty

Sends the alert to a PagerDuty account. Enter only the PagerDuty integration key. Define escalation rules and alert assignments directly in PagerDuty.

Acknowledge PagerDuty alerts from the PagerDuty dashboard.

All new PagerDuty keys use their Events API v2. If you have an Events API v1 key, you can continue to use that key with Ops Manager.

Datadog

Sends the alert to a Datadog account as a Datadog event.

When the alert first opens, Ops Manager sends the alert as an "error" event. Subsequent updates are sent as "info" events. When the alert closes, Ops Manager sends a "success" event.

If prompted, enter your Datadog API key under API Key and click Validate Datadog API Key.

Find your Datadog API Key in your Datadog account.

VictorOps

Sends the alert to a Splunk On-Call (formerly VictorOps) account.

This option displays for alerts that require acknowledgement. You can use this notification method on information alerts. These alerts include ones like User joined the organization.

Acknowledge VictorOps alerts from the VictorOps dashboard.

Opsgenie

Sends the alert to an Opsgenie account.

  • Enter the OpsGenie Alert API key in Ops Manager.

  • Define escalation rules and alert assignments in Opsgenie.

This option displays for alerts that require acknowledgement. You can use this notification method on information alerts. These alerts include ones like User joined the organization.

Acknowledge Opsgenie alerts from the Opsgenie dashboard.

6
1
  1. If it is not already displayed, select your desired organization from the Organizations menu in the navigation bar.

  2. Click Alerts in the sidebar.

  1. Click the Alert Settings tab.
2
  1. On the row for a specific alert, click then Delete.

  2. Click Delete in the Delete Alert modal or click Cancel to leave the alert as configured.

    Note

    If you have not logged in within the five minutes of pushing Delete, you need to re-enter your password, then click Delete again.

If you delete an alert setting, Ops Manager cancels active alerts related to the setting. A deleted alert setting does not remain visible.

1
  1. If it is not already displayed, select your desired organization from the Organizations menu in the navigation bar.

  2. Click Alerts in the sidebar.

  1. Click the Alert Settings tab.
2

On the row for a specific alert, click then Disable.

Click then Enable to re-enable the alert at any time.

If you disable an alert setting, Ops Manager cancels active alerts related to the setting. A disabled alert setting remains visible but unavailable and can be later re-enabled.

If you need to disable an alert only for a period of time, you can suspend alerts.

You can view all alerts, alert settings, and deleted alerts on the Organization Alerts page. To learn more, see Alerts Workflow.

1
  1. If it is not already displayed, select your desired organization from the Organizations menu in the navigation bar.

  2. Click Alerts in the sidebar.

  1. Click the Alert Settings tab.
2

Ops Manager displays the history of changes to the alert configuration.

You can test your alert configurations to ensure they work correctly before deploying them in production. This applies especially to webhook notifications with custom templates. Not all notification methods provide a way to test the configuration.

1

Navigate to Alerts > Alert Settings.

2

Create or edit an alert configuration.

3

In the Send to section, configure your notification method (webhook, email, etc.).

4

If the notification method supports it, click the test link next to the notification configuration.

5

Ops Manager sends a test notification with sample data to verify your configuration works correctly.

For webhook notifications, the test includes:

  • Sample alert data rendered through your custom templates

  • Validation that your webhook endpoint is reachable

  • Verification that custom headers and body templates render correctly