nt: Monday, January 07, 2013 11:54 PM
> > To: rsyslog-users
> > Cc: Rainer Gerhards
> > Subject: Re: [rsyslog] working with list templates
> >
> > David - no, I have batch processing working already as part of the
> > patch I'm working on. That part was actu
> -Original Message-
> From: Brian Knox [mailto:bri...@talksum.com]
> Sent: Monday, January 07, 2013 11:54 PM
> To: rsyslog-users
> Cc: Rainer Gerhards
> Subject: Re: [rsyslog] working with list templates
>
> David - no, I have batch processing working already as
On Mon, 7 Jan 2013, Brian Knox wrote:
David - no, I have batch processing working already as part of the patch
I'm working on. That part was actually pretty easy using rewriting the
plugin to properly use dequeuebatchsize, etc.
The issue is that the way the redis protocol constructs commands m
David - no, I have batch processing working already as part of the patch
I'm working on. That part was actually pretty easy using rewriting the
plugin to properly use dequeuebatchsize, etc.
The issue is that the way the redis protocol constructs commands means that
I can't just put a message payl
On Mon, 7 Jan 2013, Rainer Gerhards wrote:
The more I read, the more I think what you really want is a single string. Are
we just missing a shell escape property option?
I think that what he is wanting is a single string for each message, but he
wants to shift to processing a batch of messa
y(name="msg")
>> }
>>
>> So that from the plugin side, I can get "LPUSH", "queue_key", and the
>> message from the msg property, and their lengths - then I could easily
>> use the ArgV version of the hiredis command runners and formatters.
>
sure I did get this straight: This means you always include one
field only?
Rainer
-Original Message-
From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog-
boun...@lists.adiscon.com] On Behalf Of Brian Knox
Sent: Monday, January 07, 2013 5:18 PM
To: rsyslog-users
Subject: Re: [rsyslog]
gt; To: rsyslog-users
> Subject: Re: [rsyslog] working with list templates
>
> So - in my case I do not believe I need field names. Redis is more of
> a
> k/v store than a document store like mongo (although it supports more
> data
> structures than simply key / value, like set
On Mon, Jan 7, 2013 at 10:59 AM, Rainer Gerhards
wrote:
> > -Original Message-
> > From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog-
> > boun...@lists.adiscon.com] On Behalf Of Brian Knox
> > Sent: Monday, January 07, 2013 2:11 PM
> > To: rsyslog-u
> -Original Message-
> From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog-
> boun...@lists.adiscon.com] On Behalf Of Brian Knox
> Sent: Monday, January 07, 2013 2:11 PM
> To: rsyslog-users
> Subject: Re: [rsyslog] working with list templates
>
> Happy M
ide the plugin.
>>>> Not the template type specifies what you get, but the plugin asks the
>>>> engine. What you look for is JSON passing mode (or maybe array passing).
>>>> Ommongodb should help you, else ping me early next week.
>>>>
>>>> Rainer
>&
array passing).
>>> Ommongodb should help you, else ping me early next week.
>>>
>>> Rainer
>>>
>>> -Original Message-
>>>> From:
>>>> rsyslog-bounces@lists.adiscon.**com[mailto:
>>>> rsyslog-
>>>> bou
rking with list templates
Hi Radu! Thanks for the link, but I already know how to work with list
templates from a conf perspective. I'm looking for good examples of
accessing that data from code in an output plugin. Currently my plugin
simply does this in CODESTARTdoAction:
CHKiRet(writeHiredi
@lists.adiscon.com
Subject: Re: [rsyslog] working with list templates
Hi Radu! Thanks for the link, but I already know how to work with list
templates from a conf perspective. I'm looking for good examples of
accessing that data from code in an output plugin. Currently my plugin
simply does th
nal Message-
> From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog-
> boun...@lists.adiscon.com] On Behalf Of Brian Knox
> Sent: Thursday, January 03, 2013 2:22 PM
> To: rsyslog@lists.adiscon.com
> Subject: Re: [rsyslog] working with list templates
>
> Hi Radu! Th
I'll dig around in the ommongodb output plugin in the meantime and see
what I can learn - I know that one was updated recently so it's probably
a good one to reread. Thanks!
Brian
On 1/3/2013 8:51 AM, Radu Gheorghe wrote:
Yeah, makes sense, but I have no idea how you can do that. I suppose Ra
Yeah, makes sense, but I have no idea how you can do that. I suppose Rainer
can be bugged next week, or maybe someone else knows...
Best regards,
Radu
2013/1/3 Brian Knox
> Hi Radu! Thanks for the link, but I already know how to work with list
> templates from a conf perspective. I'm looking
Hi Radu! Thanks for the link, but I already know how to work with list
templates from a conf perspective. I'm looking for good examples of
accessing that data from code in an output plugin. Currently my plugin
simply does this in CODESTARTdoAction:
CHKiRet(writeHiredis(ppString[0], pData));
No idea how I accidentally hit "reply". So I'm continuing inline...
2013/1/3 Radu Gheorghe
> Hello Brian,
>
> Just to make sure we're not missing the obvious:
> http://www.rsyslog.com/doc/rsyslog_conf_templates.html
>
> Besides that, there are a couple of examples here:
>
http://www.rsyslog.com
Hello Brian,
Just to make sure we're not missing the obvious:
http://www.rsyslog.com/doc/rsyslog_conf_templates.html
Besides that, there are a couple of examples here:
2013/1/3 Brian Knox
> I've been working on some improvements for the omhiredis output plugin this
> week. I think I've come
I've been working on some improvements for the omhiredis output plugin this
week. I think I've come up with a better way of combining templates with
redis command formatting. In order to do this, I need to, given a list
style template, get the number of elements in the list and the length of
each
21 matches
Mail list logo
