Have any of you setup a fully redundant monitoring & alerting infrastructure? I'm not talking about the "hot-standby" setup either. I'm trying to figure out the best way to setup our Orion environment so that it's fully redundant. This means most likely that we will have a 2nd instance of Orion at a different geographical location, pointing to it's own database. But, the problem with this is you get dual alerts etc. So right now I'm stuck. I'm trying to get creative to solve this problem but everything I have come up with so far has some sort of draw back attached to it. We also own the Orion App monitor, so maybe that could be used to help this process somehow? Maybe have server #2 monitor the Orion services on server #1 and, in the event of any services failing, could start those services on server #2?
Any of you doing anything similar out there?
Thanks in advance!
Steve