wademn ✭✭✭✭✭

Agree - yes please!

I would like to echo the sentiments of the original post 100%. I would also like to echo Peter's comments with regard to trap retention. I've had to do a lot of work putting rules into place to ignore traps and reduce retention to 7 days at the request of support so that the product would work. It would be VERY beneficial…

Chris, I believe outsidesys has stated the requirements very well. This is a very big issue for my organization as well. The alert variables available for trap actions are very limited and the ones that are available are not very useful. The ability to parse out the varbinds from the trap for the various actions would be…

Funny - I think I posted basically the same feature enhancement request today. It's nice to know that others are looking for the same functionality:

Yes, I believe this happens when the application is patched/upgraded. However, as far as I know, these changes to the MIB DB are not documented or communicated in any way. Short of testing every DB rule that I have (150+), how am I supposed to know if an upgrade will break any of my trap rules?

Thank you for the reply. We do have APM but I don't believe it will work for my needs since the devices I'm querying are not servers. I was hoping to be able to run the script on the poller, not on the managed node. We currently do this with What's Up Gold but I'm trying to find a way to migrate this functionality to Orion.

I have the same question. I have two identical sensors with (apparently) different thresholds. One has a temp of 95 and is currently critical. The other is 111 and the status is OK. I understand that I can override the defaults but I'd really like to know what the defaults are so I can make adjustments before they alert.