Our event log has been a great place to see:
However, we noticed that our binary state of
failed was not always communicating the whole picture.
Consider the case where a Rule to “Create Snapshots” targets 12 Volumes, however an error is returned from AWS on the 10th Volume. GorillaStack is built for optimistic execution and will continue to execute on the remaining 2 Volumes. When classifying the event for this Rule’s execution, it is incorrect to mark it as
succeeded and also not quite right to mark it as
failed (we historically did the latter regardless, being the “least wrong” state representation).
So, we have added another state
partially succeeded, to describe scenarios where some, but not all of the targeted resources were successfully actioned.
But this was not quite enough. We decided to build a mechanism such that users could subscribe to different events and have notifications delivered via Email or Slack.
You can now subscribe to
Partially Successful and/or
Failed Rule Action executions.