Anyone got a way that seems to work. Still scratching my head. We need to touch base with customers when we didn't plan a reboot.
Anyone got a way that seems to work. Still scratching my head. We need to touch base with customers when we didn't plan a reboot.
Just a thought here, but:
Would it not be possible to just use an email alert to notify you of reboots and then you have a list in your email of customers that you need to get back to? If you have a ticketing system you could have Orion open tickets in your ticketing system also for this.
As far as your alert that isn't working is concerned, if you could post a screen shot of it I am sure somebody could help you resolve the problem you are having with it.
Hrm... okay, back to the ole drawing board...
In your Events view you can filter on only Node Rebooted events, will this satisfy your requriement?
The problem with using the All Triggered Alerts element for this is that it's designed to inform you of all "Active" alerts. Nodes rebooting is something that happens and then is done and therefore no longer active.
At one point I suggested to SolarWinds that they create a consolidated "Alarm" view which would basically be a view of all things that I care to know about. Then in every sub-subsystem I would have an Alert Action option to send an Alarm into my Alarm view. It would support the ability to acknowledge the alarms as well as write notes on them. I think this would also be a good feature to satisfy your needs.
I managed our NOC here for several years so I understand the desire to do everything via a NMS dashboard.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.