NeophyteNeophyte
Server1 Server2
uy1 - dns1.us1.blah.com ab1 - dns3.us1.blah.com
uy1 - dns2.us1.blah.com ab1 - dns4.us1.blah.com
ar1 - dns1.us1.blah.com mn1 - dns3.us1.blah.com
ar1 - dns2.us1.blah.com mn1 - dns4.us1.blah.com
my1 - dns3.us1.blah.com bg2 - dns1.us1.blah.com
my1 - dns4.us1.blah.com bg2 - dns2.us1.blah.com
All instances return back a value for a query time (from Server1/2 to dns1/2/3/4.us1.blah.com.. whichever is in the name..)
All instances return back a value of 0 1 or 2 based on if they were able to query both servers.. so for example, if uy1 can't query either dns1 or dns2, that's a critcal because that site can't query either server.
So I see two possible groupings.. the sites (uy1, ar1, my1, ab1, mn1, bg2)
or the servers (dns1.us1.., dns2.us1.., dns3.us1.., dns4.us1..)
So instead of each of my instances having to do their own scripted checking in the background to check both servers, a grouped/cluster alert could alert if both instances are down.
And in the other case, if say dns1.us1.blah.com is down... I'd rather not get a page from
uy1, ar1, and bg2... just one page with a custom alert saying that uy1, ar1, and bg2 are unable to contact dns1.us1.blah.com (I envision this being possible by pulling instance properties)
example: uy1 - dns1.us1.blah.com would have instances properties of
site = uy1
dns = dns1.us1.blah.com
Flexibility in being able to customize alert messages for each cluster / groupped alert is a big one too !! Right now it's a standard template across the board 
