Allow for escalation chain stages to start another chain.

Below is a specific use-case, yet this could be applied in many situations.

I have a set of database admins who want to be alerted when any event happens on the production database cluster, yet they shouldn\'t be alerted on events that don\'t relate to the database servers. I also have a critical alert chain that is getting rather complex and should be a catch-all to alert my server team for all critical events. With the current manner that alerting is implemented I would have to add all of the logic of my catch-all critical chain to the database team\'s rule as the service only follows one rule and then stops. This is going to quickly become too complex and rather unmanageable.

My idea is that alert rules would allow for a manner in which to hit multiple alert chains, therefore if a rule is hit will have the ability to follow multiple chains of action to be sure that I am hitting both the smaller subset of database admins as well as my team who generally see all alerts from all systems.