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) 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://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
