Re:Setup AWS Cloudwatch Monitoring and Alerts Using Bash Scr...
by sks147 on Sunday June 27, 2021 @11:12PM
(#27657702)
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.
Re:Setup AWS Cloudwatch Monitoring and Alerts Using Bash Scr...
by mulmen on Monday June 28, 2021 @01:38AM
(#27658469)
What do you do with the Slack messages?
Re:Setup AWS Cloudwatch Monitoring and Alerts Using Bash Scr...
by vergessenmir on Sunday June 27, 2021 @04:10PM
(#27654842)
Custom Cloudwatch metrics are expensive to write to making them useful for coarse grained high level service metrics. If you can afford it go ahead but setting up some other cloud native monitoring service may be the way to go.
Re:Setup AWS Cloudwatch Monitoring and Alerts Using Bash Scr...
by jeppesen-io on Sunday June 27, 2021 @08:33PM
(#27656838)
Certainly not perfect, but I've had very good success alerting load avg over 120 to 150 percent of core count
What's nice, is it catches A variety disk issues as well
I'm sure not perfect for all cases but for me, most of them
Re:Setup AWS Cloudwatch Monitoring and Alerts Using Bash Scr...
by dimitar on Sunday June 27, 2021 @04:10PM
(#27654843)
If you are running some software that requires an instance, but is in not expected to create load you can put it in a burstable, and setup such an alert, so you know when it is time to upgrade.
For the love of $DIETY, if you're going to set up CloudWatch monitoring, create custom metrics that map to your business outcomes and alert when those go off the rails.