On Tue, 2010-06-22 at 21:40 +1000, Nathan Scott wrote:
> ...
> > Also in the filesys/summary group we're logging
> > filesys.full
> > filesys.used
> > filesys.free
> > filesys.avail # for Linux
> >
> > which seems a bit over the top ... I'd guess that the only
> > information
> > really worth logging in a summary group ("on" for everyone by
> > default)
> > would be filesys.full ... so we can either trim the filesys/summary
>
> Hmm, not so sure ... full (percentage) is not as useful as having
> capacity and space used - capacity can be logged infrequently (perhaps
> once a day), and with those two we can calculate full (%) and free.
filesys.capcity is already being logged once (in the platform/hinv
group), which is effectively daily when using the cron-based log
rotation scripts.
After that, I think it is a a three-way nil-all tie in trying to pick
between full, used and free (the difference between free and avail is
not sufficiently interesting to warrant considering avail). Given any
one of these three the others can be calculated, given capacity.
|