For some hours, I am fighting with parts of rsyslog design around 2006 (or so): initially, we
thought that all actions will be terminated by canceling their thread
WHEN they not shutdown within the queue shutdown timeout. Then, we saw
that it was better to at least try it cooperatively (cancellation is
still required if that does not work). Now, with imrelp, I have a
situation where I need to pass some information down to librelp when it comes to termination. Supposedly a very simple thing to do (a single call). ... unfortunately, the interface does not provide access to the action in question.
Hopefully, I finally found a work-around, via a "terminate immediately" pointer so far in use internally for the action engine. We'll see...
Subscribe to:
Post Comments (Atom)
simplifying rsyslog JSON generation
With RESTful APIs, like for example ElasticSearch, you need to generate JSON strings. Rsyslog will soon do this in a very easy to use way. ...
-
Did you ever use TCP to transfer syslog reliably? And do you think that makes you immune against message loss? If so, it's time to think...
-
I gave an invited talk on this topic at LinuxTag 2013 in Berlin. I was originally asked to talk about "rsyslog vs. journal", but r...
-
As most of you know, rsyslog permits to pull multiple lines from a text file and combine these into a single message. This is done with the ...
No comments:
Post a Comment