I recently (2 days ago) installed a new server in a datacenter and wanted to try out the new remote agent feature in the current beta version of Dude 3.0Beta4.
I configured the main server (in my office) to probe about 15 remote devices using the Dude agent server in the new datacenter. Today, after about 1 day of successful operation, all probed devices setup to be probed from the remote agent went down. I tested connections that went down, and I could sucessfully use each probe dude said was down. I checked the remote dude server to see if it was still up, I could remote desktop into it and the Dude server was still running; It was successfully probing devices.
After changing the probe agent on my main server (in the office) the devices came back to life.
This seems to be a bug in the new version.
Also a few feature requests:
- It would be nice to be able to select a group of devices and change common settings.
- Group devices for configuration purpose, to be able to push out a settings change all at once (like the default SNMP probe type)
- Centralize the Server-Agent system so that all dude settings can be centralized and probed devices can be shared between computer. Implement fail-over procedures and redundancy to the monitoring system.
- Server rules to have servers operate in a group mode and dynamically switch to operate independantly, then back again, with syc features and handshake protocols.