Hello, I am trying to wrap my head around what best practices are in writing templates and customizing rsyslog for my application. It's a bit confusing in the various sources online what is deprecated and what is current best approach.
Ideally, I would imagine it would be supported for me to have syslog messages coming in that simply contain a list of json name value pairs: "logfoldername": "logfoldervalue", "name2": "value2", "name3": "value3", ... So I'm trying to figure out how I can write a template that can write to a folder that was specified in the message itself. How can I extract a named variable from the message and use it in the output format? Pseudo of what I mean: *.* /var/log/logfoldervalue # where the last folder is from the value of the 'logfoldername' variable in the above JSON Is there some sort of built in support for JSON? My goal is to have something generalized where I can control behaviour from the sending application to categorize log messages. Perhaps there is an easier way to achieve this--open to suggestion! Thanks! ---------------------------- Albert Meyburgh _______________________________________________ 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.
