- Monitoring and Alerts >
- System Alerts
System Alerts¶
On this page
Overview¶
System alerts are internal health checks that monitor the health of Ops Manager itself, including the health of backing databases, Backup Daemons, and backed-up deployments. Ops Manager runs health checks every 5 minutes.
To view system alerts, click the Admin link at the top of Ops Manager, select the Alerts tab, and then select the Open Alerts link under System Alerts.
Users with the Global Owner or Global Monitoring Admin roles can modify notification settings or disable an alert.
System Alerts¶
Ops Manager provides the following system alerts:
-
System detects backup oplog TTL was resized
¶ Sends an alert if the Backup Daemon has fallen so far behind in applying oplog entries that Ops Manager has extended the period of time it will store the entries. By default, Ops Manager stores oplog entries in the Oplog Store for 24 hours. If the Daemon has not yet applied an entry an hour before its expiration, Ops Manager extends the storage period by three hours. If the entry again reaches an hour from expiration, Ops Manager continues to extend the storage period, up to seven days. The system sets the storage period in the Daemon’s
mms.backup.restore.snapshotPITExpirationHours
setting.If you receive this alert, check that your Backup Daemon is running and that it has sufficiently performant hardware to apply oplog entries in a timely manner.
-
System detects backing database startup warnings
¶ Sends an alert if the MongoDB process hosting a backing database contains
startupWarnings
in its log files. Check the logs on the server running the MongoDB process.
-
System detects an unhealthy database backing the system
¶ Sends an alert if Ops Manager cannot connect to a backing database and run the ping command.
-
System detects backup daemon is down
¶ Sends an alert the Backup Daemon has not pinged Ops Manager for more than 15 minutes.
-
System detects backup daemon has low free head space
¶ Sends an alert if the disk partition on which the local copy of a backed-up replica set is stored has less than 10 GB of free space remaining.
The Ops Manager Daemons Page displays head space used for each daemon. The
mms.alerts.LowHeadFreeSpace.minimumHeadFreeSpaceGB
setting controls the alert threshold, which has a default value of 10 GB.
Procedures¶
Modify Notification Settings for a System Alert¶
Click the Admin link in the top right corner of Ops Manager.¶
Ops Manager displays the Admin link only if you have administrative privileges.
Select the Alerts tab and then the System Alert Settings page.¶
On the line for the alert, click the ellipsis icon and select Edit.¶
Select the alert recipients and delivery methods.¶
In the Send to section, configure notifications. To add notifications or recipients, click Add and select from the options listed below. To test a notification, click the test link that appears after you configure the notification and ensure that the service you are testing receives the message.
Notification Option | Description |
---|---|
Group (group or global alerts only) | Sends the alert by email or SMS to the group. If you select SMS, Ops Manager sends the text message to the number configured on each user’s Account page. To send only to specific roles, deselect All Roles and select the desired roles. |
Ops Manager User | Sends the alert by email or SMS to a specified Ops Manager user. If you select SMS, Ops Manager sends the text message to the number configured on the user’s Account page. |
SNMP Host | Specify the hostname that will receive the v2c trap on standard
port 162 . The MIB file for SNMP is available for download here. |
Sends the alert to a specified email address. | |
HipChat | Sends the alert to a HipChat room message stream. Enter the HipChat room name and API token. |
Slack | 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 https://api.slack.com/web page in your Slack account. For information on Bot users in Slack, see https://api.slack.com/bot-users. |
Flowdock | Sends the alert to a Flowdock account. Enter the following:
|
PagerDuty | Sends the alert to a PagerDuty account. Enter only the PagerDuty service 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 (group alerts only) | 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 Public API’s Alerts resource. This option is available only if you have configured Webhook settings on the Group Settings page. |
Administrators (global or system alerts only) | Sends the alert to the email address specified in the Admin Email Address field in the Ops Manager configuration options. |
Click Save.¶
Disable a System Alert¶
Click the Admin link in the top right corner of Ops Manager.¶
Ops Manager displays the Admin link only if you have administrative privileges.
Select the Alerts tab and then the System Alert Settings page.¶
Disable the alert.¶
On the line for the system alert that you want to disable, click the ellipsis icon and select Disable.