if you run mmjsonparse on the message it will populate $! variables. Then you
can just add whatever variables you want to the tree and when you output $! in a
template it will output all the variables (including yours) in JSON.
David Lang
On Tue, 2 Dec 2014, Brian Knox wrote:
The other option we're discussing is using a template on a ruleset that is
guaranteed to contain only @cee formatted messages, and using some trickery
with a list template and position.relativetoend to chop the message so we
can inject the json attribute via a constant / property pair - but we
wanted to see if there was a cleaner way of doing it first!
Brian
On Tue, Dec 2, 2014 at 3:59 PM, Brian Knox <[email protected]> wrote:
We have a case where we are receiving messages in @cee: format, and would
like to add a sequence variable generated via mmsequence to the message.
Before I spend too much time digging into this I wanted to ask if, using
some template hackery and json subtrees, this is something that sounds
possible - and if maybe someone else was already doing it.
Thanks!
Brian
_______________________________________________
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.
_______________________________________________
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.
