Has anyone had success with F5 pool-specific alerts.
Yes.Our basic trigger looks like this:
We have it set to 30m as we are primarily a network team and we only monitor/alert on network kit. The theory here is that the pool or pool member is a server in its own right and thus any primary alerts should be to the team responsible for that. This is very much a backup for our benefit for when the client inevitably says "the network is down" when in reality it's one server in a pool.I say this is our basic alert as we also have other triggers based on custom properties which check the node (the F5 in this case) is in BAU and is it a specific (aka overly paranoid) client.BTW: The "F5 LTM Pool" could be changed to Server or PoolMember.
