Setup AWS Cloudwatch Monitoring and Alerts Using Bash Scripts

Post by mulmen » Mon, Jun 28, 2021, 5:38 AM UTC

sks147 wrote: post #31

coredog64 wrote: post #23

High CPU alerts are terrible alerts. If I'm paying per instance, I want CPU utilization to be high. If it's low, I'm wasting money. So now what I need is an alert where it's not high, but somewhere between "high and too high". You know, like when there's an arbitrary spike because the Java is doing some GC. Or you have a one minute spike of traffic that fires an Ops Genie alert at 2am but auto-clears between when the…

You might want to have two separate alerts for this problem, one labelled WARNING and the other CRITICAL, such as 60 percent CPU usage as a warning and 85 percent CPU usage as a critical situation. You can have two separate SNS Topics for warning and critical alerts. Warning alerts can be thrown to a slack channel and Critical alerts can be configured to invoke the Pager.

Post by orf » Mon, Jun 28, 2021, 10:09 AM UTC

sks147 wrote: post #30

orf wrote: post #2

Not sure why you’d ever do this instead of using terraform.

Until the team onboards a terraform expert, these scripts might be helpful and cheaper to implement.