This is causing problems in our testsuite, because the lambda is not distinguishing between status == firing and status == resolved and if the endpoint group already contains both sites it kills one of them also on resolved event. The test suite then leaves the global accelerator in one site-only state.
With the current implementation of lambda and alert firing the lambda is executed 4 times.
Each site with firing event when the
vendor_jgroups_site_view_status
metric decreases to 0 from each site.Each site when the alert is resolved.
Here is an example for two payloads for each: Firing:
resolved:
This is causing problems in our testsuite, because the lambda is not distinguishing between
status == firing
andstatus == resolved
and if the endpoint group already contains both sites it kills one of them also on resolved event. The test suite then leaves the global accelerator in one site-only state.