amazon web services - OpsWorks Stack - Load-based instances scaling UP and DOWN based on cloudwatch alarms -


we have opsworks stack 2 24x7 instances. 4 time-based instances. 2 load-based instances.

our issue load-based instances. we've spent great deal of time creating meaningful-to-our-service cloudwatch alarms. thus, want load-based instances in our stack come when particular cloudwatch latency alarm in alarm state. see in load-based instance configuration, can define cloudwatch alarm bringing instance(s) , can define cloudwatch alarm bringing instance(s) down.

thing is, when select specific cloudwatch alarm want use trigger up, removes cloudwatch alarm being selected trigger down. why?

specifically, want our latency alarm (we'll call "oh crap things slowing down" cloudwatch alarm) trigger load-based instances start when in alarm state. then, want "oh crap things slowing down" cloudwatch alarm trigger load-based instances shutdown when in ok state. rad if load-based instances waited 15 minutes after ok state of alarm before shutting down.

the "oh crap things slowing down" threshold latency > 2 3 minutes

do need create new "oh nice things ok" alarm threshold of latency < 2 3 minutes use down alarm in load-based instance configuration?

sorry newbie question, feel stuck.

from can tell, have add second alarm triggers when latency below 2 3 minutes. if else comes cleaner solution this, i'd love hear it. is, you'll have 1 of alerts in continuous state of alarm.


Comments

Popular posts from this blog

Ansible - ERROR! the field 'hosts' is required but was not set -

customize file_field button ruby on rails -

SoapUI on windows 10 - high DPI/4K scaling issue -