Oh, those are very good news, as for us the zeromq is a very important
piece.
Please let me known when you have a tentative release schedule. Thanks
On 05/10/2012 12:39 PM, Brian Knox wrote:
Pablo:
Just a heads up - I'm one of the people from Aggregate Knowledge who worked
on the ZeroMQ modules. I'm currently at a new startup, and we internally
have a ground up rewrite of the modules using the v6 configuration, and
using the czmq api (rather than wrapping libzmq directly). We've just
begun testing the new modules internally. Let me talk to my folks today
and see what our schedule is for releasing them, as it could save you some
duplication of effort. More eyes on the code is always better!
Additionally, I wrote the omhiredis module that's currently in the 6.3.*
dev (on head, and I believe the code is in 6.3.8 dev release as well). The
omhiredis module is a redis output module using the hiredis C library, and
uses v6 configuration. I used Rainer's ommongodb output module as a guide
when writing it, as ommongodb only supports v6 config format.
Brian
On Thu, May 10, 2012 at 6:27 AM, Pablo Chacin<[email protected]>wrote:
Hi
I'm developing some custom input and output module to interface with a
proprietary application. In doing so, I've been checking how different
modules use the new configuration API and it's clear there are (at least)
two approaches.
OMLIBDBI implements BEGINnewActInst and uses
CODE_STD_STRING_**REQUESTparseSelectorAct
to parse configuration.
OMINFILE declares a callback function using this macro
CHKiRet(omsdRegCFSLineHdlr((**uchar *)"inputrunfilemonitor", 0,
eCmdHdlrGetWord,
addMonitor, NULL, STD_LOADABLE_MODULE_ID));
And then the addMonitor function processes the configuration
Is there any real difference? are those two ways to do the same depending
on whether the module is an input or output module?
My questions are mostly due to my limited understanding on how multiple
rulesets, selectors an actions work and how this relates to module
instances. Concretely, I need to start multiple instances of the output
module to forward event records filtered by different rules (e.g. severity,
source, etc). Also, I need to create multiple instances of the input module
to gather events from multiple sources.
Many thanks in advance
P.S. I'm also migrating the ZeroMQ input and output modules developed by
Aggregate Knowledge (https://github.com/**aggregateknowledge/rsyslog-**
zeromq<https://github.com/aggregateknowledge/rsyslog-zeromq>) to
rsyslog v6.
--
Pablo Chacin
R&D Engineer
SenseFields SL
Tlf (+34) 93 418 05 85
Baixada de Gomis 1,
08023 Barcelona (Spain)
http://www.sensefields.com/
______________________________**_________________
rsyslog mailing list
http://lists.adiscon.net/**mailman/listinfo/rsyslog<http://lists.adiscon.net/mailman/listinfo/rsyslog>
http://www.rsyslog.com/**professional-services/<http://www.rsyslog.com/professional-services/>
What's up with rsyslog? Follow https://twitter.com/rgerhards
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
--
Pablo Chacin
R&D Engineer
SenseFields SL
Tlf (+34) 93 418 05 85
Baixada de Gomis 1,
08023 Barcelona (Spain)
http://www.sensefields.com/
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
