docs.aws.amazon.com
Open in
urlscan Pro
65.9.66.93
Public Scan
URL:
https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Create_Composite_Alarm.html
Submission: On December 05 via api from DE — Scanned from DE
Submission: On December 05 via api from DE — Scanned from DE
Form analysis 0 forms found in the DOM
Text Content
SELECT YOUR COOKIE PREFERENCES
We use essential cookies and similar tools that are necessary to provide our
site and services. We use performance cookies to collect anonymous statistics so
we can understand how customers use our site and make improvements. Essential
cookies cannot be deactivated, but you can click “Customize cookies” to decline
performance cookies.
If you agree, AWS and approved third parties will also use cookies to provide
useful site features, remember your preferences, and display relevant content,
including relevant advertising. To continue without accepting these cookies,
click “Continue without accepting.” To make more detailed choices or learn more,
click “Customize cookies.”
Accept all cookiesContinue without acceptingCustomize cookies
CUSTOMIZE COOKIE PREFERENCES
We use cookies and similar tools (collectively, "cookies") for the following
purposes.
ESSENTIAL
Essential cookies are necessary to provide our site and services and cannot be
deactivated. They are usually set in response to your actions on the site, such
as setting your privacy preferences, signing in, or filling in forms.
PERFORMANCE
Performance cookies provide anonymous statistics about how customers navigate
our site so we can improve site experience and performance. Approved third
parties may perform analytics on our behalf, but they cannot use the data for
their own purposes.
Allow performance category
Allowed
FUNCTIONAL
Functional cookies help us provide useful site features, remember your
preferences, and display relevant content. Approved third parties may set these
cookies to provide certain site features. If you do not allow these cookies,
then some or all of these services may not function properly.
Allow functional category
Allowed
ADVERTISING
Advertising cookies may be set through our site by us or our advertising
partners and help us deliver relevant marketing content. If you do not allow
these cookies, you will experience less relevant advertising.
Allow advertising category
Allowed
Blocking some types of cookies may impact your experience of our sites. You may
review and change your choices at any time by clicking Cookie preferences in the
footer of this site. We and selected third-parties use cookies or similar
technologies as specified in the AWS Cookie Notice
.
CancelSave preferences
UNABLE TO SAVE COOKIE PREFERENCES
We will only store essential cookies at this time, because we were unable to
save your cookie preferences.
If you want to change your cookie preferences, try again later using the link in
the AWS console footer, or contact support if the problem persists.
Dismiss
Contact Us
English
Create an AWS Account
1. AWS
2. ...
3. Documentation
4. Amazon CloudWatch
5. User Guide
Feedback
Preferences
AMAZON CLOUDWATCH
USER GUIDE
* What is Amazon CloudWatch?
* How CloudWatch works
* Concepts
* Billing and cost
* Resources
* Getting set up
* Getting started
* See key metrics from all AWS services
* Focus on a single service
* Focus on a resource group
* Dashboards
* Create a dashboard
* CloudWatch cross-account observability dashboard
* Cross-account cross-Region dashboards
* Creating and working with widgets on CloudWatch dashboards
* Add or remove a graph
* Graph metrics manually on a CloudWatch dashboard
* Edit a graph
* Edit a graph
* Move or resize a graph
* Rename a graph
* Add an explorer widget to a CloudWatch dashboard
* Add or remove a line widget
* Add or remove a number widget
* Add or remove a gauge widget
* Add a custom widget to a CloudWatch dashboard
* Details about custom widgets
* Security and JavaScript
* Interactivity in the custom widget
* Create a custom widget
* Sample custom widgets
* Add or remove a text widget
* Add or remove an alarm widget
* Link and unlink graphs
* Sharing dashboards
* Use live data
* Viewing an animated dashboard
* Add a dashboard to your favorites list
* Change the period override setting or refresh interval
* Change the time range or time zone format
* Metrics
* Basic monitoring and detailed monitoring
* Query your metrics with CloudWatch Metrics Insights
* Build your queries
* Query components and syntax
* Reserved keywords
* Using Metrics Insights queries with metric math
* SQL inference
* Sample queries
* Metrics Insights limits
* Metrics Insights glossary
* Troubleshooting Metrics Insights
* Use metrics explorer to monitor resources by their tags and properties
* Using metric streams
* Setting up a metric stream
* Setting up a metric stream to an AWS service (data lake scenario)
* Setting up a metric stream to a third-party solution
* Statistics that can be streamed
* Metric stream operation and maintenance
* Monitoring your metric streams with CloudWatch metrics
* Trust between CloudWatch and Kinesis Data Firehose
* Metric streams output formats
* JSON format
* OpenTelemetry 0.7.0 format
* Translations with OpenTelemetry 0.7.0 format
* How to parse OpenTelemetry 0.7.0 messages
* Troubleshooting
* View available metrics
* Searching for available metrics
* Graphing metrics
* Graphing a metric
* Using dynamic labels
* Modifying the time range or time zone format for a graph
* Zooming in on a graph
* Modifying the y-axis for a graph
* Creating an alarm from a metric on a graph
* Using anomaly detection
* Using metric math
* Using search expressions in graphs
* Search expression syntax
* Search expression examples
* Creating a graph with a search expression
* Getting statistics for a metric
* CloudWatch statistics definitions
* Getting statistics for a specific resource
* Aggregating statistics across resources
* Aggregating statistics by Auto Scaling group
* Aggregating statistics by AMI
* Publishing custom metrics
* Alarms
* Setting up an SNS topic
* Create an alarm based on a static threshold
* Creating an alarm based on anomaly detection
* Creating an alarm based on a log group-metric filter
* Creating an alarm based on a metric math expression
* Creating a composite alarm
* Editing or deleting a CloudWatch alarm
* Creating a CPU usage alarm
* Creating a load balancer latency alarm
* Creating a storage throughput alarm
* Create alarms to stop, terminate, reboot, or recover an EC2 instance
* Creating a billing alarm
* Hiding Auto Scaling alarms
* Alarm events and EventBridge
* Application monitoring
* Using ServiceLens to monitor the health of your applications
* Deploying ServiceLens
* Deploying AWS X-Ray
* Integrating with CloudWatch Logs
* Enabling segment metrics from X-Ray
* Deploying the CloudWatch agent and the X-Ray daemon
* Deploying on Amazon ECS
* Deploying on Amazon EKS or Kubernetes
* Deploying on Amazon EC2
* Using the service map
* Using the resource health view
* ServiceLens troubleshooting
* Using Internet Monitor
* AWS Regions
* IAM policies
* Pricing
* Components
* Getting started
* Get started with the console
* Get started with the CLI
* Internet Monitor dashboard
* Tracking performance and availability
* Exploring historical data
* Insights to improve your network setup
* CloudWatch Logs and Metrics
* CloudWatch Logs Insights
* CloudWatch Contributor Insights
* CloudWatch Metrics
* EventBridge integration
* How Internet Monitor works
* Data protection and data privacy
* Quotas
* Using synthetic monitoring
* Required roles and permissions
* Required roles and permissions for users who manage CloudWatch
canaries
* Required roles and permissions for canaries
* Limiting a user to viewing specific canaries
* Creating a canary
* Using canary blueprints
* Using the CloudWatch Synthetics Recorder for Google Chrome
* Synthetics runtime versions
* Runtime versions using Node.js and Puppeteer
* Runtime versions using Python and Selenium Webdriver
* Writing a canary script
* Writing a Node.js canary script
* Writing a Python canary script
* Library functions available for canary scripts
* Library functions available for Node.js canary scripts
* Library functions available for Python canary scripts using
Selenium
* Scheduling canary runs using cron
* Groups
* Troubleshooting a failed canary
* Troubleshooting a canary on a VPC
* Sample code for canary scripts
* Canaries and X-Ray tracing
* Running a canary on a VPC
* Encrypting canary artifacts
* Viewing canary statistics and details
* CloudWatch metrics published by canaries
* Edit or delete a canary
* Start, stop, delete, or update runtime for multiple canaries
* Monitoring canary events with Amazon EventBridge
* Perform launches and A/B experiments with CloudWatch Evidently
* IAM policies to use Evidently
* Create projects, features, launches, and experiments
* Create a new project
* Use client-side evaluation - powered by AWS AppConfig
* Add a feature to a project
* Use segments to focus your audience
* Create a launch
* Create an experiment
* Manage features, launches, and experiments
* See the current evaluation rules and audience traffic for a feature
* Modify launch traffic
* Modify a launch's future steps
* Modify experiment traffic
* Stop a launch
* Stop an experiment
* Adding code to your application
* Project data storage
* How Evidently calculates results
* View launch results in the dashboard
* View experiment results in the dashboard
* How CloudWatch Evidently collects and stores data
* Using service-linked roles
* CloudWatch Evidently quotas
* Tutorial: A/B testing with the Evidently sample application
* Use CloudWatch RUM
* IAM policies to use CloudWatch RUM
* Set up an application to use CloudWatch RUM
* Step 1: Authorize your application to send data to AWS
* Step 2: Create an app monitor
* (Optional) Step 3: Manually modify the code snippet to configure the
CloudWatch RUM web client
* Step 4: Insert the code snippet into your application
* Step 5: Test your app monitor setup by generating user events
* Configuring the CloudWatch RUM web client
* Use page groups
* Specify custom metadata
* Send custom events
* Viewing the CloudWatch RUM dashboard
* How CloudWatch RUM sets Apdex scores
* CloudWatch metrics that you can collect with CloudWatch RUM
* Extended metrics that you can send to CloudWatch and CloudWatch
Evidently
* Set up extended metrics using the console
* Tutorial: create an extended metric and alarm it
* Data protection and data privacy with CloudWatch RUM
* Information collected by the CloudWatch RUM web client
* Route change timing for single-page applications
* Manage your applications that use CloudWatch RUM
* How do I find a code snippet that I've already generated?
* Edit your application
* Stop using CloudWatch RUM or delete an app monitor
* CloudWatch RUM quotas
* Troubleshooting
* Insights and operational visibility
* Using Container Insights
* Setting up Container Insights
* Setting up Container Insights on Amazon ECS
* Setting up Container Insights on Amazon ECS for cluster- and
service-level metrics
* Setting up Container Insights on Amazon ECS using AWS Distro for
OpenTelemetry
* Deploying the CloudWatch agent to collect EC2 instance-level
metrics on Amazon ECS
* Deploying the AWS Distro for OpenTelemetry to collect EC2
instance-level metrics on Amazon ECS clusters
* Set up Firelens to send logs to CloudWatch Logs
* Setting up Container Insights on Amazon EKS and Kubernetes
* Verify prerequisites
* Using the CloudWatch agent
* Quick Start setup for Container Insights on Amazon EKS and
Kubernetes
* Set up the CloudWatch agent to collect cluster metrics
* Using AWS Distro for OpenTelemetry
* Send logs to CloudWatch Logs
* Set up Fluent Bit as a DaemonSet to send logs to CloudWatch
Logs
* (Optional) Set up FluentD as a DaemonSet to send logs to
CloudWatch Logs
* (Optional) Set up Amazon EKS control plane logging
* (Optional) Enable App Mesh Envoy access logs
* (Optional) Enable the Use_Kubelet feature for large clusters
* Updating or deleting Container Insights on Amazon EKS and
Kubernetes
* Updating the CloudWatch agent container image
* Deleting the CloudWatch agent and FluentD for Container
Insights
* Viewing Container Insights metrics
* Metrics collected by Container Insights
* Amazon ECS Container Insights metrics
* Amazon EKS and Kubernetes Container Insights metrics
* Performance log reference
* Performance log events for Amazon ECS
* Performance log events for Amazon EKS and Kubernetes
* Relevant fields in performance log events for Amazon EKS and
Kubernetes
* Container Insights Prometheus metrics monitoring
* Set up and configure on Amazon ECS clusters
* Set up on Amazon ECS clusters
* Scraping additional Prometheus sources and importing those
metrics
* Detailed guide for autodiscovery on Amazon ECS clusters
* (Optional) Set up sample containerized Amazon ECS workloads for
Prometheus metric testing
* Sample App Mesh workload for Amazon ECS clusters
* Sample Java/JMX workload for Amazon ECS clusters
* Sample NGINX workload for Amazon ECS clusters
* Sample NGINX Plus workload for Amazon ECS clusters
* Tutorial for adding a new Prometheus scrape target: Memcached
on Amazon ECS
* Tutorial for scraping Redis Prometheus metrics on Amazon ECS
Fargate
* Set up and configure on Amazon EKS and Kubernetes clusters
* Set up on Amazon EKS and Kubernetes clusters
* Scraping additional Prometheus sources and importing those
metrics
* (Optional) Set up sample containerized Amazon EKS workloads
for Prometheus metric testing
* Set up AWS App Mesh sample workload for Amazon EKS and
Kubernetes
* Set up AWS App Mesh sample workload on an Amazon EKS
cluster with the EC2 launch type or a Kubernetes cluster
* Set up AWS App Mesh sample workload on an Amazon EKS
cluster with the Fargate launch type
* Set up NGINX with sample traffic on Amazon EKS and
Kubernetes
* Set up memcached with a metric exporter on Amazon EKS and
Kubernetes
* Set up Java/JMX sample workload on Amazon EKS and
Kubernetes
* Set up HAProxy with a metric exporter on Amazon EKS and
Kubernetes
* Tutorial for adding a new Prometheus scrape target: Redis
on Amazon EKS and Kubernetes clusters
* Prometheus metric type conversion by the CloudWatch Agent
* Prometheus metrics collected by the CloudWatch agent
* Viewing your Prometheus metrics
* Prometheus metrics troubleshooting
* Prometheus metrics troubleshooting on Amazon ECS
* Prometheus metrics troubleshooting on Amazon EKS and
Kubernetes clusters
* Integration with Application Insights
* See Amazon ECS lifecycle events within Container Insights
* Troubleshooting Container Insights
* Building your own CloudWatch agent Docker image
* Deploying other CloudWatch agent features in your containers
* Using Lambda Insights
* Getting started with Lambda Insights
* Available versions of the Lambda Insights extension
* x86-64 platforms
* ARM64 platforms
* Using the console to enable Lambda Insights on an existing Lambda
function
* Using the AWS CLI to enable Lambda Insights on an existing Lambda
function
* Using the AWS SAM CLI to enable Lambda Insights on an existing
Lambda function
* Using AWS CloudFormation to enable Lambda Insights on an existing
Lambda function
* Using the AWS CDK to enable Lambda Insights on an existing Lambda
function
* Using Serverless Framework to enable Lambda Insights on an existing
Lambda function
* Enabling Lambda Insights on a Lambda container image deployment
* Viewing your Lambda Insights metrics
* Integration with Application Insights
* Metrics collected by Lambda Insights
* Troubleshooting and known issues
* Example telemetry event
* Using Contributor Insights to analyze high-cardinality data
* Create a Contributor Insights rule
* Contributor Insights rule syntax
* Example rules
* Viewing Contributor Insights reports
* Graphing metrics generated by rules
* Using Contributor Insights built-in rules
* Detect common application problems with CloudWatch Application Insights
* What is Amazon CloudWatch Application Insights?
* How Application Insights works
* Get started
* Access CloudWatch Application Insights
* Prerequisites
* IAM policy
* Permissions for account-based application onboarding
* Set up, configure, and manage your application
* Console steps
* Command line steps
* Events and notifications
* Work with component configurations
* Template fragment
* Sections
* Example configurations for relevant services
* Amazon DynamoDB table
* Amazon EC2 Auto Scaling (ASG)
* Amazon EKS cluster
* Amazon Elastic Compute Cloud (EC2) instance
* Amazon Elastic Container Service (Amazon ECS)
* Amazon ECS services
* Amazon ECS tasks
* Amazon Elastic File System (Amazon EFS)
* Amazon FSx
* Amazon Relational Database Service (RDS) Aurora MySQL
* Amazon Relational Database Service (RDS) instance
* Amazon S3 bucket
* Amazon Simple Queue Service (SQS)
* Amazon SNS topic
* API Gateway REST API stages
* Application Elastic Load Balancing
* AWS Lambda Function
* AWS Step Functions
* Customer-grouped Amazon EC2 instances
* Elastic Load Balancing
* Java
* Kubernetes on Amazon EC2
* RDS MariaDB and RDS MySQL
* RDS Oracle
* RDS PostgreSQL
* SAP HANA on Amazon EC2
* SAP HANA High Availability on Amazon EC2
* SAP NetWeaver on Amazon EC2
* SAP NetWeaver High Availability on Amazon EC2
* SQL Always On Availability Group
* SQL failover cluster instance
* Use CloudFormation templates
* Tutorial: Set up monitoring for SAP HANA
* Tutorial: Set up monitoring for .NET and SQL
* View and troubleshoot Application Insights
* Supported logs and metrics
* Amazon Elastic Compute Cloud (EC2)
* Elastic Block Store (EBS)
* Amazon Elastic File System (Amazon EFS)
* Elastic Load Balancer (ELB)
* Application ELB
* Amazon EC2 Auto Scaling groups
* Amazon Simple Queue Server (SQS)
* Amazon Relational Database Service (RDS)
* AWS Lambda function
* Amazon DynamoDB table
* Amazon S3 bucket
* AWS Step Functions
* API Gateway REST API stages
* SAP HANA
* SAP NetWeaver
* HA Cluster
* Java
* Amazon Elastic Container Service (Amazon ECS)
* Kubernetes on AWS
* Amazon FSx
* Metrics with data points requirements
* Recommended metrics
* Performance Counter metrics
* CloudWatch cross-account observability
* Link monitoring accounts with source accounts
* Manage monitoring accounts and source accounts
* Collect metrics and logs with the CloudWatch agent
* Installing the CloudWatch agent
* Installing the CloudWatch agent using the command line
* Download and configure the CloudWatch agent
* Create IAM roles and users for use with CloudWatch agent
* Installing and running the CloudWatch agent on your servers
* Install the CloudWatch agent using Systems Manager
* Create IAM roles and users for use with the CloudWatch agent
* Download and configure the CloudWatch agent
* Installing the CloudWatch agent on EC2 instances
* Installing the CloudWatch agent on on-premises servers
* Installing the CloudWatch agent on new instances using AWS
CloudFormation
* Verifying the signature of the CloudWatch agent package
* Create the CloudWatch agent configuration file
* Create the CloudWatch agent configuration file with the wizard
* Manually create or edit the CloudWatch agent configuration file
* Collect network performance metrics
* Collect NVIDIA GPU metrics
* Collect process metrics with the procstat plugin
* Retrieve custom metrics with StatsD
* Retrieve custom metrics with collectd
* Set up and configure Prometheus metrics collection on Amazon EC2
instances
* Metrics collected by the CloudWatch agent
* OpenTelemetry support in the CloudWatch agent
* Common scenarios with the CloudWatch agent
* Troubleshooting the CloudWatch agent
* Ingest high-cardinality logs to generate metrics with CloudWatch embedded
metric format
* Generating logs using the embedded metric format
* Using the client libraries
* Using the embedded metric format with AWS Distro for OpenTelemetry
* Manually generating embedded metric format logs
* Specification: Embedded metric format
* Using the PutLogEvents API to send manually-created embedded metric
format logs
* Using the CloudWatch agent to send embedded metric format logs
* Viewing your metrics and logs in the console
* Services that publish CloudWatch metrics
* AWS usage metrics
* Visualizing your service quotas and setting alarms
* AWS API usage metrics
* CloudWatch usage metrics
* CloudWatch tutorials
* Scenario: Monitor estimated charges
* Scenario: Publish metrics
* Working with AWS SDKs
* Code examples
* Actions
* Create an alarm that watches a metric
* Delete alarms
* Describe alarm history
* Describe alarms
* Describe alarms for a metric
* Disable alarm actions
* Enable alarm actions
* Get dashboard details
* Get metric statistics
* List dashboards
* List metrics
* Put a set of data into a metric
* Put data into a metric
* Scenarios
* Get started with alarms
* Manage Amazon CloudWatch metrics and alarms
* Security
* Data protection
* Identity and access management
* CloudWatch dashboard permissions update
* Overview of managing access
* Using identity-based policies (IAM policies)
* Using condition keys to limit access to CloudWatch namespaces
* Using condition keys to limit Contributor Insights users' access to log
groups
* Using condition keys to limit alarm actions
* Using service-linked roles
* Using a service-linked role for Internet Monitor
* Using a service-linked role for CloudWatch RUM
* Using service-linked roles for Application Insights
* AWS managed policies for Application Insights
* Amazon CloudWatch permissions reference
* Compliance validation
* Resilience
* Infrastructure security
* Interface VPC endpoints
* Security considerations for Synthetics canaries
* Logging API calls with AWS CloudTrail
* Tagging your CloudWatch resources
* Grafana integration
* Cross-account cross-Region CloudWatch console
* Service quotas
* Document history
Creating a composite alarm - Amazon CloudWatch
AWSDocumentationAmazon CloudWatchUser Guide
Creating a composite alarm Composite alarm action suppression
CREATING A COMPOSITE ALARM
PDFRSS
Composite alarms determine their states by monitoring the states of other
alarms. You can use composite alarms to reduce alarm noise. For example, you can
create a composite alarm where the underlying metric alarms go into ALARM when
they meet specific conditions. You then can set up your composite alarm to go
into ALARM and send you notifications when the underlying metric alarms go into
ALARM by configuring the underlying metric alarms never to take actions.
Currently, composite alarms can take the following actions:
* Notify SNS topics
* Create OpsItems in AWS Systems Manager Ops Center
* Create incidents in AWS Systems Manager Incident Manager
If you are not using CloudWatch cross-account observability, the composite alarm
can monitor alarms in the current account.
Note
All of the underlying alarms in your composite alarm must be in the same account
and the same Region as your composite alarm. However, if you set up a composite
alarm in a CloudWatch cross-account observability monitoring account, the
underlying alarms can watch metrics in different source accounts and in the
monitoring account itself. For more information, see CloudWatch cross-account
observability.
A single composite alarm can monitor 100 underlying alarms, and 150 composite
alarms can monitor a single underlying alarm.
Rule expressions
All composite alarms contain rule expressions. Rule expressions tell composite
alarms which other alarms to monitor and determine their states from. Rule
expressions can refer to metric alarms and composite alarms. When you reference
an alarm in a rule expression, you designate a function to the alarm that
determines which of the following three states the alarm will be in:
* ALARM
ALARM ("alarm-name or alarm-ARN") is TRUE if the alarm is in ALARM.
* OK
OK ("alarm-name or alarm-ARN") is TRUE if the alarm is in ALARM.
* INSUFFICIENT_DATA
INSUFFICIENT_DATA (“alarm-name or alarm-ARN") is TRUE if the named alarm is
in INSUFFICIENT_DATA.
Note
TRUE always evaluates to TRUE, and FALSE always evaluates to FALSE.
Example expressions
The request parameter AlarmRule supports the use of the logical operators AND,
OR, and NOT, so you can combine multiple functions into a single expressions.
The following example expressions show how you can configure the underlying
alarms in your composite alarm:
* ALARM(CPUUtilizationTooHigh) AND ALARM(DiskReadOpsTooHigh)
The expression specifies that the composite alarm goes into ALARM only if
CPUUtilizationTooHigh and DiskReadOpsTooHigh are in ALARM.
* ALARM(CPUUtilizationTooHigh) AND NOT ALARM(DeploymentInProgress)
The expression specifies that the composite alarm goes into ALARM if
CPUUtilizationTooHigh is in ALARM and DeploymentInProgress is not in ALARM.
This is an example of a composite alarm that reduces alarm noise during a
deployment window.
* (ALARM(CPUUtilizationTooHigh) OR ALARM(DiskReadOpsTooHigh)) AND
OK(NetworkOutTooHigh)
The expression specifies that the composite alarm goes into ALARM if
(ALARM(CPUUtilizationTooHigh) or (DiskReadOpsTooHigh) is in ALARM and
(NetworkOutTooHigh) is in OK. This is an example of a composite alarm that
reduces alarm noise by not sending you notifications when either of the
underlying alarms aren’t in ALARM while a network issue is occurring.
CREATING A COMPOSITE ALARM
To create a composite alarm
1. Open the CloudWatch console at https://console.aws.amazon.com/cloudwatch/.
2. In the navigation pane, choose Alarms, and then choose In alarm.
3. From the list of alarms, select the check box next to each of the existing
alarms that you want to reference in your rule expression, and then choose
Create composite alarm.
4. Under Specify composite alarm conditions, specify the rule expression for
your new composite alarm.
Note
Automatically, the alarms that you selected from the list of alarms are
listed in the Conditions box. By default, the ALARM function has been
designated to each of your alarms, and each of your alarms is joined by the
logical operator OR.
You can use the following substeps to modify your rule expression:
1. You can change the required state for each of your alarms from ALARM to
OK or INSUFFICENT_DATA.
2. You can change the logical operator in your rule expression from OR to
AND or NOT, and you can add parentheses to group your functions.
3. You can include other alarms in your rule expression or delete alarms
from your rule expression.
Example: Rule expression with conditions
(ALARM("CPUUtilizationTooHigh") OR
ALARM("DiskReadOpsTooHigh")) AND
OK("NetworkOutTooHigh")
In the example rule expression where the composite alarm goes into ALARM
when ALARM ("CPUUtilizationTooHigh" or ALARM("DiskReadOpsTooHigh") is in
ALARM at the same time as OK("NetworkOutTooHigh") is in OK.
5. When finished, choose Next.
6. Under Configure actions, you can choose from the following:
For Notification
* Select an exisiting SNS topic, Create a new SNS topic, or Use a topic
ARN to define the SNS topic that will receive the notification.
* Add notification, so your alarm can send multiple notifications for the
same alarm state or different alarm states.
* Remove to stop your alarm from sending notifications or taking actions.
For Systems Manager action
* Add Systems Manager action, so your alarm can perform an SSM action when
it goes into ALARM.
To learn more about Systems Manager actions, see Configuring CloudWatch to
create OpsItems from alarms in the AWS Systems Manager User Guide and
Incident creation in the Incident Manager User Guide. To create an alarm
that performs an SSM Incident Manager action, you must have the correct
permissions. For more information, see Identity-based policy examples for
AWS Systems Manager Incident Manager in the Incident Manager User Guide.
7. When finished, choose Next.
8. Under Add name and description, enter an alarm name and optional
description for your new composite alarm. Your alarm name must contain only
ASCII characters.
9. When finished, choose Next.
10. Under Preview and create, confirm your information, and then choose Create
composite alarm.
Note
You can create a cycle of composite alarms, where one composite alarm and
another composite alarm depend on each other. If you find yourself in this
scenario, your composite alarms stop being evaluated, and you can't delete
your composite alarms because they're dependent on each other. The easiest
way to break the cycle of dependecy between your composite alarms is to
change the function AlarmRule in one of your composite alarms to False.
COMPOSITE ALARM ACTION SUPPRESSION
With composite alarm action suppression, you define alarms as suppressor alarms.
Suppressor alarms prevent composite alarms from taking actions. For example, you
can specify a suppressor alarm that represents the status of a supporting
resource. If the supporting resource is down, the suppressor alarm prevents the
composite alarm from sending notifications. Composite alarm action suppression
helps you reduce alarm noise, so you spend less time managing your alarms and
more time focusing on your operations.
You specify suppressor alarms when you configure composite alarms. Any alarm can
function as a suppressor alarm. When a suppressor alarm changes states from OK
to ALARM, its composite alarm stops taking actions. When a suppressor alarm
changes states from ALARM to OK, its composite alarm resumes taking actions.
WAITPERIOD AND EXTENSIONPERIOD
When you specify a suppressor alarm, you set the parameters WaitPeriod and
ExtensionPeriod. These parameters prevent composite alarms from taking actions
unexpectedly while suppressor alarms change states. Use WaitPeriod to compensate
for any delays that can occur when a suppressor alarm changes from OK to ALARM.
For example, if a suppressor alarm changes from OK to ALARM within 60 seconds,
set WaitPeriod to 60 seconds.
In the image, the composite alarm changes from OK to ALARM at t2. A WaitPeriod
starts at t2 and ends at t8. This gives the suppressor alarm time to change
states from OK to ALARM at t4 before it suppresses the composite alarm's actions
when the WaitPeriod expires at t8.
Use ExtensionPeriod to compensate for any delays that can occur when a composite
alarm changes to OK following a suppressor alarm changing to OK. For example, if
a composite alarm changes to OK within 60 seconds of a suppressor alarm changing
to OK, set ExtensionPeriod to 60 seconds.
In the image, the suppressor alarm changes from ALARM to OK at t2. An
ExtensionPeriod starts at t2 and ends at t8. This gives the composite alarm time
to change from ALARM to OK before the ExtensionPeriod expires at t8.
Composite alarms don't take actions when WaitPeriod and ExtensionPeriod become
active. Composite alarms take actions that are based on their currents states
when ExtensionPeriod and WaitPeriod become inactive. We recommended that you set
the value for each parameter to 60 seconds, as CloudWatch evaluates metric
alarms every minute. You can set the parameters to any integer in seconds.
The following examples describe in more detail how WaitPeriod and
ExtensionPeriod prevent composite alarms from taking actions unexpectedly.
Note
In the following examples, WaitPeriod is configured as 2 time units, and
ExtensionPeriod is configured as 3 time units.
EXAMPLES
Example 1: Actions are not suppressed after WaitPeriod
In the image, the composite alarm changes states from OK to ALARM at t2. A
WaitPeriod starts at t2 and ends at t4, so it can prevent the composite alarm
from taking actions. After the WaitPeriod expires at t4, the composite alarm
takes its actions because the suppressor alarm is still in OK.
Example 2: Actions are suppressed by alarm before WaitPeriod expires
In the image, the composite alarm changes states from OK to ALARM at t2. A
WaitPeriod starts at t2 and ends at t4. This gives the suppressor alarm time to
change states from OK to ALARM at t3. Because the suppressor alarm changes
states from OK to ALARM at t3, the WaitPeriod that started at t2 is discarded,
and the suppressor alarm now stops the composite alarm from taking actions.
Example 3: State transition when actions are suppressed by WaitPeriod
In the image, the composite alarm changes states from OK to ALARM at t2. A
WaitPeriod starts at t2 and ends at t4. This gives the suppressor alarm time to
change states. The composite alarm changes back to OK at t3, so the WaitPeriod
that started at t2 is discarded. A new WaitPeriod starts at t3 and ends at t5.
After the new WaitPeriod expires at t5, the composite alarm takes its actions.
Example 4: State transition when actions are suppressed by alarm
In the image, the composite alarm changes states from OK to ALARM at t2. The
suppressor alarm is already in ALARM. The suppressor alarm stops the composite
alarm from taking actions.
Example 5: Actions are not suppressed after ExtensionPeriod
In the image, the composite alarm changes states from OK to ALARM at t2. A
WaitPeriod starts at t2 and ends at t4. This gives the suppressor alarm time to
change states from OK to ALARM at t3 before it suppresses the composite alarm's
actions until t6. Because the suppressor alarm changes states from OK to ALARM
at t3, the WaitPeriod that started at t2 is discarded. At t6, the suppressor
alarm changes to OK. An ExtensionPeriod starts at t6 and ends at t9. After the
ExtensionPeriod expires, the composite alarm takes its actions.
Example 6: State transition when actions are suppressed by ExtensionPeriod
In the image, the composite alarm changes states from OK to ALARM at t2. A
WaitPeriod starts at t2 and ends at t4. This gives the suppressor alarm time to
change states from OK to ALARM at t3 before it suppresses the composite alarm's
actions until t6. Because the suppressor alarm changes states from OK to ALARM
at t3, the WaitPeriod that started at t2 is discarded. At t6, the suppressor
alarm changes back to OK. An ExtensionPeriod starts at t6 and ends at t8. When
the composite alarm changes back to OK at t7, the ExtensionPeriod is discarded,
and a new WaitPeriod starts at t7 and ends at t9. After the new WaitPeriod
expires, the composite alarm can take its actions.
Tip
If you replace the action suppressor alarm, any active WaitPeriod or
ExtensionPeriod is discarded.
Javascript is disabled or is unavailable in your browser.
To use the Amazon Web Services Documentation, Javascript must be enabled. Please
refer to your browser's Help pages for instructions.
Document Conventions
Creating an alarm based on a metric math expression
Editing or deleting a CloudWatch alarm
Did this page help you? - Yes
Thanks for letting us know we're doing a good job!
If you've got a moment, please tell us what we did right so we can do more of
it.
Did this page help you? - No
Thanks for letting us know this page needs work. We're sorry we let you down.
If you've got a moment, please tell us how we can make the documentation better.
Did this page help you?
Yes
No
Provide feedback
Edit this page on GitHub
Next topic:Editing or deleting a CloudWatch alarm
Previous topic:Creating an alarm based on a metric math expression
Need help?
* Try AWS re:Post
* Connect with an AWS IQ expert
PrivacySite termsCookie preferences
© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved.
On this page
--------------------------------------------------------------------------------
* Creating a composite alarm
* Composite alarm action suppression
DID THIS PAGE HELP YOU? - NO
Thanks for letting us know this page needs work. We're sorry we let you down.
If you've got a moment, please tell us how we can make the documentation better.
Feedback