This is just a quick note that systemd is doing really well in providing logging right from the system startup, even when no syslogd is running. The magic is that messages are put into the kernel log, where the (later started) syslogd can pull them from. Unfortunately, there are some downsides from this mode, and we are currently working to solve them. For more details, please follow this thread:
http://lists.freedesktop.org/archives/systemd-devel/2011-March/001558.html
I guess the remaining issues will be settled soon, as almost everything is in place and I just need to add some additional parsing logic to rsyslog. Due to the conference next week, I may need one extra week to complete that. All of this work will be part of the newly opened v5-devel (and above).
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