On Tue, 24 Apr 2018, putcha narayana wrote:
😊 wasn't me. so that makes 2 of us asking for same lol.
i think, using global variable would have kept the export and backtick options
out of the rsyslogd. But i am sure the support was provided after careful
consideration and requests from others.
the problem you are missing is that modifying the rsyslog engine to allow for
variables (of any kind) instead of constants in these fields will have a
signficant run-time cost, slowing down everyone.
When you are already editing the config file and restarting syslog to implement
your change, why should we suffer the cost of making this a variable?
It's not just the cost of a variable lookup, it's the cost of maintaining a
table of connectons, expiring them, figuring out how to re-use connections, etc.
We do this with filenames using the dynafile mechanism, and it's a significant
enough overhead that it has to be explicitly opted in to each time it's used
(and misuse of this feature and it's settings is a very common cause of
horrifically bad performance)
sending to a wide variety of destinations is just not that common a use case,
and when people are doing it (high volume systems distributing load), they don't
want to pay the overhead. And even there, it's very unusual for there to be more
than a handful of destinations, so simple if-then-else nested outputs handle the
job.
_______________________________________________
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.
