On 10/23/2013 03:31 PM, David Lang wrote:
On Wed, 23 Oct 2013, Erik Steffl wrote:
On 10/22/2013 11:05 PM, David Lang wrote:
On Tue, 22 Oct 2013, Erik Steffl wrote:
so is the use case that I presented a valid one for usage of global
variables? The use case I have in mind is having variables set up in
one of the files in /etc/rsyslog.d/ then use them in templates. It
seems to me these should be global variables (even though they are
pretty much constant, i.e. they are only initialized, never changed
afdterwards). This is a somewhat different use case than counters that
other people mentioned (different from the point of vier why we need
the global variables, same from the implementation viewpoint)
If I am understanding you correctly, absolutly.
the question is what sets these variables. If they are set and not
changed by future messages (or at least, not changed for a significant
time period) then that seems like the perfect use case for global
variables.
yes, in our case these variables are essentially constants, something
like:
set $!logOrigin!cluster = "clusterName";
as part of our deployment we split rsyslog config into one file that
has these variables (file is generated during deployment, mostly things
like cluster name) and another part that is essentially same for all
installations (templates, inputs, outputs etc. that use the variables
from the other file).
erik
_______________________________________________
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.
