Namespace AlarmSuppressionHistoryItem

Human-readable reason for this alarm suppression. 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.}

Configured dimension filter for suppressing alarm state entries that include the set of specified dimension key-value pairs.

Example: {@code {\"resourceId\": \"ocid1.instance.region1.phx.exampleuniqueID\"}}

A user-friendly name for the alarm suppression. It does not have to be unique, and it's changeable. Avoid entering confidential information.

The level of this alarm suppression. {@code ALARM} indicates a suppression of the entire alarm, regardless of dimension. {@code DIMENSION} indicates a suppression configured for specified dimensions.

The OCID of the alarm suppression.

The start date and time for the suppression actually starts, inclusive. Format defined by RFC3339.

Example: {@code 2023-02-01T01:02:29.600Z}

The end date and time for the suppression actually ends, inclusive. Format defined by RFC3339.

Example: {@code 2023-02-01T02:02:29.600Z}