Duh.. on the graph site if I set the Type to "Max Value" it will show the peaks on all graphs.
Thanks for your help anyway. > -----Original Message----- > From: Palle L Jensen [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 14, 2008 4:48 PM > To: 'Patrick Morris' > Cc: 'Nagios Users' > Subject: RE: [Nagios-users] Nagiosgrapher showing different values over > time > > Thanks for you response. I understand, but The question I had is why are > the peaks that are showing on the daily and weekly graphs not appearing on > the monthly and yearly graphs? > > > -----Original Message----- > > From: Patrick Morris [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, May 14, 2008 1:30 PM > > To: Palle L Jensen > > Cc: Nagios Users > > Subject: Re: [Nagios-users] Nagiosgrapher showing different values over > > time > > > > On Wed, 14 May 2008, Palle L Jensen wrote: > > > > > > > > I have noticed that in the graphs for ping and also Cpu load that the > > graphs are changing as you look at the different graphs. > > > For example the ping daily/graph shows at 11:00 14ms, then when you > look > > at the weekly/graph it shows for the same day and time only 10ms, if you > > look at the monthly it?s gone down to 10.5 ms for the same day. > Shouldn?t > > it be consistent showing the same value on the daily/weekly, monthly and > > yearly graph if you are looking at the same day and time on all the > > different graphs? Does anyone have an explanation on this? > > > > No, they should not be the same. Each graph shows an average over a > > different time period, depending on the scale of the graph. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
