>From reading the call documentation [1] I understand the call ruleset can
be used to independent parallel message processing bypassing the standard
queue-lanes behavior [2].
Is this my assumption correct?
Want to come with configuration that will prevent unavailability of one
destination to block message processing of other actions.
Will the ruleset-linux use the default mainQ on input if not configured
with queue.* options?
something like this (one input only):
input(type="imtcp" ... ruleset="ruleset-linux")
ruleset(name="ruleset-linux"){
call ruleset-localstore
call ruleset-forward1
call ruleset-forward2
}
ruleset(name="ruleset-localstore"){
action(type="omfile" asyncWriting="on" file="/var/log/lin-all.log"
template="fileStoreTemplate")
}
ruleset(name="ruleset-forward1"){
action(type="omfwd" ....
queue.*=...
)
}
ruleset(name="ruleset-forward2"){
action(type="omfwd" ....
queue.*=...
)
}
[1]
https://www.rsyslog.com/doc/v8-stable/rainerscript/rainerscript_call.html
[2] https://www.rsyslog.com/doc/v8-stable/whitepapers/queues_analogy.html
--
Peter
_______________________________________________
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.
