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 |
All values are initially false with the result being that no notifications will be sent.
Successful Response
Bad request
Unauthorized
Forbidden
Not found
Not acceptable
Unsupported media type
Internal server error
{- "criticalNotification": true,
- "criticalNonServiceNotification": true,
- "warningNotification": true,
- "healthNotification": true
}
{- "serverId": "string",
- "criticalNotification": true,
- "criticalNonServiceNotification": true,
- "warningNotification": true,
- "healthNotification": true
}