Navigation
This version of the documentation is archived and no longer supported. It will be removed on 01 March 2021. 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.

Acknowledge One Alert

Note

Groups and projects are synonymous terms. Your {GROUP-ID} is the same as your project id. For existing groups, your group/project id remains the same. This page uses the more familiar term group when referring to descriptions. The endpoint remains as stated in the document.

Resource

Base URL: https://{OPSMANAGER-HOST}:{PORT}/api/public/v1.0

PATCH /groups/{GROUP-ID}/alerts/{ALERT-ID}

Request Path Parameters

Parameter Type Necessity Description
PROJECT-ID string Required Unique identifier for the Project in which this alert is set.
ALERT-ID string Required Unique identifier for the Alert.

Request Query Parameters

This endpoint may use any of the HTTP request query parameters available to all Ops Manager API resources. These are all optional.

Name Type Description Default
pretty boolean Indicates whether the response body should be in a prettyprint format. false
envelope boolean

Indicates whether or not to wrap the response in an envelope.

Some API clients cannot access the HTTP response headers or status code. To remediate this, set envelope=true in the query.

For endpoints that return one result, the response body includes:

Name Description
status HTTP response code
envelope Expected response body
false

Request Body Parameters

Field Type Necessity Description
acknowledged
Until
string Conditional

Timestamp in ISO 8601 date and time format until which the alert should be acknowledged.

  • To acknowledge an alert “forever”, set the field value to a large number of years in the future. Recommend setting to 100 years in the future.
  • To unacknowledge an acknowledged alert, remove this parameter from your request.
acknowledgement
Comment
string Optional

Text description of the reason for this acknowledgement.

Ops Manager displays the comment next to the message that the alert has been acknowledged.

Response

The fields in the return document depend on the alert type:

Name Type Description
acknowledged
Until
string

Timestamp, in the number of seconds that have elapsed since the UNIX epoch until which the alert has been acknowledged.

Ops Manager returns this value if the alert has been acknowledged.

acknowledgement
Comment
string

Comment left by the user who acknowledged the alert.

Ops Manager returns this value if the alert has been acknowledged.

acknowledging
Username
string

Username of the user who acknowledged the alert.

Ops Manager returns this value if the alert has been acknowledged.

alertConfigId string Unique identifier for the alert configuration that triggered this alert.
clusterId string

Unique identifier for the cluster to which this alert applies.

Ops Manager returns this value if "eventTypeName" was set to BACKUP, REPLICA_SET, or CLUSTER.

clusterName string

Name of the cluster to which this alert applies.

Ops Manager returns this value if "eventTypeName" was set to BACKUP, REPLICA_SET, and CLUSTER.

created string Timestamp, in the number of seconds that have elapsed since the UNIX epoch when the alert was opened.
currentValue object

Current value of the metric that triggered the alert.

Ops Manager returns this value if "eventTypeName" was set to HOST_METRIC.

currentValue
.number
number Value of the metric.
currentValue
.units
string

Units for the value. Value depends on the type of metric.

Example

A metric that measures memory consumption would have a byte measurement, while a metric that measures time would have a time unit.

Ops Manager can return:

  • RAW
  • BITS
  • BYTES
  • KILOBITS
  • KILOBYTES
  • MEGABITS
  • MEGABYTES
  • GIGABITS
  • GIGABYTES
  • TERABYTES
  • PETABYTES
  • MILLISECONDS
  • SECONDS
  • MINUTES
  • HOURS
  • DAYS
eventTypeName string

Name of the event that triggered the alert.

To review the types of events that generate alerts, see Alert Types

groupId string Unique identifier of the group for which this alert was opened.
hostId string

unique identifier for the host to which the metric pertains.

Ops Manager returns this value if "eventTypeName" was set to HOST, HOST_METRIC, or REPLICA_SET.

hostnameAndPort string

Hostname and port of each host to which the alert applies. This can be a hostname, an FQDN, an IPv4 address, or an IPv6 address.

Ops Manager returns this value if "eventTypeName" was set to HOST, HOST_METRIC, or REPLICA_SET.

id string Unique identifier for this alert.
lastNotified string Timestamp, in the number of seconds that have elapsed since the UNIX epoch when the last notification was sent for this alert. Only displayed if notifications have been sent.
links array of objects One or more links to sub-resources and/or related resources. The relations between URLs are explained in the Web Linking Specification
metricName string

Name of the measurement whose value went outside the threshold.

Ops Manager returns this value if "eventTypeName" was set to OUTSIDE_METRIC_THRESHOLD.

For possible values, see Measurement Types for Alerts.

replicaSetName string

Name of the replica set.

Ops Manager returns this value if "eventTypeName" was set to HOST, HOST_METRIC, BACKUP, and REPLICA_SET.

resolved string

Timestamp, in the number of seconds that have elapsed since the UNIX epoch when the alert was closed.

Ops Manager returns this value if "status" : "CLOSED".

status string

Current state of the alert. Ops Manager can return:

  • TRACKING

    The alert condition exists but has not persisted beyond the defined notification delay. For details, see Request Query Parameters.

  • OPEN

  • CLOSED

  • CANCELLED

sourceTypeName string

Type of server being backed up when "eventTypeName" : "BACKUP". Ops Manager can return:

  • REPLICA_SET
  • SHARDED_CLUSTER
  • CONFIG_SERVER
tags string array Identifying labels set for this alert.
typeName string Deprecated field. |mms| ignores it.
updated string Timestamp, in the number of seconds that have elapsed since the UNIX epoch when the alert was last updated.

Example Request

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
curl --user "{PUBLIC-KEY}:{PRIVATE-KEY}" --digest \
     --header "Accept: application/json" \
     --header "Content-Type: application/json" \
     --include \
     --request PATCH "https://<ops-manager-host>/api/public/v1.0/groups/{PROJECT-ID}/alerts/{ALERT-CONFIG-ID}"
     --data '
       {
         "acknowledgedUntil": "2016-04-15T00:00:00-0400",
         "acknowledgementComment": "This is normal. Please ignore."
       }'

Example Response

Response Header

HTTP/1.1 401 Unauthorized
Content-Type: application/json;charset=ISO-8859-1
Date: {dateInUnixFormat}
WWW-Authenticate: Digest realm="MMS Public API", domain="", nonce="{nonce}", algorithm=MD5, op="auth", stale=false
Content-Length: {requestLengthInBytes}
Connection: keep-alive
HTTP/1.1 200 OK
Vary: Accept-Encoding
Content-Type: application/json
Strict-Transport-Security: max-age=300
Date: {dateInUnixFormat}
Connection: keep-alive
Content-Length: {requestLengthInBytes}

Response Body

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
{
  "id" : "533dc45ee4b00835ff81ec2a",
  "groupId" : "5196d3628d022db4cbc26d9e",
  "eventTypeName" : "OUTSIDE_METRIC_THRESHOLD",
  "status" : "OPEN",
  "acknowledgedUntil" : "2014-04-15T04:00:00Z",
  "acknowledgementComment" : "This is normal. Please ignore.",
  "acknowledgingUsername" : "someuser@example.com",
  "created" : "2014-04-03T20:28:14Z",
  "updated" : "2014-04-03T20:33:14Z",
  "lastNotified" : "2014-04-03T20:33:23Z",
  "metricName": "ASSERTS_REGULAR",
  "currentValue" : {
    "number" : 0.0,
    "units" : "RAW"
  },
  "links" : []
}