svindle

Agree, similar is not the same; However, I'm not using custom UnDP's for this, I'm using the in-built UPS poller. It works if I delete an affected node and then add it back, but then I have to rebuild dependencies and fill out custom properties, and doing that en-masse is prohibitively time consuming.

Similar. APC Smart-UPS X 2200 is the old, APC Smart-UPS 2200 is the new.

This did not help.

This was the correct answer. Upgraded to 2020.2.6, and that brought along the fields we needed. Thanks for pointing me in the right direction!

So that looks like exactly what I need...However, I'm missing the Syslog HOSTNAME and Syslog ORIGINAL ADDRESS field options?

I tried a couple different variables: * Critical Value - ${N=SwisEntity;M=InPercentUtilizationThreshold.Level2Value}* Turned into '90', the default value instead of the current dynamic value * Formula - ${N=SwisEntity;M=InPercentUtilizationThreshold.Level2Formula}* Turned into ${USE_BASELINE_CRITICAL}

Good call! I had been quite interested in the perfstack features but was struggling to find a use for them. I'm not in the office right now so I can't check, but can you build a perfstack...project, I guess they're called, into a view?

D09h - Thanks for finding that, but that's not quite what I'm posting about. We've already figured out that muting an alert doesn't stop the 'repeat' actions once an alert has already been triggered What I'm seeing is that these node down alerts appear to be ignoring the 'mute alerts' flag altogether. I'll mute one of…

Yes, I have the dependency chains set up; The problem is, they only seem to work correctly if a device further it up the chain is detected down. The complaint is that our techs don't want to have to mute alerts on every node in the chain - WhatsUP Gold would allow us to mute the device at the top of the chain (or just…

We have experienced the same issue. In our case, I think it might be that we muted the alerts on a node that had already sent it's 'Hey i'm down' notification. In our setup, that alert has a few escalations before it hits a recurring 60-minute reminder. We did wind up unmanaging the node to hush the alert.