On 04/03/11 19:39, Adam Armstrong wrote:
...
Whichever bits you'd like to improve. There are things that need
done just about everywhere. It's a good idea to be present in our
IRC channel when doing work, so that you can communicate with
other devs and users.
We've some philisophical ideas about how things should be done
that might not match with what you want to do, so always best to
check first :)
I will try to catch up with you guys on IRC as soon as i have a few
spare hours. :-)
Also, we prefer to take patches via IRC, as svn-diffs hosted on a
www somewhere.
I'm fast losing my svn-fu after switching my personal stuff to git,
but hopefully i'll be able to work this out with a bit of prodding.
...
- The global storage screen (health/storage/nographs/) would
make a lot more sense to me if the size of the area which
was shaded was relative to the size of the storage. Making
the width of the gauge grow on a logarithmic scale would
make sense to me.
Well, how do you scale that so it stays relevant? In 5 years time
we'll all have disks 10 times the size, etc, etc.
My idea was that the entire width would be used to show the largest
figure in the system and everything would just be scaled
logarithmically between that and the smallest one (at, say, 10
pixels wide).
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.
Paul