Tobias Oetiker wrote: > Hi Thorsten, > > Today Thorsten von Eicken wrote: > >> I totally concur. We use collectd and rrdtool in production, monitoring >> thousands of machines and I rather not know how many rrds. We have tens >> of servers running to collect all the data and can't wait to deploy >> rrdcached. We've tried but ran into a bug with flushing (it didn't do >> it) which we still need to reproduce cleanly. We desperately want a full >> networked daemon so we can aggregate across arbitrary monitored servers >> whose rrds end up on different rrdcached servers. Security is a >> low-priority issue because (a) the data is not all that sensitive to >> start with and (b) all this is behind firewall, plus (c) the server ids >> used by the data collection are not easy to map back to something >> meaningful. The one feature we will need is the ability to fetch data >> from rrdcached. This is necessary to aggregate across multiple rrd >> stores and also for performance. We compute alerts from the data in rrds >> so there is a constant fetch stream going on, not just when someone is >> actively looking at graphs. > > :-) well 1.4 will probably only bring part of the sollution for > you. Also note that the fetching will cause the daemon to be > flushed which kills the performance gains ... the sollution here is for > the daemon to support updatev (there is a plan on how todo this but > it is also for 1.5) then you get the data values as they are shoved into the > RRAs right which allows you todo alerts without killing performance ...
Thanks for reminding me, sigh... > regarding the flusing problem, could you test this again, as I > think there were some fixes in this area. Will do! > cheers > tobi TvE _______________________________________________ rrd-developers mailing list rrd-developers@lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers