daveg123

As I posted in my first comment, yes, it was set to 'alert when All apply'. Maybe the order of the conditions is important? I tested using... node status is equal to Down node name is equal to MailServer ...and it definitely suppressed all alerts because I tested rebooting a few servers many times and got bubkis until I…

I don't think NPM possesses that type of logic. It simply sees that a node is down and asks if any of the conditions apply to it and then activates the trigger. It doesn't have the ability to see that a node is down and then ask if another node is Up before sending. What I've done is keep my simple alert which alerts me…

So, it turns out that I somehow got sidetracked from the KISS methodology and maybe was just fatigued. I set the primary alert to send all alerts to my primary SMTP server and a second to suppress alerts to my secondary SMTP if the primary is up. This seems to be working, although SolarWinds will be sending double alerts…

By setting a suppression condition, no alerts were sent at all. I did have the order of the conditions reversed from yours, but that is what I initially tried. I also tried 'Not Up' instead of Down and that didn't work. Once I removed the suppression alerts started again.