> ++ 20/01/03 13:00 +0100 - Edwin Eefting:
> >I'm currently thinking of a new way to do performance data gathering with
> >nagios and rrdtool. (to create those nice graphs
> >
> > [...]
> >
> >DISK OK - [1000000 kB (10%) free on /dev/sda1]
> >curr=9000000,max=10000000
> >
> >So we add a new line with performance data thats easy to interpret and is
> >formatted in a generic way. So "curr" is always the current value of
> >a service, and "max" always will be the maximum value.
> >
> >What do you think of this? Any suggestions for this system, or should we
> >just do it and submit our patches?
>
> I'm 100% for it. I beleive that lots of people have already done that in
> a more or less clean way (parsing the logs, patching Nagios, running
> a duplicate request with MRTG / Cricket).
>
> It would be excellent to have an "official" way to export data from
> Nagios.
>
> Yet... how would that interact with the concept of 'trends' ? rrdtool
> and Nagios' Trends basically represent the same kind of information
> (the history of a variable). So... would it still be interesting to keep the
> trends ?
I think we should keep the trends, since there IS a difference. Nagios
trends are about the history of a variable, that's true. However, there
are some extra variables to be considered when these trends are
generated. Besides, rrdtool also does calculations on a variable
(calculation the average, wrapping counters around), and that's not what
we want the the "state" variable.
So i think the can stay for now.
>
> Olivier
>
--
//||\\ Edwin Eefting
|| || || DatuX - Linux solutions and innovations
\\||// http://www.datux.nl
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: lists@datux.nl