improving the 300 second resolution nagiosgraph

Litwin, Matthew mlitwin at stubhub.com
Tue Jan 5 16:09:23 CET 2010


Thank you very much. This correlates with the results I am seeing. Normally this behavior is something that is beneficial for any sort of floating point arithmetic but can easily produce confusing results for monitors with (1) integer values and (2) have checks more frequent that the step or "bucket" duration.

>From your explanation this is what I can surmise about my current case. A monitor is checked every 60 seconds so there are going to be 5 readings per step that would be averaged. This monitor usually flat at "0" and occasionally blips into "1". Thus, depending on how many readings per step are at "1" and how many are at "0", my RRD data at each step will predictably be 0.2 for 1 reading at "1", 0.4 for 2 readings at "1" and so forth. Do I have that right?

That said, it sounds like I might want to make a plea to the author of nagiosgraph to make the step length something that can be configureable, but I might just be hitting the wall of what this tool can actually do.

On Jan 5, 2010, at 6:10 AM, Marc Powell wrote:

> 
> On Jan 5, 2010, at 7:40 AM, Eric Emerson wrote:
> 
>> I had the opposite problem a while back (checks which only ran every 30 minutes making the grahps really choppy.
>> You can change the heartbeat value in nagiosgraph.conf which controls the --step for rrdcreate 
> 
> This is very different functionality, but may appear to be be the same effect in your case. It absolutely does not affect the step value. Heartbeat essentially specifies how much time can be missed before a value is considered to be unknown. It's also set per datasource whereas step applies universally to the entire rrd database (which may contain multiple datasources). Think of the steps as a bunch of buckets in a line. You walk along the line placing something in each bucket (value at each step). If you skip one, rrdtool is smart enough to guess what you would have put in it based on what's in the bucket before it and the bucket after it and your consolidation functions (AVERAGE, MAX, MIN, etc). The heartbeat determines how many buckets (steps) you can skip in a row before rrdtool will
  give up on guessing what would have been in them and just assume they were empty.
> 
> --
> Marc
> 
> 
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev 
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> 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

Thanks,
Matthew Litwin
mlitwin at stubhub.com
415.222.8475


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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





More information about the Users mailing list