This is caused by an SNMP query not completing properly. Usually timeouts or a device failing to reply properly.
Its usually an indicator of packetloss somewhere.
This happens with us an not other platforms because we rely on snmpbulkwalk, which is more efficient but also more prone to network issues.
Adam.
Sent from BlueMail
On 19 Oct 2016, 15:48, at 15:48, greg lambert grelamen1@gmail.com wrote:
Thank you,
From time to time I get these breaks in the graphs. I thought it was my
memory/cpu or rrd but I have other solutions on the server like cacti, smokeping... that does not exhibit the same... would you have any idea?
On 10/19/2016 1:01 PM, Paul Townsend wrote:
On Wed, Oct 19, 2016 at 12:19:57 -0500, greg lambert wrote:
Just one simple maintenance question - it seems observium pulls lots
of data,
logs is 2.5 g and rrds is 9.5 g for 60 devices for 9 mths. Is this
normal ,if
not, is there any maintenance advice that you can give?
Take a look at the housekeeping script:
http://www.observium.org/docs/housekeeping/
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium