Managing Alarms

This topic describes how to create, update, suppress, and delete alarms , as well as how to retrieve alarm history. See also Best Practices for Your Alarms.

Warning

Avoid entering confidential information when assigning descriptions, tags, or friendly names to your cloud resources through the Oracle Cloud Infrastructure Console, API, or CLI.

Prerequisites

  • IAM policies: Managing alarms is part of monitoring. To monitor resources, you must be given the required type of access in a policy  written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. The policy must give you access to the monitoring services as well as the resources being monitored. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which compartment  you should work in. For more information on user authorizations for monitoring, see the Authentication and Authorization section for the related service: Monitoring or Notifications. For a common alarms policy, see Let users view alarms.
  • Metrics exist in Monitoring: The resources that you want to monitor must emit metrics to the Monitoring service.
  • Compute instances: To emit metrics, Compute instances must be monitoring-enabled. Oracle Cloud Agent software installation may also be required. For more information, see Enabling Monitoring for Compute Instances.

Tagging Resources

You can apply tags to your resources to help you organize them according to your business needs. You can apply tags at the time you create a resource, or you can update the resource later with the desired tags. For general information about applying tags, see Resource Tags.

Using the Console

To see all firing alarms
To create an alarm

This section includes steps to create example alarms as well as any kind of alarm.

To create an example threshold alarm

This procedure walks through creation of an example threshold alarm to detect Compute instances operating at non-optimal thresholds. A threshold alarm is an alarm that checks for metric values outside a given range or value. The procedure uses options as displayed in Basic Mode.

  1. Open the navigation menu. Under Solutions and Platform, go to Monitoring and click Alarm Definitions.
  2. Click Create alarm.

  3. On the Create Alarm page, under Define alarm, fill in or update the alarm settings:

    • Alarm Name: Non-Optimal Alarm
    • Alarm Severity: Warning
    • Alarm Body: Non-optimal utilization detected. An application or process may be consuming more CPU than usual.
    • Metric description
      • Compartment: (select your compartment  )
      • Metric Namespaceoci_computeagent
      • Metric NameCpuUtilization
      • Interval1m

        Note

        Valid alarm intervals depend on the frequency at which the metric is emitted. For example, a metric emitted every five minutes requires a 5-minute alarm interval or higher. Most metrics are emitted every minute, which means most metrics support any alarm interval. To determine valid alarm intervals for a given metric, check the relevant service's metric reference.
      • StatisticCount
    • Trigger rule:

      • Operatorbetween
      • Value: 60
      • Value: 80
      • Trigger Delay Minutes: 10
  4. Set up an email notification under Notifications, Destinations:
    • Destination ServiceNotifications Service
    • Compartment: (select your compartment  )
    • Topic: Click Create a topic

      • Topic Name: Operations Team
      • Topic Description: Resource Monitoring Channel
      • Subscription Protocol: Email
      • Email Addresses: (type an email address for the operations team here)
  5. Repeat notifications every day: 

    • Repeat Notification?: (select this option)
    • Notification Interval: 24 hours
  6. Click Save alarm.

To create an example absence alarm

This procedure walks through creation of an example absence alarm to detect resources that may be down or unreachable. An absence alarm is an alarm that checks for absent metrics (using the absent operator). The procedure uses options as displayed in Basic Mode.

  1. Open the navigation menu. Under Solutions and Platform, go to Monitoring and click Alarm Definitions.
  2. Click Create alarm.

  3. On the Create Alarm page, under Define alarm, fill in or update the alarm settings:

    • Alarm Name: Up/Down Resource Alarm
    • Alarm Severity: Critical
    • Alarm Body: Resource may be down. Please investigate. Move workloads to another available resource.
    • Metric description
      • Compartment: (select your compartment  )
      • Metric Namespaceoci_computeagent
      • Metric NameCpuUtilization
      • Interval1m

        Note

        Valid alarm intervals depend on the frequency at which the metric is emitted. For example, a metric emitted every five minutes requires a 5-minute alarm interval or higher. Most metrics are emitted every minute, which means most metrics support any alarm interval. To determine valid alarm intervals for a given metric, check the relevant service's metric reference.
      • StatisticCount
    • Trigger rule:

      • Operatorabsent
      • Trigger Delay Minutes: 5
  4. Set up an email notification under Notifications, Destinations:
    • Destination Service: Notifications Service
    • Compartment: (select your compartment  )
    • Topic: Click Create a topic

      • Topic Name: Operations Team
      • Topic Description: Resource Up/Down Channel
      • Subscription Protocol: Email
      • Email Addresses: (type an email address for the operations team here)

        Note

        To add a notification (subscription) for another protocol, such as PagerDuty, create a copy of this alarm and choose the corresponding protocol. For more information about subscription protocols, see To create a subscription.

  5. Repeat notifications every minute: 

    • Repeat Notification?: (select this option)
    • Notification Interval: 1 minute
  6. Click Save alarm.

