correct, the rsyslog config is not a programming language
what sort of lookups are you trying to create?
David Lang
On Fri, 17 Feb 2023, Mariusz Kruk via rsyslog wrote:
Date: Fri, 17 Feb 2023 16:13:29 +0100
From: Mariusz Kruk via rsyslog <rsyslog@lists.adiscon.com>
To: Dimi Onobodies via rsyslog <rsyslog@lists.adiscon.com>
Cc: Mariusz Kruk <k...@epsilon.eu.org>
Subject: [rsyslog] Non-message based looping
Just double-checking.
Please confirm that I see it right and there is no way of "looping" outside
of the message processing mechanism. I mean - if I have several dozens of
lookup files I have to explicitly create those lookups one by one, I can't do
a "loop" over some set of names to automatically create those lookups, right?
And on a similar note - I can't dynamically create values for some
configuration parts like - for example - input name. Use case - same config
deployed over several hosts and I want to have inputs named differently so
that when I capture stats I can easiliy distinguish between the nodes. I
suppose provisioning tool like ansible/chef/puppet is needed here, right?
Best regards and have a great weekend ;-)
MK
_______________________________________________
rsyslog mailing list
https://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
https://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.
