Manage Global Alerts
On this page
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 you resolve or cancel the alert.
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.
Note
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
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 |
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. |
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
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.
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 Review Alert Conditions.
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.* |
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, 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 | Sends the alert by email or text message to users with specific roles in the Project.
| |||||||||||||||
Ops Manager Organization | Sends the alert by email or text message to users with specific roles in the Organization.
| |||||||||||||||
Ops Manager User | Sends the alert to a Ops Manager user, either by email or text message.
| |||||||||||||||
Ops Manager Team | Sends the alert to a Ops Manager user, either by email or text message.
| |||||||||||||||
SNMP Host | Specify the hostname that will receive the v2c trap on
standard port ImportantOps Manager 6.0.0 deprecates SNMP alerts. Ops Manager 7.0.0 will not include SNMP alerts. To learn more about other alert options, see Third-Party Service Integrations. | |||||||||||||||
Email | Sends the alert to a specified email address. | |||||||||||||||
SMS | 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 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. | |||||||||||||||
Sends the alert to a HipChat room message stream. Enter the
HipChat room name and API token. | ||||||||||||||||
Sends the alert to a Slack channel in the authorized Slack workplace for the Organization.
To learn more about Bot users in Slack, see the Slack documentation. | ||||||||||||||||
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. PagerDuty decommissioned their REST API v1 key in October 2018. If you have a v1 key, you can continue to use that key with Ops Manager. All new PagerDuty keys use their REST API v2, but Ops Manager does not support their v2 keys. If you don't have their REST API v1 key, use the PagerDuty Events API v1 instead. | ||||||||||||||||
Webhook | 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 configure this option, configure the Webhook settings on the Project Settings page. To use this method at the Global level:
Ops Manager adds a request header called
If you specify a key in the Webhook Secret field,
MongoDB Ops Manager adds the | |||||||||||||||
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. | ||||||||||||||||
Administrators | Sends the alert to the email address specified in the
Admin Email Address field in the Ops Manager
configuration options. | |||||||||||||||
Global Alerts Summary Email | Sends a summary email of all global alerts to the specified
email address. |
Disable or Enable a Global Alert Configuration
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.