To create an alarm (any kind)
  1. Open the navigation menu. Under Solutions and Platform, go to Monitoring and click Alarm Definitions.
  2. Click Create alarm.

    Note

    You can also create an alarm from a predefined query on the Service Metrics page. Expand Options and click Create an Alarm on this Query. For more information about service metrics, see Viewing Default Metric Charts.
  3. On the Create Alarm page, under Define alarm, fill in or update the alarm settings:

    Note

    To toggle between Basic Mode and Advanced Mode, click Switch to Advanced Mode or Switch to Basic Mode (to the right of Define Alarm).

    Basic Mode (default)

    By default, this page uses Basic Mode, which separates the metric from its dimensions and its trigger rule.

    • Alarm Name

      User-friendly name for the new alarm. This name is sent as the title for notifications related to this alarm.

      Rendering of the title by protocol
      Protocol Rendering of the title
      Email Subject line of the email message.
      HTTPS (Custom URL) Not rendered.
      PagerDuty Title field of the published message.
      Slack Not rendered.
    • Alarm Severity: The perceived type of response required when the alarm is in the firing state.
    • Alarm Body: The human-readable content of the notification delivered. Oracle recommends providing guidance to operators for resolving the alarm condition. Consider adding links to standard runbook practices. Example: "High CPU usage alert. Follow runbook instructions for resolution."
    • Tags (optional): If you have permissions to create a resource, you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, skip this option (you can apply tags later) or ask your administrator.
    • Metric description: The metric to evaluate for the alarm condition.
      • Compartment: The compartment  containing the resources that emit the metrics evaluated by the alarm. The selected compartment is also the storage location of the alarm. By default, the first accessible compartment is selected.
      • Metric Namespace: The service or application emitting metrics for the resources that you want to monitor.
      • Resource Group (optional): The group that the metric belongs to. A resource group is a custom string provided with a custom metric. Not applicable to service metrics.
      • Metric Name: The name of the metric. Only one metric can be specified. Example: CpuUtilization
      • Interval: The aggregation window, or the frequency at which data points are aggregated.

        Interval values
        Note

        Valid alarm intervals depend on the frequency at which the metric is emitted. For example, a metric emitted every five minutes requires a 5-minute alarm interval or higher. Most metrics are emitted every minute, which means most metrics support any alarm interval. To determine valid alarm intervals for a given metric, check the relevant service's metric reference.
        • 1m - 1 minute
        • 5m - 5 minutes
        • 1h - 1 hour
        • 1d - 1 day
        Note

        For alarm queries, the specified interval  has no effect on the resolution  of the request. The only valid value of the resolution for an alarm query request is 1m. For more information about the resolution parameter as used in alarm queries, see Alarm.

      • Statistic: The aggregation function.

        Statistic values
        • COUNT- The number of observations received in the specified time period.
        • MAX - The highest value observed during the specified time period.
        • MEAN - The value of Sum divided by Count during the specified time period.
        • MIN - The lowest value observed during the specified time period.
        • P50 - The value of the 50th percentile.
        • P90 - The value of the 90th percentile.
        • P95 - The value of the 95th percentile.
        • P99 - The value of the 99th percentile.
        • P99.5 - The value of the 99.5th percentile.
        • RATE - The per-interval average rate of change.
        • SUM - All values added together.
    • Metric dimensions: Optional filters to narrow the metric data evaluated.

      Dimension fields
      • Dimension Name: A qualifier specified in the metric definition. For example, the dimension resourceId is specified in the metric definition for CpuUtilization.

        Note

        Long lists of dimensions are trimmed.

        • To view dimensions by name, type one or more characters in the box. A refreshed (trimmed) list shows matching dimension names.
        • To retrieve all dimensions for a given metric, use the following API operation: ListMetrics
      • Dimension Value: The value you want to use for the specified dimension. For example, the resource identifier for your instance of interest.
      • + Additional dimension: Adds another name-value pair for a dimension.
    • Trigger rule: The condition that must be satisfied for the alarm to be in the firing state. The condition can specify a threshold, such as 90% for CPU Utilization, or an absence.

      • Operator: The operator used in the condition threshold.

        Operator values
        • greater than
        • greater than or equal to
        • equal to
        • less than
        • less than or equal to
        • between (inclusive of specified values)
        • outside (inclusive of specified values)
        • absent
      • Value: The value to use for the condition threshold.
      • Trigger Delay Minutes: The number of minutes that the condition must be maintained before the alarm is in firing state.
    Advanced Mode

    Click Advanced Mode or Switch to Advanced Mode to view the alarm query as a Monitoring Query Language (MQL) expression. Edit your query using MQL syntax to aggregate results by group or for additional parameter values. See Monitoring Query Language (MQL) Reference.

    • Alarm Name

      User-friendly name for the new alarm. This name is sent as the title for notifications related to this alarm.

      Rendering of the title by protocol
      Protocol Rendering of the title
      Email Subject line of the email message.
      HTTPS (Custom URL) Not rendered.
      PagerDuty Title field of the published message.
      Slack Not rendered.
    • Alarm Severity: The perceived type of response required when the alarm is in the firing state.
    • Alarm Body: The human-readable content of the notification delivered. Oracle recommends providing guidance to operators for resolving the alarm condition. Consider adding links to standard runbook practices. Example: "High CPU usage alert. Follow runbook instructions for resolution."
    • Tags (optional): If you have permissions to create a resource, you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, skip this option (you can apply tags later) or ask your administrator.
    • Metric description, dimensions, and trigger rule: The metric to evaluate for the alarm condition, including dimensions and the trigger rule.

      • Compartment: The compartment  containing the resources that emit the metrics evaluated by the alarm. The selected compartment is also the storage location of the alarm. By default, the first accessible compartment is selected.
      • Metric Namespace: The service or application emitting metrics for the resources that you want to monitor.
      • Resource Group (optional): The group that the metric belongs to. A resource group is a custom string provided with a custom metric. Not applicable to service metrics.
      • Query Code Editor box: The alarm query as a Monitoring Query Language (MQL) expression.

        Note

        Valid alarm intervals depend on the frequency at which the metric is emitted. For example, a metric emitted every five minutes requires a 5-minute alarm interval or higher. Most metrics are emitted every minute, which means most metrics support any alarm interval. To determine valid alarm intervals for a given metric, check the relevant service's metric reference.

        Example alarm query: 

        CpuUtilization[1m]{availabilityDomain=AD1}.groupBy(poolId).percentile(0.9) > 85

        For query syntax and examples, see Working with Metric Queries.

      • Trigger Delay Minutes: The number of minutes that the condition must be maintained before the alarm is in firing state.

    The chart below the Define alarm section dynamically displays the last six hours of emitted metrics according to currently selected fields for the query. Very small or large values are indicated by International System of Units (SI units), such as M for mega (10 to the sixth power).

  4. Set up notifications: Under Notifications, fill in the fields.

    • Destinations
      • Destination Service: The provider of the destination to use for notifications.

        Available options: 

      • Compartment: The compartment  storing the topic to be used for notifications. Can be a different compartment from the alarm and metric. By default, the first accessible compartment is selected.
      • Topic: The topic to use for notifications. Each topic supports a subscription protocol, such as PagerDuty.
      • Create a topic: Sets up a topic and subscription protocol in the selected compartment, using the specified destination service.

        • Topic Name: User-friendly name for the new topic. Example: "Operations Team " for a topic used to notify operations staff of firing alarms.
        • Topic Description: Description of the new topic.
        • Subscription Protocol: Medium of communication to use for the new topic. Configure your subscription for the protocol you want: 

          Email subscription

          Sends an email message when you publish a message  to the subscription's parent topic .

          • Subscription Protocol: Select Email.
          • Subscription Email: Type an email address.
          HTTPS (Custom URL) subscription

          Sends specified information when you publish a message  to the subscription's parent topic .

          Endpoint format (URL using HTTPS protocol): 

          https://<anyvalidURL>
          Basic access authentication is supported, allowing you to specify a username and password in the URL, as in https://user:password@domain.com or https://user@domain.com. The username and password are encrypted over the SSL connection established when using HTTPS. For more information about Basic Access Authentication, see RFC-2617.
          Query parameters are not allowed in URLs.
          • Subscription Protocol: Select HTTPS (Custom URL).
          • Subscription URL: Type (or copy and paste) the URL you want to use as the endpoint.
          PagerDuty subscription

          Creates a PagerDuty incident by default when you publish a message  to the subscription's parent topic .

          Endpoint format (URL): 

          https://events.pagerduty.com/integration/<integrationkey>/enqueue
          Query parameters are not allowed in URLs.

          To create an endpoint for a PagerDuty subscription (set up and retrieve an integration key), see the PagerDuty documentation.

          • Subscription Protocol: Select PagerDuty.
          • Subscription URL: Type (or copy and paste) the integration key portion of the URL for your PagerDuty subscription. (The other portions of the URL are hard-coded.)
          Slack subscription

          Sends a message to the specified Slack channel by default when you publish a message  to the subscription's parent topic .

          Endpoint format (URL): 

          https://hooks.slack.com/services/<webhook-token>

          The <webhook-token> portion of the URL contains two slashes (/).

          Query parameters are not allowed in URLs.

          To create an endpoint for a Slack subscription (using a webhook for your Slack channel), see the Slack documentation.

          • Subscription Protocol: Select Slack.
          • Subscription URL: Type (or copy and paste) the Slack endpoint, including your webhook token.
      • + Additional destination service: Adds another destination service and topic to use for notifications.

        Note

        Each alarm is limited to one destination per supported destination service.
    • Repeat Notification?: While the alarm is in the firing state, resends notifications at the specified interval.
    • Notification Interval: The period of time to wait before resending the notification.
    • Suppress Notifications: Sets up a suppression time window during which to suspend evaluations and notifications. Useful for avoiding alarm notifications during system maintenance periods.

      • Suppression Description
      • Start Time
      • End Time
  5. If you want to disable the new alarm, clear Enable This Alarm?.
  6. Click Save alarm.

    The new alarm is listed on the Alarm Definitions page.

