Indicates the Data Safe feature to which the alert policy belongs.
The OCID of the compartment that contains the alert policy.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags
Example: {@code {\"Operations\": {\"CostCenter\": \"42\"}}}
The description of the alert policy.
The display name of the alert policy.
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags
Example: {@code {\"Department\": \"Finance\"}}
The OCID of the alert policy.
Indicates if the alert policy is user-defined (true) or pre-defined (false).
The current state of the alert.
Severity level of the alert raised by this policy.
System tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}
Creation date and time of the alert policy, in the format defined by RFC3339.
Last date and time the alert policy was updated, in the format defined by RFC3339.
An Alert Policy is a set of alerting rules evaluated against a target. The alert policy is said to be satisfied when all rules in the policy evaulate to true. If there are three rules: rule1,rule2 and rule3, the policy is satisfied if rule1 AND rule2 AND rule3 is True.