----- Original Message -----
From: "Tobias Oetiker" <[email protected]>
>> I tried getting mrtg to work with rrdcached but it uses updatev
>> in the rrdtool v1.2+ code path so it doesn't work. Looking through
>> the code it seemed like there was no reason why if we forced the
>> old 1.1 path it wouldn't work just fine.
>
> except for the rrdtool fetch which is necessary to figure out of
> alarms have to be raised which would force rrdcachd to flush the
> cache on every round ... but if you do NOT use alarms, then things
> should work fine.
Hmm, we don't use alarms but there doesn't seem to be any condition
on the fetch, so its only processed if there are threshold checks
are defined.
Are you saying that the call to threshcheck and the info / fetch
block under the comment:
# get the rrdtool-processed values back from rrdtool
in mrtg could be skipped if no threshold checks are defined?
The following is the stats from our rrdcached which has been running
now ~ 30hours, it does seem to indicate there are a very large number
of possibly unneeded flushes happening, do you think this is down
to the mrtg fetch?
9 Statistics follow
QueueLength: 0
UpdatesReceived: 9156170
FlushesReceived: 1083366
UpdatesWritten: 1475662
DataSetsWritten: 9103092
TreeNodesNumber: 4153
TreeDepth: 15
JournalBytes: 0
JournalRotate: 0
Regards
Steve
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the
person or entity to whom it is addressed. In the event of misdirection, the
recipient is prohibited from using, copying, printing or otherwise
disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please
telephone +44 845 868 1337
or return the E.mail to [email protected].
_______________________________________________
rrd-users mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