To disable or enable an alarm
  1. Open the navigation menu. Under Solutions and Platform, go to Monitoring and click Alarm Definitions.
  2. Click the alarm that you want to disable or enable.
  3. On the alarm detail page, select or clear Alarm is Enabled.

    Note

    You can also disable and enable alarms when creating or editing an alarm.
To move an alarm to a different compartment

Associated metrics remain in their current compartments. For more information, see Moving Alarms to a Different Compartment.

Note

To move resources between compartments, resource users must have sufficient access permissions on the compartment that the resource is being moved to, as well as the current compartment. For more information about permissions for Monitoring resources, see Details for Monitoring.
  1. Open the navigation menu. Under Solutions and Platform, go to Monitoring and click Alarm Definitions.
  2. In the List Scope section, select a compartment.
  3. Click the alarm that you want to move.
  4. On the alarm detail page, click Move Resource.
  5. Choose the destination compartment from the list.
  6. Click Move Resource.
To update an alarm
  1. Open the navigation menu. Under Solutions and Platform, go to Monitoring and click Alarm Definitions.
  2. Click the alarm that you want to update.
  3. Go to Actions on the right, and then click Edit Alarm.
  4. On the Edit Alarm page, under Define alarm, update alarm settings as needed:

    Basic Mode (default)

    By default, this page uses Basic Mode, which separates the metric from its dimensions and its trigger rule.

    • Alarm Name

      User-friendly name for the new alarm. This name is sent as the title for notifications related to this alarm.

      Rendering of the title by protocol
      Protocol Rendering of the title
      Email Subject line of the email message.
      HTTPS (Custom URL) Not rendered.
      PagerDuty Title field of the published message.
      Slack Not rendered.
    • Alarm Severity: The perceived type of response required when the alarm is in the firing state.
    • Alarm Body: The human-readable content of the notification delivered. Oracle recommends providing guidance to operators for resolving the alarm condition. Consider adding links to standard runbook practices. Example: "High CPU usage alert. Follow runbook instructions for resolution."
    • Tags (optional): If you have permissions to create a resource, you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, skip this option (you can apply tags later) or ask your administrator.
    • Metric description: The metric to evaluate for the alarm condition.
      • Compartment: The compartment  containing the resources that emit the metrics evaluated by the alarm. The selected compartment is also the storage location of the alarm. By default, the first accessible compartment is selected.
      • Metric Namespace: The service or application emitting metrics for the resources that you want to monitor.
      • Resource Group (optional): The group that the metric belongs to. A resource group is a custom string provided with a custom metric. Not applicable to service metrics.
      • Metric Name: The name of the metric. Only one metric can be specified. Example: CpuUtilization
      • Interval: The aggregation window, or the frequency at which data points are aggregated.

        Interval values
        Note

        Valid alarm intervals depend on the frequency at which the metric is emitted. For example, a metric emitted every five minutes requires a 5-minute alarm interval or higher. Most metrics are emitted every minute, which means most metrics support any alarm interval. To determine valid alarm intervals for a given metric, check the relevant service's metric reference.
        • 1m - 1 minute
        • 5m - 5 minutes
        • 1h - 1 hour
        • 1d - 1 day
        Note

        For alarm queries, the specified interval  has no effect on the resolution  of the request. The only valid value of the resolution for an alarm query request is 1m. For more information about the resolution parameter as used in alarm queries, see Alarm.

      • Statistic: The aggregation function.

        Statistic values
        • COUNT- The number of observations received in the specified time period.
        • MAX - The highest value observed during the specified time period.
        • MEAN - The value of Sum divided by Count during the specified time period.
        • MIN - The lowest value observed during the specified time period.
        • P50 - The value of the 50th percentile.
        • P90 - The value of the 90th percentile.
        • P95 - The value of the 95th percentile.
        • P99 - The value of the 99th percentile.
        • P99.5 - The value of the 99.5th percentile.
        • RATE - The per-interval average rate of change.
        • SUM - All values added together.
    • Metric dimensions: Optional filters to narrow the metric data evaluated.

      Dimension fields
      • Dimension Name: A qualifier specified in the metric definition. For example, the dimension resourceId is specified in the metric definition for CpuUtilization.

        Note

        Long lists of dimensions are trimmed.

        • To view dimensions by name, type one or more characters in the box. A refreshed (trimmed) list shows matching dimension names.
        • To retrieve all dimensions for a given metric, use the following API operation: ListMetrics
      • Dimension Value: The value you want to use for the specified dimension. For example, the resource identifier for your instance of interest.
      • + Additional dimension: Adds another name-value pair for a dimension.
    • Trigger rule: The condition that must be satisfied for the alarm to be in the firing state. The condition can specify a threshold, such as 90% for CPU Utilization, or an absence.

      • Operator: The operator used in the condition threshold.

        Operator values
        • greater than
        • greater than or equal to
        • equal to
        • less than
        • less than or equal to
        • between (inclusive of specified values)
        • outside (inclusive of specified values)
        • absent
      • Value: The value to use for the condition threshold.
      • Trigger Delay Minutes: The number of minutes that the condition must be maintained before the alarm is in firing state.
    Advanced Mode

    Click Advanced Mode or Switch to Advanced Mode to view the alarm query as a Monitoring Query Language (MQL) expression. Edit your query using MQL syntax to aggregate results by group or for additional parameter values. See Monitoring Query Language (MQL) Reference.

    • Alarm Name

      User-friendly name for the new alarm. This name is sent as the title for notifications related to this alarm.

      Rendering of the title by protocol
      Protocol Rendering of the title
      Email Subject line of the email message.
      HTTPS (Custom URL) Not rendered.
      PagerDuty Title field of the published message.
      Slack Not rendered.
    • Alarm Severity: The perceived type of response required when the alarm is in the firing state.
    • Alarm Body: The human-readable content of the notification delivered. Oracle recommends providing guidance to operators for resolving the alarm condition. Consider adding links to standard runbook practices. Example: "High CPU usage alert. Follow runbook instructions for resolution."
    • Tags (optional): If you have permissions to create a resource, you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, skip this option (you can apply tags later) or ask your administrator.
    • Metric description, dimensions, and trigger rule: The metric to evaluate for the alarm condition, including dimensions and the trigger rule.

      • Compartment: The compartment  containing the resources that emit the metrics evaluated by the alarm. The selected compartment is also the storage location of the alarm. By default, the first accessible compartment is selected.
      • Metric Namespace: The service or application emitting metrics for the resources that you want to monitor.
      • Resource Group (optional): The group that the metric belongs to. A resource group is a custom string provided with a custom metric. Not applicable to service metrics.
      • Query Code Editor box: The alarm query as a Monitoring Query Language (MQL) expression.

        Note

        Valid alarm intervals depend on the frequency at which the metric is emitted. For example, a metric emitted every five minutes requires a 5-minute alarm interval or higher. Most metrics are emitted every minute, which means most metrics support any alarm interval. To determine valid alarm intervals for a given metric, check the relevant service's metric reference.

        Example alarm query: 

        CpuUtilization[1m]{availabilityDomain=AD1}.groupBy(poolId).percentile(0.9) > 85

        For query syntax and examples, see Working with Metric Queries.

      • Trigger Delay Minutes: The number of minutes that the condition must be maintained before the alarm is in firing state.

    The chart below the Define alarm section dynamically displays the last six hours of emitted metrics according to currently selected fields for the query. Very small or large values are indicated by International System of Units (SI units), such as M for mega (10 to the sixth power).

  5. Under Notifications, update settings as needed: 

    • Destinations
      • Destination Service: The provider of the destination to use for notifications.

        Available options: 

      • Compartment: The compartment  storing the topic to be used for notifications. Can be a different compartment from the alarm and metric. By default, the first accessible compartment is selected.
      • Topic: The topic to use for notifications. Each topic supports a subscription protocol, such as PagerDuty.
      • Create a topic: Sets up a topic and subscription protocol in the selected compartment, using the specified destination service.

        • Topic Name: User-friendly name for the new topic. Example: "Operations Team " for a topic used to notify operations staff of firing alarms.
        • Topic Description: Description of the new topic.
        • Subscription Protocol: Medium of communication to use for the new topic. Configure your subscription for the protocol you want: 

          Email subscription

          Sends an email message when you publish a message  to the subscription's parent topic .

          • Subscription Protocol: Select Email.
          • Subscription Email: Type an email address.
          HTTPS (Custom URL) subscription

          Sends specified information when you publish a message  to the subscription's parent topic .

          Endpoint format (URL using HTTPS protocol): 

          https://<anyvalidURL>
          Basic access authentication is supported, allowing you to specify a username and password in the URL, as in https://user:password@domain.com or https://user@domain.com. The username and password are encrypted over the SSL connection established when using HTTPS. For more information about Basic Access Authentication, see RFC-2617.
          Query parameters are not allowed in URLs.
          • Subscription Protocol: Select HTTPS (Custom URL).
          • Subscription URL: Type (or copy and paste) the URL you want to use as the endpoint.
          PagerDuty subscription

          Creates a PagerDuty incident by default when you publish a message  to the subscription's parent topic .

          Endpoint format (URL): 

          https://events.pagerduty.com/integration/<integrationkey>/enqueue
          Query parameters are not allowed in URLs.

          To create an endpoint for a PagerDuty subscription (set up and retrieve an integration key), see the PagerDuty documentation.

          • Subscription Protocol: Select PagerDuty.
          • Subscription URL: Type (or copy and paste) the integration key portion of the URL for your PagerDuty subscription. (The other portions of the URL are hard-coded.)
          Slack subscription

          Sends a message to the specified Slack channel by default when you publish a message  to the subscription's parent topic .

          Endpoint format (URL): 

          https://hooks.slack.com/services/<webhook-token>

          The <webhook-token> portion of the URL contains two slashes (/).

          Query parameters are not allowed in URLs.

          To create an endpoint for a Slack subscription (using a webhook for your Slack channel), see the Slack documentation.

          • Subscription Protocol: Select Slack.
          • Subscription URL: Type (or copy and paste) the Slack endpoint, including your webhook token.
      • + Additional destination service: Adds another destination service and topic to use for notifications.

        Note

        Each alarm is limited to one destination per supported destination service.
    • Repeat Notification?: While the alarm is in the firing state, resends notifications at the specified interval.
    • Notification Interval: The period of time to wait before resending the notification.
    • Suppress Notifications: Sets up a suppression time window during which to suspend evaluations and notifications. Useful for avoiding alarm notifications during system maintenance periods.

      • Suppression Description
      • Start Time
      • End Time
  6. Select or clear Enable this alarm?.
  7. Click Save alarm.

    The updated alarm settings are listed on the Alarm Definitions page.

