Currently I use Dude to monitor about hundered devices. Almost all of them have one or more important services and someone must be notified in case they fail. But it already happened few times that service died and no one was notified, because someone else either forgot to enable notification for that service or disabled it by accident. It wasn’t Dude’s fault, obviously. But if I wanted to verify current notifications settings, I’d have to go to Services list and then open about two hundered dialog windows one by one to check current settings. Or if I wanted to add some new notification type to several devices, it would be the same thing.
My suggestion is to include notifications in Services list. Either show them all, one column for each notification type, which I’d like best (first picture). Or if theoretically unlimited number of columns would be problematic, then show just one column and add combobox to select which notification it represents (second picture). Even the single column solution would be huge time saver.
I like the idea but remember that if you don’t specify a notification on the device(leave it unchecked) and have a global notification configured you will get a notification.
There are some issues here I have noticed, for one, when I specified a popup I stopped getting an email even though “notificiation” and “popup” were enabled globally, there must be others.
I do have some devices configured with specific notifications but try to keep it all coming from global.
Lebowski
Global notifications are not very useful for me. I monitor services with very different importance levels and they need different notifications. Sms for critical ones, e-mail for less important ones or nothing for things like cpu or memory snmp monitoring (with few exceptions those are only useful for me for historical overview and if they go down sometimes - and they do - it’s not a problem). On top of that, there are different people who need to be notified about different things and don’t care about others. So global “one settings fits all” just won’t do. Per-service notifications are perfect, but to set them up correctly takes too much work currently.
