Xymon Mailing List Archive search

Help with Graphing peak values

6 messages in this thread

list Phil Wild · Wed, 18 Jan 2006 09:24:29 +0800 ·
Hello hobbit users,
 
I am looking at changing the graph for load average (if possible).
Actually, this applies to a few of the graphs.
 
Typically, our systems are very busy during the day yet at night are
mostly idle (load average of around 10 to 12. When you look at the
graphs produced from a capacity planning perspective, for the last 48
hours, you get accurate values, but from a 576 day graph, the load
average is much lower as it is taking into account the out of hours
period.
 
I was thinking it would be nice to see a line plotted on the same graph
showing the peak value for the sample rather than the average.
 
I have been reading through rrdtool man pages but every change I make
seems to stop the graphs being produced.
 
Ideas?
 
Thanks
 
Phil

=======================================================
                 IMPORTANT INFORMATION

This message and any files transmitted with it are confidential and should be read only by those persons to whom it is addressed.  If you have received this message in error, please notify us immediately by way of reply. Please also destroy and delete the message from your computer.  Any unauthorised form of reproduction of this message is strictly prohibited. 

It is the duty of the recipient to virus scan and otherwise test the information provided before loading on to any computer system.  No warranty is given or made by Asgard Wealth Solutions Limited, Asgard Capital Management Limited or SECURITOR Financial Group Limited that the information is free of a virus or any other defect or error and they will not be liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt.

Any views expressed in this message are those of the individual sender, except where the sender specifically states they are the views of Asgard Wealth Solutions Limited, Asgard Capital Management Limited or SECURITOR Financial Group Limited, as the case may be.

=======================================================
list Ralph Mitchell · Wed, 18 Jan 2006 07:01:42 -0600 ·
Well, nobody else spoke up yet...

I don't know if this will help, but it might push you in the right
direction.  The rrds are created with builtin archives that are
defined like this:

    "RRA:AVERAGE:0.5:1:576"
    "RRA:AVERAGE:0.5:6:576"
    "RRA:AVERAGE:0.5:24:576"
    "RRA:AVERAGE:0.5:288:576"

The rrdcreate man page says that the "576" is the number of rows to
create, and the number immediately preceeding that is the number of
original data samples to average together to create any given datum in
the archive.

So, for example, each point in the second archive is averaged from 6
points in the original data.

I haven't tried this myself, but I would expect to be able to increase
that "576" without affecting anything, other than possibly getting
graphs that are 6 feet long...  The number 576 is the number of
samples that occur at 5 minute intervals in 48 hours.  One week of
samples at 5 min intervals would be:

     7 * 24 * 60 / 5 = 2016

I have no idea how that would affect the graphing stuff built into Hobbit...

Ralph Mitchell
quoted from Phil Wild


On 1/17/06, Wild, Phil <user-89e1187e271b@xymon.invalid> wrote:
Hello hobbit users,

I am looking at changing the graph for load average (if possible). Actually,
this applies to a few of the graphs.

Typically, our systems are very busy during the day yet at night are mostly
idle (load average of around 10 to 12. When you look at the graphs produced
from a capacity planning perspective, for the last 48 hours, you get
accurate values, but from a 576 day graph, the load average is much lower as
it is taking into account the out of hours period.

I was thinking it would be nice to see a line plotted on the same graph
showing the peak value for the sample rather than the average.

I have been reading through rrdtool man pages but every change I make seems
to stop the graphs being produced.

Ideas?

Thanks

Phil
list Timothy L. Myers · Wed, 18 Jan 2006 10:15:32 -0700 ·
While you in there for my use the best change would be if you take the data average over a period put it in a Sunday - Saturday array and plot the average by hour or 5 min segment for a 7 day work week.  This view would give a work week load graph that would help on load balancing scheduled tasks and new project in the work week.
 
I am new to this wonderfully tool (Hobbit) and still trying to understand the basics.  I don't know yet how easy it is to filter the data or extract and create a new database.  I would assume that pulling the data periodically and building a summary database would be the easy approach. Another approach would be to build a day of the week data base with the same data as the load data.  I don't know yet if the graphing tool has a adequate summary function for the task given day of the week, hour, time, date, load order. 
 
Right now I have more questions than answers, I will be reading and testing to get my answers but in the mean time I thought I would add my suggestion as long as your research is already headed that way.
quoted from Phil Wild

 
 -----Original Message-----
From: Wild, Phil [mailto:user-89e1187e271b@xymon.invalid]
Sent: Tuesday, January 17, 2006 6:24 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] Help with Graphing peak values


Hello hobbit users,
 
I am looking at changing the graph for load average (if possible). Actually, this applies to a few of the graphs.
 
Typically, our systems are very busy during the day yet at night are mostly idle (load average of around 10 to 12. When you look at the graphs produced from a capacity planning perspective, for the last 48 hours, you get accurate values, but from a 576 day graph, the load average is much lower as it is taking into account the out of hours period.
 
I was thinking it would be nice to see a line plotted on the same graph showing the peak value for the sample rather than the average.
 
I have been reading through rrdtool man pages but every change I make seems to stop the graphs being produced.
 
Ideas?
 
Thanks
 
Phil

=======================================================
IMPORTANT INFORMATION

This message and any files transmitted with it are confidential and should be read only by those persons to whom it is addressed. If you have received this message in error, please notify us immediately by way of reply. Please also destroy and delete the message from your computer. Any unauthorised form of reproduction of this message is strictly prohibited. 

It is the duty of the recipient to virus scan and otherwise test the information provided before loading on to any computer system. No warranty is given or made by Asgard Wealth Solutions Limited, Asgard Capital Management Limited or SECURITOR Financial Group Limited that the information is free of a virus or any other defect or error and they will not be liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt.

Any views expressed in this message are those of the individual sender, except where the sender specifically states they are the views of Asgard Wealth Solutions Limited, Asgard Capital Management Limited or SECURITOR Financial Group Limited, as the case may be.

=======================================================
list Henrik Størner · Wed, 18 Jan 2006 18:49:23 +0100 ·
quoted from Timothy L. Myers
Typically, our systems are very busy during the day yet at night are mostly idle (load 
average of around 10 to 12. When you look at the graphs produced from a capacity planning 
perspective, for the last 48 hours, you get accurate values, but from a 576 day graph, 
the load average is much lower as it is taking into account the out of hours period.
That's how rrdtool works - the further back in time you go, the more
the data is averaged out over the entire time period.
quoted from Timothy L. Myers
I was thinking it would be nice to see a line plotted on the same graph showing the peak 
value for the sample rather than the average.
You *can* do it, but it will require that you create custom RRD's for
the data that you want to measure like this.

RRDtool stores data from one dataset in one or more "archives" called
"RRA's". An RRA uses a "consolidation function" to convert the raw data
into the data that it stores - typically by computing an average value
over the time interval that is used for the data. But you need not use
the "average" method - there are others, including MIN and MAX to store
the minimum and maximum values for a timeperiod.

When Hobbit creates a new RRD file, it defines 4 archives for each dataset.
All of them use the AVERAGE function, but averages the data over
different time periods, which is why there are 4 graphs for each data
showing the 48-hour, one-week, 4 weeks, and 576 days data.

So what you can do is to create the RRD files by hand using the "rrdtool
create" command. As long as the dataset names match, Hobbit will happily
update your custom RRD files - rrdtool takes care of that. So for e.g. 
the cpu load (the "la.rrd" file): "rrdtool dump" tells you that there is
one dataset called "la" of type GAUGE and a minimum value of 0. So you
could create such an rrd file with the command

   rrdtool create la.rrd \
      DS:la:GAUGE:600:0:U \
      RRA:AVERAGE:0.5:1:576 \
      RRA:AVERAGE:0.5:6:576 \
      RRA:AVERAGE:0.5:24:576 \
      RRA:AVERAGE:0.5:288:576 \
      RRA:MAX:0.5:288:576

The first 4 RRA's are the standard ones Hobbit uses. The last one is a
custom RRA that stores the maximum reading over 288 measurements (that's
24 hours since we measure once every 5 minutes), and keeps 576 of those
measurements in the database. So it gives you the max. load seen over
the past 576 days.

If you create such a file in the ~hobbit/data/rrd/HOSTNAME/ directory
where Hobbit puts its RRD files, it should be updated automatically.

Then to graph the data, you just have to setup a custom graph definition
that uses the MAX RRA instead of the AVERAGE one: 

[maxla]
        TITLE MAX CPU Load
        YAXIS Load
        DEF:avg=la.rrd:la:MAX
        CDEF:la=avg,100,/
        AREA:la#00CC00:CPU Load Average
        -u 1.0

Compare it to the existing [la] definition in hobbitgraph.cfg, and
you'll see they are almost identical.

I haven't tried this at all, so if you do - please let us know what 
your experiences are.


Regards,
Henrik
list Phil Wild · Thu, 19 Jan 2006 09:41:33 +0800 ·
Many thanks with this answer. I'll give it a go and report back.

Phil 
quoted from Henrik Størner

-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid] 
Sent: Thursday, 19 January 2006 1:49 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Help with Graphing peak values
Typically, our systems are very busy during the day yet at night are 
mostly idle (load average of around 10 to 12. When you look at the 
graphs produced from a capacity planning perspective, for the last 48 
hours, you get accurate values, but from a 576 day graph, the load
average is much lower as it is taking into account the out of hours
period.
That's how rrdtool works - the further back in time you go, the more the
data is averaged out over the entire time period.
I was thinking it would be nice to see a line plotted on the same 
graph showing the peak value for the sample rather than the average.
You *can* do it, but it will require that you create custom RRD's for
the data that you want to measure like this.

RRDtool stores data from one dataset in one or more "archives" called
"RRA's". An RRA uses a "consolidation function" to convert the raw data
into the data that it stores - typically by computing an average value
over the time interval that is used for the data. But you need not use
the "average" method - there are others, including MIN and MAX to store
the minimum and maximum values for a timeperiod.

When Hobbit creates a new RRD file, it defines 4 archives for each
dataset.
All of them use the AVERAGE function, but averages the data over
different time periods, which is why there are 4 graphs for each data
showing the 48-hour, one-week, 4 weeks, and 576 days data.

So what you can do is to create the RRD files by hand using the "rrdtool
create" command. As long as the dataset names match, Hobbit will happily
update your custom RRD files - rrdtool takes care of that. So for e.g. 
the cpu load (the "la.rrd" file): "rrdtool dump" tells you that there is
one dataset called "la" of type GAUGE and a minimum value of 0. So you
could create such an rrd file with the command

   rrdtool create la.rrd \
      DS:la:GAUGE:600:0:U \
      RRA:AVERAGE:0.5:1:576 \
      RRA:AVERAGE:0.5:6:576 \
      RRA:AVERAGE:0.5:24:576 \
      RRA:AVERAGE:0.5:288:576 \
      RRA:MAX:0.5:288:576

The first 4 RRA's are the standard ones Hobbit uses. The last one is a
custom RRA that stores the maximum reading over 288 measurements (that's
24 hours since we measure once every 5 minutes), and keeps 576 of those
measurements in the database. So it gives you the max. load seen over
the past 576 days.

If you create such a file in the ~hobbit/data/rrd/HOSTNAME/ directory
where Hobbit puts its RRD files, it should be updated automatically.

Then to graph the data, you just have to setup a custom graph definition
that uses the MAX RRA instead of the AVERAGE one: 

[maxla]
        TITLE MAX CPU Load
        YAXIS Load
        DEF:avg=la.rrd:la:MAX
        CDEF:la=avg,100,/
        AREA:la#00CC00:CPU Load Average
        -u 1.0

Compare it to the existing [la] definition in hobbitgraph.cfg, and
you'll see they are almost identical.

I haven't tried this at all, so if you do - please let us know what your
experiences are.


Regards,
Henrik


=======================================================
                 IMPORTANT INFORMATION

This message and any files transmitted with it are confidential and should be read only by those persons to whom it is addressed.  If you have received this message in error, please notify us immediately by way of reply. Please also destroy and delete the message from your computer.  Any unauthorised form of reproduction of this message is strictly prohibited. 

It is the duty of the recipient to virus scan and otherwise test the information provided before loading on to any computer system.  No warranty is given or made by Asgard Wealth Solutions Limited, Asgard Capital Management Limited or SECURITOR Financial Group Limited that the information is free of a virus or any other defect or error and they will not be liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt.

Any views expressed in this message are those of the individual sender, except where the sender specifically states they are the views of Asgard Wealth Solutions Limited, Asgard Capital Management Limited or SECURITOR Financial Group Limited, as the case may be.

=======================================================
list Kumaresh P N · Mon, 19 Oct 2009 15:21:01 -0400 ·
Hi,

I followed this link to Graph the peak values
http://www.hswn.dk/hobbiton/2006/01/msg00202.html

But before doing this ...

#/usr/local/rrdtool-1.2.19/bin/rrdtool info la.rrd
filename = "la.rrd"
rrd_version = "0003"
step = 300
last_update = 1255979096
ds[la].type = "GAUGE"
ds[la].minimal_heartbeat = 600
ds[la].min = 0.0000000000e+00
ds[la].max = NaN
ds[la].last_ds = "37"
ds[la].value = 1.0952000000e+04
ds[la].unknown_sec = 0
rra[0].cf = "AVERAGE"
rra[0].rows = 576
rra[0].pdp_per_row = 1
rra[0].xff = 5.0000000000e-01
rra[0].cdp_prep[0].value = NaN
rra[0].cdp_prep[0].unknown_datapoints = 0
rra[1].cf = "AVERAGE"
rra[1].rows = 576
rra[1].pdp_per_row = 6
rra[1].xff = 5.0000000000e-01
rra[1].cdp_prep[0].value = 0.0000000000e+00
rra[1].cdp_prep[0].unknown_datapoints = 0
rra[2].cf = "AVERAGE"
rra[2].rows = 576
rra[2].pdp_per_row = 24
rra[2].xff = 5.0000000000e-01
rra[2].cdp_prep[0].value = 4.4309333333e+02
rra[2].cdp_prep[0].unknown_datapoints = 0
rra[3].cf = "AVERAGE"
rra[3].rows = 576
rra[3].pdp_per_row = 288
rra[3].xff = 5.0000000000e-01
rra[3].cdp_prep[0].value = 8.9465533333e+03
rra[3].cdp_prep[0].unknown_datapoints = 0
• After following the link ... i get this .. NAN value ... any way to fix it

*# /usr/local/rrdtool-1.2.19/bin/rrdtool info la.rrd
filename = "la.rrd"
rrd_version = "0003"
step = 300
last_update = 1255979247
ds[la].type = "GAUGE"
ds[la].minimal_heartbeat = 600
ds[la].min = 0.0000000000e+00
ds[la].max = NaN
ds[la].last_ds = "UNKN"
ds[la].value = 0.0000000000e+00
ds[la].unknown_sec = 147
rra[0].cf = "AVERAGE"
rra[0].rows = 576
rra[0].pdp_per_row = 1
rra[0].xff = 5.0000000000e-01
rra[0].cdp_prep[0].value = NaN
rra[0].cdp_prep[0].unknown_datapoints = 0
rra[1].cf = "AVERAGE"
rra[1].rows = 576
rra[1].pdp_per_row = 6
rra[1].xff = 5.0000000000e-01
rra[1].cdp_prep[0].value = NaN
rra[1].cdp_prep[0].unknown_datapoints = 1
rra[2].cf = "AVERAGE"
rra[2].rows = 576
rra[2].pdp_per_row = 24
rra[2].xff = 5.0000000000e-01
rra[2].cdp_prep[0].value = NaN
rra[2].cdp_prep[0].unknown_datapoints = 13
rra[3].cf = "AVERAGE"
rra[3].rows = 576
rra[3].pdp_per_row = 288
rra[3].xff = 5.0000000000e-01
rra[3].cdp_prep[0].value = NaN
rra[3].cdp_prep[0].unknown_datapoints = 229
rra[4].cf = "MAX"
rra[4].rows = 576
rra[4].pdp_per_row = 288
rra[4].xff = 5.0000000000e-01
rra[4].cdp_prep[0].value = NaN
rra[4].cdp_prep[0].unknown_datapoints = 229


Help is much apprepicate ... Trying to plot the graph with averaged out of
max value
• *************************************
Best Regards
Kumaresh