On 05/03/11 10:03, Paul Gear wrote:
...
And some questions and related suggestions:
* When we ignore a port, does that prevent graphing and data collection on it, or just notification? I have a lot of edge switches for which i have no use of port up/down notifications, but if it is up, i would like to collect the interface stats. Perhaps the "ignore" tickbox needs to be split into "collect" and "notify"?Ignore still collects, but alarms and the like should ignore the device. Disabled disables polling.
That seems to work for devices, but not for ports - there's just ignore, and it seems to disable polling.
Hi Adam, Tom, and others,
I tried to get you guys on IRC today, but it seems you weren't around. I've created two patches for this. They were created against the svn trunk which was up-to-date as of about 02:00 UTC today. (I hope they meet your coding standards; cut & paste coding is my speciality. ;-) )
* http://gear.dyndns.org/~paulgear/patches/observium-port-disable.patch This adds the concept of disabled ports as well as ignored. Disabling disables polling, ignoring disables notifications. I plan to use this on all my edge switches which connect end-user devices which are often turned off overnight or rebooted during the day. I still want to collect data when they up, but i don't care if they're down. * http://gear.dyndns.org/~paulgear/patches/observium-port-outofsync.patch This one changes the outofsync status (red colour) to check both the ignore and disabled flags on a port, instead of just the ignored status. Apply after observium-port-disable.patch.
There are a couple of things that my patches don't handle:
* Update of the database schema: i couldn't work out how to trigger this except by changing the static config file that said not to touch anything below the comment line. * Distinguishing between administratively down (/ports/admindown/) which is called "disabled" in the ports menu, and disabled from my patches' perspective, which means to disable polling.
Any feedback appreciated.
Regards, Paul