On Fri, 26 Apr 2013, Gary Foster wrote:
Can I make multiple actions use the same action queue or do I need to have a
discrete queue for every single action?
The particular use case I'm thinking of is similar to this:
if $msg contains 'some match' then {
$ActionQueueType LinkedList
$ActionQueueFileName redis1
$ActionResumeRetryCount -1
action(do a redis INCR on some key)
$ActionQueueType LinkedList
$ActionQueueFileName redis1 # <-- using the same queue file name here
$ActionResumeRetryCount -1
action(do a redis EXPIRE on some key)
}
I want to queue these up in a disk based action queue, but I obviously don't
want the chance of the expire happening before the incr in this case, so I
want to use the same queue for both of them. I'm under the impression that I
can't do that because it will corrupt the disk backed queue if two different
actions use it… so would this be something I would just default back to the
main message queue instead?
I don't think this is the right way to define queues in the V7 world. the queue
commands you are using are the V5 and earlier ones.
With the pre V6 type queue commands, you set them prior to defining the action
(before the IF) and then they take effect for all actions after that until a new
queue is defined. (at least as I understand it)
With the V7 style configs, the queue commands are part of the action statement.
I don't know if there is a way to have the same non-main queue for multiple
actions.
The other thing you could look into is using a ruleset. have the statements you
are showing go to a ruleset that has it's own main queue, then don't do seperate
action queues inside that ruleset.
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.
