So I talked to some people in the #zeromq channel on freenode, and have been
reading through the zeromq guide. Seems like at scale, with tons of nodes,
you would need pretty fast disk I/O to handle all the writes to RRD. Using
ZeroMQ, you could dish out to different collectd worker machines to
Hi Allan,
if you're after distributing the load, you might want to take a look at
the AMQP plugin, too. It has these topic branches, where subscribers
can subscribe to matching messages only. This allows you to distribute
the load in a consistent manner and is re-configurable during runtime.
Hi guys,
Just a little note: The current implementation of ZMQ filter on the
subscriber, not on the publisher...
Seem that ZMQ v3 is addressing the problem.
my 2cents
On Mon, Aug 29, 2011 at 9:22 AM, Florian Forster o...@collectd.org wrote:
Hi Allan,
if you're after distributing the load,
Thanks Francois, the way the code is right now, the subscriber is the node
doing the bind, and the publisher connects to the subscriber. This would
mean that your central collectd process would be able to do the filtering
since it is the subscriber.
As far as AMQP goes, we have noticed scaling
Hello,
Allan Feid wrote,
Hello,
I've been looking into using collectd combined with zeromq for transport.
This seems like a fairly good way to scale out monitoring infrastructure as
each node being monitored can send out requests over zeromq to one or more
locations with little overhead. I
