22.10.2013 12:23, David Lang:
well, the original request that lead to getting global variables added
was to have the contents of one message set a variable that could be
used in processing future messages.
For this use, the current functionality works as-is.
I agree, for me these globals look suitable for changing behaviour on
the fly, based on contents of some messages. Including switching on and
off output actions, changing templates, and so on. All implications are
not so important here, because changes just will happen not in real
time, but sufficiently fast.
22.10.2013 12:10, Rainer Gerhards:
I wonder what are the actual use cases behind the desire to have global
variables in rsyslog. There are two that I know (I describe them very
briefly as they were expressed at length in the past couple of days):
1. counting messages for some reason
2. load-balancing output actions
Number 2 is - I think - a weak one, as this should better go into a
specific facility inside the engine (read: nothing that the admin should
need to emulate in the conf file).
For load-balancing case, it's hard to reproduce all possible features
via a specific facility. How about balancing non-equally between
different nodes? Or balancing between substantially different entities?
Or writing each 1000th message to a specific file for future analysis?
As balancing is new to rsyslog, it is hard to find real real-world
scenarios. All of cases mentioned just above are very likely to me.
--
Pavel Levshin
_______________________________________________
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.
