CloudConsole

CloudConsole · What changed?

What caused my AWS alarm? See what changed before it fired

Most alarms follow a change. Open an alarm in CloudConsole and “What changed?” lists the deploys and configuration changes from the hour before it fired, on one timeline, with the ones that touch the same resource marked “Likely related”.

What changed? timeline on an alarm: a GitHub deploy run and an ECS UpdateService marked likely related, before checkout-api-5xx fired

A deployment timeline for every alarm

Scroll down on any alarm to What changed?. It covers the 60 minutes before the alarm last went into ALARM up to now, newest first, with a marker at the moment it fired. If the alarm isn’t firing, it shows the last 3 hours. You don’t set anything up: it reads what AWS already records.

Where the changes come from

  • CloudTrail: write calls in the alarm’s region, such as UpdateService, PutParameter or ModifyDBInstance, without the noise of read calls and sign-ins.
  • CodePipeline runs that started or finished in the window.
  • CloudFormation stack updates.
  • ECS service deployments.
  • GitHub Actions runs on the repositories you watch, if you connect GitHub.

Correlate the alarm with the deploy

A change is marked Likely related when it names something from the alarm’s dimensions: the ECS service, Lambda function, target group or database the alarm watches. A deploy run, the UpdateService it made and the 5xx alarm that followed line up in one list, and a tap opens each one.

Works with the permissions you have

Each source loads on its own. If your role can’t read one, for example CloudTrail, that row says so and the rest still show. It needs read access such as cloudtrail:LookupEvents, and nothing is installed in your account. Viewing it is free; the app calls AWS and GitHub straight from your phone.

Questions

How do I find what caused a CloudWatch alarm?

Look at what changed shortly before it fired: deploys, configuration changes and stack updates. CloudTrail records API writes, and CodePipeline, CloudFormation and ECS keep their own histories. CloudConsole puts all of them on one timeline on the alarm screen, starting 60 minutes before the alarm fired.

Which changes does “What changed?” include?

CloudTrail write events in the alarm’s region, CodePipeline runs, CloudFormation stack updates, ECS service deployments, and GitHub Actions runs on your watched repositories if GitHub is connected.

What does “Likely related” mean?

The change names a resource from the alarm’s dimensions, such as the ECS service, function, target group or database it watches. It is a pointer for where to look first, not proof of cause.

Do I need to set anything up in AWS?

No. It reads CloudTrail event history and the services’ own records with your existing credentials. CloudTrail event history covers management events for the last 90 days without creating a trail.

Is it free?

Yes. Viewing alarms and their timeline is part of the free plan, which covers one AWS account, read-only. Pro, at £14.99 a month, adds changes and unlimited accounts.

Try CloudConsole

On the App Store for iPhone and Google Play for Android. Look around the demo, GitHub and Slack included, before connecting an account.