Xymon Mailing List Archive search

Custom 60 second interval test still has 5 min interval graph

list Scot Kreienkamp
Wed, 1 Jul 2015 03:10:00 +0000
Message-Id: <user-82c2c10d2367@xymon.invalid>

Hi Jeremy,

I’m viewing the graph on the custom test page.  The data is being reported in via data message if that makes a difference.  Not sure what you mean by reducing the trends period?


Scot Kreienkamp  | Senior Systems Engineer | La-Z-Boy Corporate
One La-Z-Boy Drive | Monroe, Michigan 48162 | Office: XXX-XXX-XXXX | | Mobile: XXXXXXXXXX | Email: user-9678697f1438@xymon.invalid
From: Jeremy Laidman [mailto:user-71895fb2e44c@xymon.invalid]
Sent: Tuesday, June 30, 2015 9:48 PM
To: Scot Kreienkamp
Cc: J.C. Cleaver; xymon at xymon.com
Subject: Re: [Xymon] Custom 60 second interval test still has 5 min interval graph

Scot

I /think/ the RRD side of things is correct, so it must be the graphing that's the problem.

Where are you viewing the graph?  On the "stats" page?  If so, have you tried reducing the trends period to (say) 30 minutes?

J


On 1 July 2015 at 09:49, Scot Kreienkamp <user-9678697f1438@xymon.invalid<mailto:user-9678697f1438@xymon.invalid>> wrote:
Hi JC,

Maybe I missed it when it's staring me in the face, but I still don't understand why it's not showing the 1 minute resolution when it is saving it into the RRD.  The resulting RRD from the configuration I posted has a 60 second step, a 180 second heartbeat, and the data is being stored every 60 seconds, all of that verified by rrdtool dump.  So I have successfully increased the resolution of the RRD; but even though it's stored every minute the resulting graph only registers changes in values every 5 minutes.

-----Original Message-----
From: J.C. Cleaver [mailto:user-87556346d4af@xymon.invalid<mailto:user-87556346d4af@xymon.invalid>]
Sent: Tuesday, June 30, 2015 7:13 PM
To: Scot Kreienkamp
Cc: xymon at xymon.com<mailto:xymon at xymon.com>
Subject: Re: [Xymon] Custom 60 second interval test still has 5 min interval
graph

This is correct.

The data format for a "round robin database" is fixed at creation time for
a certain number of data points at a certain interval, using a certain
method for combining them (typically 'AVERAGE' by default).

When you're increasing the number of data points you're submitting, you're
putting more data in, but you're still only going to see 5 minute average
"chunks" (and the larger ones). To actually increase the resolution you're
saving at, you'll want to use (I believe) the 'rrdtune' command.
Alternatively, some find it easier to export/re-import the data into a new
file.


HTH,
-jc


On Tue, June 30, 2015 2:21 pm, Scot Kreienkamp wrote:
Hey everyone,

I created a custom test and RRD definition because I wanted to reduce the
interval time on a few graphs from 5 minute resolution to 1 minute.  I got
the data to be logged once every minute, which I verified is hitting the
RRD.  The problem is that when I view the graph it's still got a
resolution of 5 minutes.

Here's the partial RRDTool dump:

                        <!-- 2015-06-30 16:53:00 EDT / 1435697580 -->
<row><v> 1.0033333333e+01 </v></row>
                        <!-- 2015-06-30 16:54:00 EDT / 1435697640 -->
<row><v> 1.0550000000e+01 </v></row>
                        <!-- 2015-06-30 16:55:00 EDT / 1435697700 -->
<row><v> 5.6333333333e+00 </v></row>
                        <!-- 2015-06-30 16:56:00 EDT / 1435697760 -->
<row><v> 7.3166666667e+00 </v></row>
                        <!-- 2015-06-30 16:57:00 EDT / 1435697820 -->
<row><v> 7.5000000000e+00 </v></row>
                        <!-- 2015-06-30 16:58:00 EDT / 1435697880 -->
<row><v> 6.2500000000e+00 </v></row>
                        <!-- 2015-06-30 16:59:00 EDT / 1435697940 -->
<row><v> 7.5500000000e+00 </v></row>
                        <!-- 2015-06-30 17:00:00 EDT / 1435698000 -->
<row><v> 9.3333333333e+00 </v></row>
                        <!-- 2015-06-30 17:01:00 EDT / 1435698060 -->
<row><v> 5.2666666667e+00 </v></row>
                        <!-- 2015-06-30 17:02:00 EDT / 1435698120 -->
<row><v> 7.0666666667e+00 </v></row>
                        <!-- 2015-06-30 17:03:00 EDT / 1435698180 -->
