[rrd-users] Huge 'outlier' in a graph rendering rest of graph unreadable

David Ball davidtball at gmail.com
Thu Apr 23 19:32:14 CEST 2009

  Ugh....my max was set to 1Tbps, not 1Gbps....duh.  Thanks for the smack.


On 23/04/2009, A Darren Dunham <ddunham at taos.com> wrote:
> On Thu, Apr 23, 2009 at 09:21:03AM -0600, David Ball wrote:
>>   A couple of weeks ago, a process running on one of the routers
>> restarted itself, and resulted in the interface counter values being
>> reset to 0.  As such, the counter value went from, say, 35000000000 in
>> one reading to 16000 in the next.  While the parsing script can detect
>> these types of things and 'discard' the sample when calculating the
>> total bytes in/out on the interface, the value was still graphed,
>> resulting in a spike to 125Gbps in the graph (obviously impossible).
> You're collecting as a COUNTER?  Do you have the max on your DS set
> below that impossible value?
> --
> Darren
> _______________________________________________
> rrd-users mailing list
> rrd-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

More information about the rrd-users mailing list