[rrd-users] Re: How to handle upper limit spikes

Alex van den Bogaerdt alex at ergens.op.het.net
Thu Oct 12 15:08:43 MEST 2006


On Thu, Oct 12, 2006 at 08:53:07AM -0400, jeffrey.j.petter at verizon.com wrote:

> I'm graphing various firewall data, and one of the graphs shows the number
> of connections along with accepted packets. Typically, the number of
> connections may be in the neighborhood of 30,000 and the packets may be in
> the 1,200 - 1,800 range. Then, every other day, sometimes more frequently,
> there will be a spike in packets sending it up over 10 M, which skews the
> scale so severely that it makes the graph meaningless for 24 hours until
> the spike has passed. I have played around with setting an upper limit, but
> then the real story of the spike is never told. Is there a way to somehow
> note the spike, but still keep the graph in some meaningful perspective?


something like:

DEF:realdata=  ...etc...
CDEF:despiked=realdata,2000,GT,INF,realdata,IF
LINE2:despiked#0000FF:despiked
GPRINT:realdata:MAX:%6.2lf

after debugging this, you should end up with:

plotting all data upto 2000 as is, data above 2000 will just
reach top of graph but does not influence scaling.

Printing the maximum uses realdata, thus shows 10,000,000.


Isn't there a similar example in one of the tutorials?


-- 
Alex van den Bogaerdt
http://www.vandenbogaerdt.nl/rrdtool/

--
Unsubscribe mailto:rrd-users-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:rrd-users-request at list.ee.ethz.ch?subject=help
Archive     http://lists.ee.ethz.ch/rrd-users
WebAdmin    http://lists.ee.ethz.ch/lsg2.cgi



More information about the rrd-users mailing list