Create, update, suppress, and delete alarms. Retrieve alarm history.
The following pages describe how you can manage alarms:
- Creating an Alarm
- Viewing an Alarm Metric Chart
- Listing Alarms
- Listing Alarm Statuses
- Listing Metric Stream Status in an Alarm
- Getting an Alarm's Details
- Getting History of an Alarm
- Updating an Alarm
- Enabling an Alarm
- Disabling an Alarm
- Suppressing an Alarm
- Removing Suppression from an Alarm
- Moving an Alarm
- Tagging an Alarm
- Deleting an Alarm
See also Best Practices for Your Alarms.
- IAM policies: Managing alarms is part of monitoring. To monitor resources, you must have 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 have and which compartment you should work in. For more information about user authorizations for monitoring, see IAM Policies (Monitoring). Administrators: For common alarm policies, see Alarm Access for Groups.
- Metrics exist in Monitoring: The resources that you want to monitor must emit metrics to the Monitoring service.
- Compute instances: To emit metrics, the Compute Instance Monitoring plugin must be enabled on the instance, and plugins must be running. The instance must also have either a service gateway or a public IP address to send metrics to the Monitoring service. For more information, see Enabling Monitoring for Compute Instances.