To update an alarm after moving a resource

This section shows how to update the metric compartment of an alarm after you move a resource that is emitting metrics monitored by the alarm. For example, if you move a block volume to another compartment, then the alarm must be updated if you want to continue monitoring metrics from the moved block volume.

  1. Open the navigation menu. Under Solutions and Platform, go to Monitoring and click Alarm Definitions.
  2. Click the alarm that you want to update.
  3. Go to Actions on the right, and then click Edit Alarm.
  4. Update the metric compartment: On the Edit Alarm page, under Metric description (or Metric description, dimensions, and trigger rule for Advanced mode), change the Compartment to the compartment where the resource has been moved.

    The chart below the Define alarm section dynamically updates according to the selected compartment, displaying the last six hours of emitted metrics. Very small or large values are indicated by International System of Units (SI units), such as M for mega (10 to the sixth power).

    If the chart is not showing the expected data, then the old compartment might be specified in the query (MQL), as in the following example: 

    IopsRead[1m]{compartmentId="ocid1.compartment.oc1.phx..oldcompartmentexampleuniqueID"}.grouping().max()
  5. If the old compartment is specified in the query, then update the query to reference the new compartment: 
    1. Click Advanced Mode or Switch to Advanced Mode to view the alarm query as a Monitoring Query Language (MQL) expression.
    2. In Query Code Editor, update the query to reference the new compartment.

      View example

      Original query:

      IopsRead[1m]{compartmentId="ocid1.compartment.oc1.phx..oldcompartmentexampleuniqueID"}.grouping().max()

      Updated query:

      Read[1m]{compartmentId="ocid1.compartment.oc1.phx..newcompartmentexampleuniqueID"}.grouping().max()

      For more information about query syntax and more examples, see Working with Metric Queries.

      The chart below the Define alarm section dynamically updates according to the updated query, displaying the last six hours of emitted metrics. Very small or large values are indicated by International System of Units (SI units), such as M for mega (10 to the sixth power).

      If the chart is not showing the expected data, then confirm that every compartment reference (Compartment, Query Code Editor) points to the new compartment.

  6. Click Save alarm.

    The alarm now monitors metrics from the new compartment.

