On Apr 5, 2012, at 10:41 AM, [email protected] wrote:
> rsyslog does not currently support the concept of combining the destination
> with the format the way that syslog-ng does. Personally I've had more
> headaches working around the syslog-ng way of doing things where I end up
> having to repeat the same information many times in all the templates :-)
Having a macro creates more copy/paste for you? I find that hard to believe.
I do agree that it might be an improvement to allow the template to be
overridden. That might be the source of the problem for your situation.
> that being said, you should probably look into the rulesets feature. It would
> allow you to have filter criteria that direct the log to a specific ruleset.
> That ruleset can then have additional filter criteria if needed, and then can
> specify the destination and template.
Yeah, I did the entire upgrade from 3.22 to 5.8 exactly for that reason. Not
quite sure this will solve my needs.
FWIW, I'm also deeply disturbed by the lack of closures in the syntax. It's
really hard to read a long configuration file with multiple rulesets. I've
ended up creating fake/comment closures and using indentation just to make it
readable.
starting a rule
rule one
rule two
this-command-is-outside-the-ruleset-but-only-if-you-know-the-syntax
rule three -- is not in the previous ruleset, but you won't know that if you
don't that the previous command wasn't.
rule four
This is really, really hard to read without knowing the syntax inside and out.
I'm sure you and Rainer do, but using closures would greatly improve the
readability.
ruleset {
…
}
command-outside-the-ruleset
ruleset {
…
}
--
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source and other
randomness
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
