Namespace AlarmSuppressionSummary

The OCID of the compartment containing the alarm suppression.

Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace": {"bar-key": "value"}}}

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.

Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}

The OCID of the alarm suppression.

The current lifecycle state of the alarm suppression.

Example: {@code DELETED}

The date and time the alarm suppression was created. Format defined by RFC3339.

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

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 date and time the alarm suppression was last updated (deleted). Format defined by RFC3339.

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