On Wed, 6 Mar 2019, Rainer Gerhards wrote:
Seems the same is valid for in-memory part of the queue. Does it make sense
or would it be possible to implement some special mode in which the message
will be "queued" before the variables/templates will be applied (in similar
way the main queue is storing the messages)? Those templates with variables
processing might be applied as a part of dequeueing.
Impossible - you cannot re-create the precise state of the message at
that point. There is too much dynamic. Note that the template is not
stored inside the message object. But variables are - because they
*are* part of the message.
You have no way of knowing what will be done with the message after it's taken
off the queue. Is it just going to be used by one action using a known template?
(If so, it would, in theory, be possible to store the output of the template for
the action to use, but that would be very action specific), or is it going to be
used for dozens of actions that reference different variables, and have other
logic consume the variables.
Queues exist for the main message queue, rulesets, and actions. It's only the
action ones that could, in theory have data thrown away, but the queue logic
doesn't care what's reading from the queue, so it has no way of knowing.
David Lang
_______________________________________________
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.
