[rlug] Re: spike-uri rrdtool

[Catalin Bucur]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bogdan Luca wrote:
| ok, din ce am gasit pe net, o solutie ar fi sa te uiti la uptime-ul
| echipamentului, si in caz ca e <5 min (adica intervalul la care se face
| update), sa logheze 'U' in loc de valoarea counter-ului. o solutzie mai
| simpla?

Exista un asa-zis killspike, e un script in perl care exista prin
directorul contrib al rrdtool-ului:

# $Id: killspike.pl.in,v 1.1.1.1 2002/02/26 10:21:19 oetiker Exp $
# $Source:
/home/oetiker/data/cvs-repo/AABN-rrdtool/contrib/killspike/killspike.pl.in,v
$

#This script will read an XML file produced by
# rrdtool dump foo.rrd >in.xml
#and look at the $maxspike highest samples per datasource. It then finds
#the records with the most hits and ditches the data. The resulting file
#can be read back into the RRD database with the command
# rrdtool restore out.xml foo.rrd
#
#The whole idea is to find and eradicate "spikes" caused by erroneous
#readings affecting entire records.

Personal nu l-am folosit, asa ca nu stiu cum merge. Eu am tratat
situatia asa cum este, adica am creat un CDEF care sa ia valoarea
UNKNOWN daca depaseste o anumita valoare $SPIKE pe care i-o definesc eu.
In pseudocod, ceva de genul:

## if (DEF_in < $SPIKE)
## CDEF_result=DEF_in
## else
## CDEF_result=UNKN


- --
Catalin Bucur mailto:[EMAIL PROTECTED]
NOC @ Genius Network SRL - Galati - Romania

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9+xKHpDe20wwI9oIRAqueAJwL3Ggh9FNpaommrsVse5eDR0YzUQCff7ll
qx7FjS3Eu9CPiPkyprXSy7Q=
=MMRe
-----END PGP SIGNATURE-----

---
Pentru dezabonare, trimiteti mail la [EMAIL PROTECTED] cu subiectul 'unsubscribe rlug'.
REGULI, arhive si alte informatii: http://www.lug.ro/mlist/