Excellent. If you have concrete on-shot questions, it's probably far quicker for me to answer them...
Rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Pablo Chacin > Sent: Friday, May 11, 2012 11:31 AM > To: rsyslog-users > Subject: Re: [rsyslog] Advice on developing module to rsyslog 6 > > No problem! I'll proceed the way I understand it and then I'll ask you > back about the code. Thanks! > > On 05/11/2012 11:26 AM, Rainer Gerhards wrote: > > Pablo, > > > > I am currently a bit short on time. I guess it would work best if you post > > your code (or link to its public repository), so we could go through it. > > > > Rainer > > > >> -----Original Message----- > >> From: [email protected] [mailto:rsyslog- > >> [email protected]] On Behalf Of Pablo Chacin > >> Sent: Friday, May 11, 2012 10:01 AM > >> To: [email protected] > >> Subject: Re: [rsyslog] Advice on developing module to rsyslog 6 > >> > >> Rainer, Brian > >> > >> Regarding my initial questions about how to use the v6 configuration, > >> could you please help me to understand some things that puzzle me. As I > >> said before, these doubts come mostly from my limited understanding of > >> the configuration model and the interplay of rulesets, actions, > >> selectors, module instances). > >> > >> Is there any documentation besides the example modules (which I'm still > >> dissecting) > >> > >> Thanks again! > >> > >> On 05/11/2012 07:15 AM, Rainer Gerhards wrote: > >>>> -----Original Message----- > >>>> From: [email protected] [mailto:rsyslog- > >>>> [email protected]] On Behalf Of Brian Knox > >>>> Sent: Thursday, May 10, 2012 10:51 PM > >>>> To: rsyslog-users > >>>> Subject: Re: [rsyslog] Advice on developing module to rsyslog 6 > >>>> > >>>> Pablo, Rainer - > >>>> > >>>> We talked today and we're going to sync up Monday - it's not "officially > >>>> official" yet but I expect we'll be releasing the code sometime next > > week. > >>> That's great news! > >>> > >>>> Rainer, this is both input and output modules for zeromq, using czmq > >>>> (they're much cleaner than the first ones we wrote against zmq 2 that > > are > >>>> on github currently). If you're ok with it, I'll send the diffs off of > >>>> head to you hopefully next week. > >>> Sure, pls do. I'll see that things get smoothly integrated this time. > > Ping me > >>> if not ;) > >>> > >>> Rainer > >>>> Brian > >>>> > >>>> On Thu, May 10, 2012 at 10:23 AM, Pablo Chacin > >>>> <[email protected]>wrote: > >>>> > >>>>> 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- > >>>> **<https://github.com/**aggregateknowledge/rsyslog-**> > >>>>>>> zeromq<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.ne > >>> t/* > >>>> *mailman/listinfo/rsyslog> > > <http:**//lists.adiscon.net/mailman/**listinfo/rsyslog<http://lists.adiscon.n > >>> et/ > >>>> mailman/listinfo/rsyslog> > >>>>>>> http://www.rsyslog.com/****professional- > >>>> services/<http://www.rsyslog.com/**professional-services/> > >>>>>>> <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://lists.adiscon.net/ > >>> mail > >>>> man/listinfo/rsyslog> > >>>>>> http://www.rsyslog.com/**professional- > >>>> services/<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://lists.adiscon.net/ > >>> mail > >>>> man/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 > >>> _______________________________________________ > >>> 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 > > _______________________________________________ > > 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 _______________________________________________ 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
