Alarm definition
When onboarding your alarms to AWS Incident Detection and Response, you're responsible for defining the metrics and alarm configurations that provide visibility into the performance of your applications. As part of this process, you must also identify the teams within your organization who is responsible for responding to these alarms.
When preparing alarms, we recommend the following best practices:
Alarms only enter the "Alarm" state when there is ongoing critical impact to your monitored workload that requires immediate attention from your team and AWS. Alarms that trigger and don't automatically recover require your teams to join an incident bridge with AWS Incident Detection and Response.
Ensure the contact information you provide allows AWS Incident Detection and Response to reliably engage the appropriate teams within your organization to an incident bridge 24/7.
Key outputs
A list of alarms and contact details, which you provide to AWS Incident Detection and Response using the IDR CLI
.
For more information about defining and ingesting Amazon CloudWatch alarms see Ingesting CloudWatch alarms.
For more information about ingesting third party Application Performance Monitoring alarms see Ingesting Third Party Application Performance Monitoring Alarms.