<row><v> 6.4000000000e+00 </v></row>
                        <!-- 2015-06-30 17:04:00 EDT / 1435698240 -->
<row><v> 6.4000000000e+00 </v></row>
                        <!-- 2015-06-30 17:05:00 EDT / 1435698300 -->
<row><v> 1.3000000000e+01 </v></row>
                        <!-- 2015-06-30 17:06:00 EDT / 1435698360 -->
<row><v> 9.2000000000e+00 </v></row>
                        <!-- 2015-06-30 17:07:00 EDT / 1435698420 -->
<row><v> 3.4650000000e+01 </v></row>
                        <!-- 2015-06-30 17:08:00 EDT / 1435698480 -->
<row><v> 5.7200000000e+01 </v></row>
                        <!-- 2015-06-30 17:09:00 EDT / 1435698540 -->
<row><v> 5.0283333333e+01 </v></row>
                        <!-- 2015-06-30 17:10:00 EDT / 1435698600 -->
<row><v> 4.4100000000e+01 </v></row>
                        <!-- 2015-06-30 17:11:00 EDT / 1435698660 -->
<row><v> 4.1500000000e+01 </v></row>
                        <!-- 2015-06-30 17:12:00 EDT / 1435698720 -->
<row><v> 2.4500000000e+01 </v></row>
                        <!-- 2015-06-30 17:13:00 EDT / 1435698780 -->
<row><v> 1.2000000000e+01 </v></row>

So the data is getting logged every 60 seconds.  It's also rolling up to
the 5 second, etc, values.

Here's the line from xymonserver.cfg:

SPLITNCV_cpustat="*:GAUGE:180:0:100"  #Configure for 60 second
intervals,
range of 0-100


Here's the lines from rrddefinitions.cfg:
[cpustat]
-s 60
        RRA:AVERAGE:0.1:1:120
        RRA:AVERAGE:0.5:5:576
        RRA:AVERAGE:0.5:30:576
        RRA:AVERAGE:0.5:120:576
        RRA:AVERAGE:0.5:1440:576
        RRA:MAX:0.1:1:120
        RRA:MAX:0.5:5:576
        RRA:MAX:0.5:30:576
        RRA:MAX:0.5:120:576
        RRA:MAX:0.5:1440:576

Here's the graph definition:
[cpustat]
        FNPATTERN ^cpustat.(.+).rrd
        TITLE % CPU usage
        YAXIS Percent
        DEF:p at RRDIDX@=@RRDFN@:lambda:MAX
        LINE2:p at RRDIDX@#@COLOR@:@RRDPARAM@
        GPRINT:p at RRDIDX@:LAST: \: %5.0lf (cur)
        GPRINT:p at RRDIDX@:MAX: \: %5.0lf (max)
        GPRINT:p at RRDIDX@:MIN: \: %5.0lf (min)
        GPRINT:p at RRDIDX@:AVERAGE: \: %5.0lf (avg)\n


I had read that RRDTool should use the lowest resolution available, which
is 1 minute for this RRD.  So why are the graphs not going less than 5
minute intervals when zooming in?  Any ideas?

Thanks!

Scot Kreienkamp | Senior Systems Engineer | La-Z-Boy Corporate
One La-Z-Boy Drive | Monroe, Michigan 48162  | * XXX-XXX-XXXX | | *
7349151444 | *  user-9678697f1438@xymon.invalid<mailto:user-9678697f1438@xymon.invalid><mailto:%7BE-mail%7D>
www<http://www.la-z-boy.com/>.la-z-boy.com<http://la-z-boy.com><http://www.la-z-
boy.com/<http://boy.com/>>; |
facebook.<https://www.facebook.com/lazboy>com<https://www.facebook
.com/lazboy>/<https://www.facebook.com/lazboy>lazboy<http://facebook
.com/lazboy>
| twitter.com/lazboy<http://twitter.com/lazboy><https://twitter.com/lazboy>; |
youtube.com/<http://youtube.com/><https://www.youtube.com/user/lazboy>lazboy<https://ww
w.youtube.com/user/lazboy<http://w.youtube.com/user/lazboy>>;
[cid:lzbVertical_hres.jpg]


This message is intended only for the individual or entity to which it is
addressed.  It may contain privileged, confidential information which is
exempt from disclosure under applicable laws.  If you are not the intended
recipient, you are strictly prohibited from disseminating or distributing
this information (other than to the intended recipient) or copying this
information.  If you have received this communication in error, please
notify us immediately by e-mail or by telephone at the above number.
Thank
you.

This message is intended only for the individual or entity to which it is addressed.  It may contain privileged, confidential information which is exempt from disclosure under applicable laws.  If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information.  If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.