Navigation
This version of the documentation is archived and no longer supported. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.
This version of the manual is no longer supported.

Manage Global Alerts

Overview

A global alert applies the same alert configuration to multiple projects at once. When an alert condition occurs, Ops Manager sends notification only to the affected project. Ops Manager sends notification at regular intervals until the alert resolves or gets canceled.

If you acknowledge a global alert, Ops Manager sends no further notifications to the alert’s distribution list until the acknowledgement period has passed or until the alert resolves. If the alert condition ends during the acknowledgment period, Ops Manager sends a notification of the resolution.

To access global alerts you must have the Global Owner role or Global Monitoring Admin role.

Default Global Alerts

When Ops Manager starts, it creates default global alert configurations. If you delete a default global alert configuration, Ops Manager recreates it when the application restarts.

If you don’t want to receive alerts from a default global alert configuration, you must disable that global alert configuration.

View Global Alerts

1
2

Select the Alerts tab and then select Open Alerts under Global Alerts.

3

Select one or more filters above the list and click Filter.

To filter by: Do this:
Acknowledgement Select the appropriate option in the All States drop-down list.
Project Type the project’s name in the Projects box.
Project Tags

Type the tag’s name in the Tags box.

Users with the Global Owner role can assign tags to projects.

Alert type (open alerts only) Type the alert type in the Types box. The box autocompletes an alert type only if there is an open alert of that type.
Date Select the dates in the From and To fields.
4

Acknowledge or unacknowledge an alert.

To acknowlege an alert, click Acknowledge on the line for the alert, select the time period for the acknowledgement, and click Acknowledge. Ops Manager sends no further notifications for the selected period.

To “undo” an acknowledgment and again receive notifications if the alert condition still applies, click Unacknowledge on the line for the alert and click Confirm.

Configure a Global Alert

1
2

Select the Alerts tab, then the Global Alert Settings page.

3

Click the Add Alert button.

Ops Manager displays the alert configuration options.

4

Select the projects to which to apply the alert.

If you specify tags, the alert only applies to the projects that have those tags. Users with the Global Owner role can assign tags to projects.

You can type the first few letters of a tag or project to locate it in the drop-down list.

5

Select the condition that triggers the alert.

In the Alert if section, select the target component and the condition. For explanations of alert conditions, see Alert Conditions.

6

Apply the alert only to specific targets. (Optional)

If the options in the For section display, you can filter the alert to apply to a subset of the targets.

The matches field supports regular expressions. Regular expressions must match against an entire hostname.

Example

To find hostnames involving foo using a regular expression, you can filter for a hostname using one the following options:

Hostname Description matches Query
Starts with foo foo.*
Ends with foo .*foo
Contains foo .*foo.*
7

Select the alert recipients and delivery methods.

In the Send to section, click Add to add notifications or recipients. To help eliminate false positives, set the time to elapse before the condition triggers the alert.

To test HipChat, Slack, FlowDock, or PagerDuty integration, click the test link that appears after you configure the notification.

Which alert notification methods can be set depend on the scope of the alert:

Project alerts
Apply to one or more individual Organizations and Projects only.
Global alerts
Apply to all Organizations and Projects.
System alerts
Apply to the health of Ops Manager and its backing databases.

The alert notifications methods are as follows:

Notification Method Project Global System Description
Ops Manager Project check icon check icon  

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

  1. Select the Project roles that should receive the alerts from the Select Role(s) check boxes or select All Roles for all users in the Project to receive the alert.
  2. Select SMS to send these alerts to the mobile number configured for each Ops Manager Project user in their Account page.
  3. Select Email to send these alerts to the email address configured for each Ops Manager Project user in their Account page. Email is checked by default.
Ops Manager Organization check icon check icon  

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

  1. Select the Organization roles that should 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 check icon    

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

  1. Select SMS to send these alerts to the mobile number configured for the Ops Manager user in their Account page.
  2. Select Email to send these alerts to the email address configured for the Ops Manager user in their Account page. Email is checked by default.
