I think there should be an option for NCM to unmanage or mute alerts on a node when your scheduling a job via NCM. ie: if you have a job that is upgrading or rebooting a number of switches, rather than having to go in separately and unmanage or mute the nodes, NCM should have the ability to do this. Not only will it make everyone's lives easier, but let's say you think your reboots are going to happen between 6 and 8pm based on the number of nodes you have. So, you schedule your reboots and go schedule an unmanage for that time frame. That means every node is unmanaged for the full 2 hours, even though each node might only be affected for 5 minutes or something? Or what if the job takes much longer to execute? All of a sudden you start getting alerts for nodes that go down after the timeframe you planned.
In thinking about it, it would probably be good to say "unmanage when operating on this node" with the option of doing it for X minutes. So if node # 200 kicks off at 7:20 PM, that node would get unmanaged from 7:20 to 7:25. A killer option might be to unmanage it until it starts responding again, which would mean Orion would poll it, but ignore the poll results until the node was met the "up" criteria for the node?
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community.
More than 150,000 members are here to solve problems, share technology and best practices, and directly
contribute to our product development process.