Created
June 5, 2018 19:52
-
-
Save openfly/d05f626d52e3d43f95625cc1ce221872 to your computer and use it in GitHub Desktop.
AWS Lying their faces off.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Hello again, thanks for getting back in touch! | |
| Given that there was a datapoint where the "StatusCheckFailed_System" was 1.0, please assume from this that there was an issue with the underlying host during this timeframe. Because the issue occurs at a hypervisor level, it is transparent to the instance's operating system - meaning that there would be no logs for it on the OS. | |
| With regard to raising an alert for future occurrences, please consider the solution I have provided in my previous correspondence where you can configure CloudWatch Alarms to monitor the "StatusCheckFailure" metric and send an email notification to a desired email address if the alarm is triggered [1]. | |
| I hope this answers your query and should you have further questions regarding this matter, please do not hesitate in responding to this case and we will be happy to help you. | |
| [1] Create Alarms to Stop, Terminate, Reboot, or Recover an Instance | |
| - http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/UsingAlarmActions.html | |
| Best regards, | |
| David M. | |
| Amazon Web Services |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment