Update event and health notifications for a server

put/compute-ops-mgmt/v1beta2/servers/{id}/notifications

Purpose

When a server is added to Compute Ops Management, these attributes will be used to set the initial email notification subscription choices for event and daily health email notifications.

Event notification selections are made such that each selection increases the scope of the set of events that will be included. The order of event selections from minimum to maximum scope are

  • criticalNotification - Events that are marked as service events. These events may have severity levels of 'warning' or 'critical'
  • criticalNonServiceNotification - Events that are not service events but have a severity level of 'critical'
  • warningNotification - Events that are not service events but have a severity level of 'warning'

Note that healthNotification is not part of the event notification set and may be set independently.

Since each selection builds on the previous one, there exists a hierarchy between selections that must be maintained. The table below shows which notification combinations are valid. All other combinations will result in an HTTP 400 error

criticalNotification criticalNonServiceNotification warningNotification
False False False
True False False
True True False
True True True

Initial values

All values are initially false with the result being that no notifications will be sent.

URI PATH PREFIX RENAME

This API now supports the URI path prefix /compute-ops-mgmt which used to be /compute-ops. The old prefix will continue to be supported to allow for a smooth transition. The Guide contains more information about this change.

SecurityBearer
Request
path Parameters
id
required
string
Request Body schema: application/json
required
criticalNotification
required
boolean
criticalNonServiceNotification
boolean or null
warningNotification
boolean or null
healthNotification
boolean or null
Responses
200

Successful Response

400

Bad request

401

Unauthorized

403

Forbidden

404

Not found

406

Not acceptable

415

Unsupported media type

500

Internal server error

Request samples
application/json
{
  • "criticalNotification": true,
  • "criticalNonServiceNotification": true,
  • "warningNotification": true,
  • "healthNotification": true
}
Response samples
application/json
{
  • "serverId": "string",
  • "criticalNotification": true,
  • "criticalNonServiceNotification": true,
  • "warningNotification": true,
  • "healthNotification": true
}