Prior to NPM 12 upgrade, I set all my node down alerts to reset after the condition is no longer true. The trigger condition would be node equals down. I would then send a reset email that would have the state variable in the subject. It used to be that the reset would reset on Up, but now it's resetting with condition Warning, which isn't actually true (a continuous ping from solarwinds shows it is never responding to ping and is actually down). Then after the next check of the alert, it goes back to down. I haven't changed anything with my alerts between upgrades - is this a change in behavior of the alerts engine? Any thoughts on how to rewrite the alert if this is expected behavior now?
Screenshots of current example alert:
Do I need to change the reset condition to custom and reset when status is equal to up?
