There are so many cases where someone needs to override something in the default
template (bad hostname, bad programname, etc) that having to create a custom
tempalte for each thing gets to be a hassle.
I'd like to propose that we have some templates that are exactly the same as the
default ones, but that look (for example) for $.hostname and if it's set, use
that instead of $hostname. Have this setup for everything in the default
template set.
I don't know if we dare to do this to the existing templates, or if these would
need to be new templates. If new, could they be built-in, or should they be
string modules that are explicitly loaded (and if string modules, could they
override the default definitions??)
I also think that we need to have a couple of JSON based templates:
file and forwarding versions of the base templates that use $! for the message
body instead of $msg (do we need a version with '@cee:? or can we modify
mmjsonparse to have an option to no longer require that now that cee is dead?)
and finally a template that is just "$!\n" to use when forwarding to other tools
(nxlog, logstash, etc)
thoughts?
David Lang
_______________________________________________
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.
