I'm not using the Gauge option so that could very well be the problem.
I'll try that and see what happens since the values will be rather small and
shouldn't change much from each polling.However, should my log file still show all zeros beyond the initial line as indicated below? This was just an example, but the zeros continue on for the remainder of the file. Or is this related to not using the Gauge option? Just wanted to determine if there could be other issues beyond MRTG. Thanks, Brian -----Original Message----- From: Peter Glanville [mailto:[EMAIL PROTECTED] Sent: Friday, April 11, 2003 4:00 AM To: Myers Brian; [EMAIL PROTECTED] Subject: Re: [mrtg] Logging / Graphing Issues >The log file looks somewhat as follows: >1050011711 227 227 >1050011711 0 0 0 0 >1050011112 0 0 0 0 Are you using the Guage option? You have read in low values (227 for both variable being plotted). 5 mins later MRTG re-runs, and (by default) takes the previous value from the current value, and divides by 300 to get the 'per second' rate. Fractions are not stored. Values above Maxbytes (or AbsMax, if defined) are also dropped. Using 'Gauge' cause the system to not divide by 300, but simply plot the value (good for UPS voltage, current, etc) For systems with very low rates of change (eg printer pages are normally less than one per second), you can use options like PerMinute etc. Without knowing what you are plotting, and what entries are in your log file, it is impossible to be more specific. The time value is seconds since the beginning of time, the first two colums are the average/gauge values for the time interval and will be plotted in the graph, the last two are the peak rates (in case you use the withpeak option) Regards Peter -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
