AWS Systems Manager Incident Manager now identifies probable root causes of incidents
Starting today, customers can identify probable root causes of incidents in Incident Manager, a capability of AWS Systems Manager. When an alarm or event triggers an incident, Incident Manager now identifies recent AWS CloudFormation and AWS CodeDeploy deployments that included the affected resource and likely caused the incident. Incident responders will see deployment details and a direct link to the deployment, accelerating root cause diagnosis and reducing mean time to resolution (MTTR).
Starting today, customers can identify probable root causes of incidents in Incident Manager, a capability of AWS Systems Manager. When an alarm or event triggers an incident, Incident Manager now identifies recent AWS CloudFormation and AWS CodeDeploy deployments that included the affected resource and likely caused the incident. Incident responders will see deployment details and a direct link to the deployment, accelerating root cause diagnosis and reducing mean time to resolution (MTTR).
Changes to infrastructure and application code are among the most common causes of application availability and performance issues. This launch provides incident responders with the critical information they need to investigate likely root causes. For example, a CloudFormation stack update that reduced the memory allocated to a business critical Lambda function could cause invocation errors, triggering Incident Manager to engage an on-call engineer. Now, the root cause stack update will be highlighted in the incident and the on-call engineer can quickly investigate and resolve the issue.
This feature is available to Incident Manager customers at no additional cost. To learn more about Incident Manager, refer to the product page. To get started with the new feature, refer to the documentation. For Incident Manager pricing, see the pricing page. To view the regions where Incident Manager is available, see Incident Manager endpoints and quotas.