To suppress alarms
Important

Only one suppression  can be configured per alarm. Any existing suppression for the alarm is overwritten when you apply a new suppression.
  1. Open the navigation menu. Under Solutions and Platform, go to Monitoring and click Alarm Definitions.
  2. On the Alarm Definitions page, select the check boxes for the alarms you want to suppress.

    Note

    You can also suppress alarms from the Alarm Status page or when creating or editing an alarm.
  3. Go to Actions and select Add Suppressions.
  4. In the Suppress alarms dialog box, select a Start Time and End Time and then optionally fill in a Suppression Description.
  5. Click Apply suppressions.

    A suppression is created for each selected alarm. The updated alarm settings are listed on the Alarm Definitions page.

To delete alarms
  1. Open the navigation menu. Under Solutions and Platform, go to Monitoring and click Alarm Definitions.
  2. On the Alarm Definitions page, select the check boxes for the alarms you want to delete.

    Note

    You can also delete an alarm from its detail page.
  3. Go to Actions and select Delete Alarms.

    The deleted alarms are removed from the compartment and are no longer displayed on the Alarm definitions page.

To view alarm history
  1. Open the navigation menu. Under Solutions and Platform, go to Monitoring and click Alarm Definitions.
  2. On the Alarm Definitions page, click the alarm that you want to view history for.

    The alarm detail page displays a chart showing data for the indicated time range and a list of timestamped transitions, such as Firing to OK.

    Alarm history is retained for 90 days.