» Data Source: oci_monitoring_alarm_statuses

This data source provides the list of Alarm Statuses in Oracle Cloud Infrastructure Monitoring service.

List the status of each alarm in the specified compartment.

» Example Usage

data "oci_monitoring_alarm_statuses" "test_alarm_statuses" {
    #Required
    compartment_id = "${var.compartment_id}"

    #Optional
    compartment_id_in_subtree = "${var.alarm_status_compartment_id_in_subtree}"
    display_name = "${var.alarm_status_display_name}"
}

» Argument Reference

The following arguments are supported:

• compartment_id - (Required) The OCID of the compartment containing the resources monitored by the metric that you are searching for. Use tenancyId to search in the root compartment.
• compartment_id_in_subtree - (Optional) When true, returns resources from all compartments and subcompartments. The parameter can only be set to true when compartmentId is the tenancy OCID (the tenancy is the root compartment). A true value requires the user to have tenancy-level permissions. If this requirement is not met, then the call is rejected. When false, returns resources from only the compartment specified in compartmentId. Default is false.
• display_name - (Optional) A filter to return only resources that match the given display name exactly. Use this filter to list an alarm by name. Alternatively, when you know the alarm OCID, use the GetAlarm operation.

» Attributes Reference

The following attributes are exported:

• alarm_statuses - The list of alarm_statuses.

» AlarmStatus Reference

The following attributes are exported:

• display_name - The configured name of the alarm. Example: High CPU Utilization
• id - The OCID of the alarm.
• severity - The configured severity of the alarm. Example: CRITICAL
• status - The status of this alarm. Example: FIRING

• suppression - The configuration details for suppressing an alarm.

  • description - 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: Planned outage due to change IT-1234.

  • time_suppress_from - The start date and time for the suppression to take place, inclusive. Format defined by RFC3339. Example: 2019-02-01T01:02:29.600Z

  • time_suppress_until - The end date and time for the suppression to take place, inclusive. Format defined by RFC3339. Example: 2019-02-01T02:02:29.600Z

• timestamp_triggered - Timestamp for the transition of the alarm state. For example, the time when the alarm transitioned from OK to Firing. Example: 2019-02-01T01:02:29.600Z