[rsyslog-notify] Forum Thread: Re: rsyslog blocked when backend database down - (Mode 'reply')

[noreply at adiscon.com]

User: dlang 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=25002#p25002

Message: 
----------
This is what action queues are for. Add a queue to the database calls (or
put the two database calls in a ruleset and make a queue for that ruleset)
and it will decouple the database output from the file output.

What's going on is that rsyslog is taking a log message and going through
all the rules delivering it. If it can't deliver it, it keeps trying until
the configurable timeout, and won't try to process other messages in the
meantime.

by creating a queue for the action (or a ruleset containing a few actions),
the rsyslog thread that i'm talking about above delivers the message to the
queue and continues on (at least as long as there is room for it in the
queue)