Alerts¶

On this page

Types

The “Alerts” section provides access to On-Prem MongoDB Management Service’s alert system. This section has three tabs: open alerts, closed alerts, and alert settings. Following the installation of your first Monitoring agent, the system configures an alert to send an email when the agent is down. You can delete or modify this alert as you like.

Types¶

There are four possible alert types. On Prem MMS Monitoring:

“Host Down” activates in response to a mongod or other monitored instance restarts or fails to check in to MMS within 90 seconds. There are no “host down” alerts if the agent is down.
“Agent Down” activates in response to an agent that fails to report to MMS within 90 seconds.
“Host Recovering” activates when a replica set member enters RECOVERING status.
“Metric Min/Max Value” activates when a monitored metric passes a specified threshold.

MMS will add additional alert types in the near future.

Configure Notifications¶

You can create notifications for any of the above alert types. Click on the + Add Alert button next to the word “Alerts” at the top of these pages. This will raise a dialogue where you can create email, SMS, or SNMP alerts for any of these event types.

Note

The MIB file for SNMP is available for download here.

You can configure the following options:

For all Alerts Except Metric Min/Max Value¶

Address specifies an address to send alert emails. For SMS alerts, specify the telephone number that will receive the alert. For SNMP alerts, specify the hostname that will receive the v2c trap on standard port 162.

Warning

Telephone numbers are not validated or checked, and users must ensure that they have entered the correct number into the Alerts interface.

If you are outside of the United States or Canada, you will need to include ‘011’ and your country code. For instance, for New Zealand (country code 64), you would need to enter ‘01164’, followed by your phone number. Alternately, you can sign up for a Google Voice number, and use that number for your authentication.

Note

Two-Factor Authentication via SMS text message does not currently support Indian mobile phone numbers (country code 91).

Type to select from text email, HTML formatted email, SMS, or SNMP alerts.

Frequency Config (minutes) to select how often to send alerts, in minutes.
Minimum Time Before Notification specifies how long MMS will wait before sending a notification. Raising this value will increase the amount of time between the identification of an issue and the alert, but it may reduce potential false positives.

You may also create multiple alerts with different minimum times before notification to implement alert escalation.

Important

The time between re-notifications increases by the frequency amount every alert cycle (e.g. 5 minutes, 10 minutes, 15 minutes, 20 minutes.)

For Metric Min/Max Value Alerts¶

Host Type specifies the kind of monitored host. Options include: standalone, primary, secondary, mongos, conf, master, slave, and individual/specific host.
Replica Set specifies a monitored replica set to include in the alert.
Field specifies the metric to use in the alert.
Alert Value specifies the alert threshold. Use the toggles in this field to select greater than or less than and avg per second or total per epoch.

Contact Type specifies the method of contact. Select from text email, HTML formatted email, SMS message, and SNMP trap.

Contact Frequency Config (minutes) to select how often to send alerts, in minutes.
Contact Min Time Before Notification specifies how long MMS will wait before sending a notification. Raising this value will increase the amount of time between the identification of an issue and the alert, but it may reduce potential false positives.

You may also create multiple alerts with different minimum times before notification to implement alert escalation.

Important

The time between re-notifications increases by the frequency amount every alert cycle (e.g. 5 minutes, 10 minutes, 15 minutes, 20 minutes.)

Unresolved Alerts¶

The “Open” tab displays a list of all monitored instances that have current unresolved alerts. Check this tab to make sure that there are no outstanding alerts.

Resolved Alerts¶

The “Closed” tab displays a record of all historical alerts. Use this tab as a record of past activity.

Alert Settings¶

The “Settings” tab provides an interface for configuring alerts. You can delete and disable existing alerts using the function buttons in the right hand column.

SNMP Integration¶

The following is an example of using snmpwalk to query for SNMP health status:

$ snmpwalk -v 2c -c public mms.acmewidgets.com:11611 MMS-10GEN-MIB::mmsHeartbeatObject
MMS-10GEN-MIB::mmsHeartbeatHostnameId.0 = STRING: "[hostname]-[instance#]"
MMS-10GEN-MIB::mmsHeartbeatInterval.0 = INTEGER: 300
MMS-10GEN-MIB::mmsHeartbeatMessage.0 = STRING: "Healthy"
MMS-10GEN-MIB::mmsHeartbeatMessage.0 = No more variables left in this MIB View
                                       (It is past the end of the MIB tree)

MIB File¶

The MIB file is available for download at: http://downloads.mongodb.com/on-prem-monitoring/MMS-10GEN-MIB.txt

Each of the main alert notification fields contain a brief description in the MIB file. an example of which follows:

Alert Trap:

mmsAlertId OBJECT-TYPE
    SYNTAX  DisplayString (SIZE (0.. 64))
    DESCRIPTION "The alert identification"

mmsAlertGroupName OBJECT-TYPE
    SYNTAX DisplayString (SIZE (0.. 256))
    DESCRIPTION "The MMS group name from where the alert occurred"

mmsAlertHostId OBJECT-TYPE
    SYNTAX DisplayString (SIZE (0.. 64))
    DESCRIPTION "The MMS Host ID of the affected host"

mmsAlertHostAndPort OBJECT-TYPE
    SYNTAX DisplayString (SIZE (0.. 256))
    DESCRIPTION "The hostname:port of affected host"

mmsAlertStatus OBJECT-TYPE
    SYNTAX INTEGER
    {
        new (1),
        reminder (2),
        clear (3)
    }
    DESCRIPTION "Is this alert new, a reminder of an existing alert, or clearing (closing)
                 an existing alert"

mmsAlertUrl OBJECT-TYPE
    SYNTAX DisplayString (SIZE (0.. 256))
    DESCRIPTION "The url of the corresponding MMS alerts list page"

mmsAlertMetricName OBJECT-TYPE
    SYNTAX DisplayString (SIZE (0.. 128))
    DESCRIPTION "The name of the triggering alert metric"

mmsAlertMetricThreshold OBJECT-TYPE
    SYNTAX DisplayString (SIZE (0.. 16))
    DESCRIPTION "The threshold set on the metric"

mmsAlertMetricValue OBJECT-TYPE
    SYNTAX DisplayString (SIZE (0.. 16))
    DESCRIPTION "The observed value of the metric which caused the alert to be triggered"

mmsAlertReplSetName OBJECT-TYPE
    SYNTAX DisplayString (SIZE (0.. 64))
    DESCRIPTION "The Replica Set name (if applicable) to which this affected host belongs"

mmsAlertSeverity OBJECT-TYPE
    SYNTAX INTEGER
    {
        debug (1),
        info (2),
        warning (3),
        error (4),
        critical (5)
    }
    DESCRIPTION "The severity of this alert, set automatically by MMS based on alert type"

mmsAlertSummary OBJECT-TYPE
    SYNTAX DisplayString (SIZE (0.. 256))
    DESCRIPTION "Summary text description of the alert condition"

Heartbeat/Health Trap:

mmsHeartbeatHostnameId OBJECT-TYPE
    SYNTAX DisplayString (SIZE (0.. 256))
    DESCRIPTION "Hostname and instance id of MMS server."

mmsHeartbeatInterval OBJECT-TYPE
    SYNTAX      Integer32
    DESCRIPTION "Interval in seconds between successive heartbeat notifications."

mmsHeartbeatMessage OBJECT-TYPE
    SYNTAX DisplayString (SIZE (0.. 256))
    DESCRIPTION "Text description of current MMS server health."

← Events Dashboards →