From: the+cricket@llama.com
On Tue, 12 Oct 1999, Scott Call wrote:
> From: Scott Call <scall@devolution.com>
>
> All is working well except that when the counters reset to 0, we get
> huge spikes for DSL customers (since they are usually really light
> users, a reset to 0 can look like a 90 Mbps spike). I was wondering
> (and this may be an RRD issue, not a cricket issue) if there was a way
> to drop or ignore samples like that. I'd rather risk missing a 5 minute
> spike than have to deal with customers asking why their 384 DSL peaked
> at 90Mbps in the middle of the night.
>
> Any ideas?
This is probably what you want, in lieu of the workaround for very fast
interfaces which is yet forthcoming.
>From http://www.munitions.com/~jra/cricket/doc/reference.html
rrd-max
Default value: U
This tag is used to set the RRD maximum value parameter. If RRD gets a value
higher than this number, it will throw the data away, instead of adding it to
the RRA. This can be used to filter bad data, though it could be argued it
would be better to simply avoid fetching bad data in the first place. When it
is set to "U" (for unknown), RRD does not attempt to check incoming data
against an upper bound.
If the tag rrd-max is present in the target dictionary, it will override the
value found in the datasource dictionary. This makes is possible to assign
different maxima to different targets.
If this value is changed after the underlying RRD file has been created, the
rrd-tune script must be used to apply the changes.
Take care,
--Sam
--------------------------- ONElist Sponsor ----------------------------
??? Computer Questions ==> Free Answers From Live Experts ! ! !
go to EXPERTCITY.COM
<a href=" http://clickme.onelist.com/ad/expertcity15 ">Click Here</a>
------------------------------------------------------------------------
This archive was generated by hypermail 2b29 : Mon Mar 06 2000 - 19:01:03 PST