-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add alarms for UIs being unavailable. #497
Conversation
Will notifiy SNS when the public UI or authenticated UI are unavailable.
155a7cb
to
1cc06a1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎵 Du dud dud udu duuu dudud du dudu dudu dud uduu 🎵 CircleCI caught that we need to add permissions to the deployer for |
Route53 health checks are used to monitor the system; this PR allows the CircleCI deployer to add, remove, modify, list them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"the system is down..."
The previous descriptions were not helpful across environments.
Okay, finally got this sorted out — the timeframe for alarms must be 60 seconds or longer for AWS metrics, and I tweaked the alarm name after seeing them in the console, as the alarm dashboard didn’t indicate which environment the alarms are attached to. This is ready for final review/merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mmarcotte, I recommend you accept this PR into the court environments. Thanks!
To achieve part of #250, this will notify SNS when the public UI or authenticated UI are unavailable. Subscriptions for alertees can be manually managed through the AWS console.
staging
AWS account already to test.develop
to test in that environment, but I think thedevelop
environment hasn’t been fixed since blue/green deployments were introduced. I’ll take a look in the morning, but here’s the diff for review in the meantime!