Ops Manager Team check icon    

Sends the alert by email or text message to a specified Ops Manager team.

Note

This option appears only after at least one team has been created.

  1. Select SMS to send these alerts to the mobile number configured for each Ops Manager Team user in their Account page.
  2. Select Email to send these alerts to the email address configured for each Ops Manager Team user in their Account page. Email is checked by default.
SNMP Host check icon check icon check icon Specify the hostname that will receive the v2c trap on standard port 162. The MIB file for SNMP is available for download.
Email check icon check icon check icon Sends the alert to a specified email address.
SMS check icon check icon check icon

Sends the alert to a specified mobile number.

Available only if Ops Manager is configured for Twilio integration.

HipChat check icon check icon check icon Sends the alert to a HipChat room message stream. Enter the HipChat room name and API token.
Slack check icon check icon check icon Sends the alert to a Slack channel. 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. For information on Bot users in Slack, see Bot Users.
FlowDock check icon check icon check icon

Sends the alert to a Flowdock account. Enter the following:

  • Organization Name: The Flowdock organization name in lowercase letters. This is the name that appears after www.flowdock.com/app/ in the URL string.
  • Flow Name: The flow name in lowercase letters. The flow name appears after the organization name in the URL www.flowdock.com/app/orgname/flowname.
  • User API Token: Your Flowdock “personal API token” found on the Tokens page of your Flowdock account.
PagerDuty check icon check icon check icon

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

This option is available only for alerts that require acknowledgement. Informational alerts, such as the alert that a replica set has elected a new primary, cannot use this notification method.

Users can acknowledge PagerDuty alerts only from the PagerDuty dashboard.

Webhook check icon check icon  

Sends an HTTP POST request to an endpoint for programmatic processing. The request body contains a JSON document that uses the same format as the Ops Manager API Alerts resource.

To use this method:

  • At the Project level, configure the Webhook settings for your Project
  • At the Global level, configure the Webhook settings on the Administration Alerts tab for Global alerts.

Ops Manager adds a request header called X-MMS-Event to distinguish between various alert states. The possible values for this header are:

alert.open The alert was just opened.
alert.close The alert was resolved.
alert.update A previously opened alert is still open.
alert.acknowledge The alert was acknowledged.
alert.cancel The alert became invalid and was canceled.
alert.inform Represents an informational alert, which is a point-in-time event, such as “Primary Elected.”

If you specify a key in the Webhook Secret field, MongoDB Atlas adds the X-MMS-Signature request header. This header contains the base64-encoded HMAC-SHA-1 signature of the request body. MongoDB Atlas creates the signature using the provided secret.

Datadog check icon check icon check icon

Sends the alert to a DataDog account. Enter the following:

Administrators   check icon check icon Sends the alert to the email address specified in the Admin Email Address field in the Ops Manager configuration options.
Global Alerts Summary Email   check icon   Sends a summary email of all global alerts to the specified email address.
8

Click Save.

Disable or Enable a Global Alert Configuration

1

Click the Admin link in the top right corner of Ops Manager.

Ops Manager displays the Admin link only if you have administrative privileges.

2

Click the Alerts tab, then click Global Alert Settings page.

3

Choose the alert setting to disable.

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

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

Default Global Alerts

Each time Ops Manager starts, it creates global alert configurations for the following conditions:

  • Blockstore jobs have reached a high number of retries
  • Sync slice transfer has not progressed in more than 60 minutes
  • Inconsistent cluster snapshot count is above 5
  • Backup is down
  • Backup has too many conf call failures
  • No daemon is available to take a queryable restore job
  • Inconsistent backup configuration has been detected
  • Backup requires a resync
  • Replica set has a late snapshot
  • Backup is in an unexpected state
  • Backup has reached a high number of retries
  • Backup could not be assigned to a backup daemon

If you do not want to receive alerts from a default global alert configuration, you must disable that global alert configuration.