> > Ideally, I think it would be a very interesting step to be able to > > 'stack' syslog modules to define the path a given set of messages > take > > through the collector. Something akin to the Linux iptables concept, > > where a basic high-speed framework is laid out with a well-defined > > order and an API that enables administrators to elect how specific > > run-time modules interact within the stack. That's less of a request > > and more of a pipe dream, and is definitely influenced by the half > > network security hat I wear. > > hmm, the recent ability to have secondary queues would allow this to > fit > in very nicely as a filter for what to do when moving messages between > the > queues.
I have thought more about this over the night. I think most of the capabilities are already present, just need to be a bit "re-labled". However, what is missing is functionality to use loadable modules as a filter condition. However, especially for complex filters, this sounds very valuable, both from a performance as well as from a capability POV. It also looks like it is not hard to add. I will definitely look into that direction. Thanks all for bringing up these thoughts, any further comments are of course appreciated as well ;) Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
