On Sat, Dec 14, 2013 at 2:51 PM, RB <[email protected]> wrote: > On Sat, Dec 14, 2013 at 5:24 AM, Rainer Gerhards > <[email protected]> wrote: > > well, technically it's for sure possible, it's just another of these 24h > > things. Technically, it's a question of interface, and insofar of which > > types of modules. Obviously, these will be slower, and how slow is > another > > interface/effort question. > > > > Thinking about this, one could probably also claim the answer is "yes, > you > > can write OUTPUT modules in any language", it's just a doc issue. In > fact, > > omprog can be used as an interface here. It's actually not even a bad > > interface... > > > > Again, something learned ;) > > Probably the cheapest (implementation) "binding" for rsyslog would be > a system() like call. Execute the subprogram with /bin/sh -c and > communicate with structured messages on STDIO. > > > that's exactly what omprog does:
http://www.rsyslog.com/doc/omprog.html It's, however, a seldom-used output and thus it may require some tweaking if it gets seriously used. Note that it offers full template support, so the output script can accept messages in almost all formats (inclusing JSON). Rainer _______________________________________________ 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 NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
