Human-readable reason for suppressing alarm notifications. It does not have to be unique, and it's changeable. Avoid entering confidential information.
Oracle recommends including tracking information for the event or associated work, such as a ticket number.
Example: {@code Planned outage due to change IT-1234.}
The start date and time for the suppression to take place, inclusive. Format defined by RFC3339.
Example: {@code 2023-02-01T01:02:29.600Z}
The end date and time for the suppression to take place, inclusive. Format defined by RFC3339.
Example: {@code 2023-02-01T02:02:29.600Z}
The configuration details for an alarm-wide suppression. For dimension-specific suppressions, see AlarmSuppression. For information about alarms, see Alarms Overview.