Find when an investigated CloudWatch alarm recovered
Open the CloudWatch investigation and inspect its Alert status. If the alarm fired again, check which episode each recovery belongs to.
Compare alarm episodes and close times#
A CloudWatch alarm investigation starts when its alarm enters ALARM. When the same alarm enters ALARM again in the environment at most 10 minutes after the investigation's own entry, and before the investigation has a result, that entry joins the investigation instead of opening another, so one investigation can cover several episodes. A later entry opens its own investigation. When entries have joined, Closes recorded says how many of the investigation's episodes, its own and each joined one, have a recorded close, such as 1 of 3 incidents, the same count as its row on the Investigations page. The page has no Alert incidents row for a CloudWatch alarm. Original incident then shows the state of the episode that started the investigation; its close does not mean that the joined episodes closed. With no joined entry, Alert shows that state. When Proofline records the alarm's return from ALARM to OK, from a forwarded alarm or from reading a watched alarm's history, Alert or Original incident shows Closed, the time CloudWatch gives for that return and how long the alarm was in ALARM. A return through INSUFFICIENT_DATA records no close. No close recorded means only that Proofline holds no return to OK for this episode. It does not mean that the alarm is still in ALARM, or say whether the service has recovered. A recorded close changes neither the investigation's conclusion nor its Slack message.
Some older CloudWatch investigations show no Alert, because Proofline did not track their episodes' closes.