The Journal - a proposed syslog replacement
Posted Nov 18, 2011 21:29 UTC (Fri) by
b0ti (guest, #81465)
Parent article:
The Journal - a proposed syslog replacement
I, for one, welcome this. This Journal is finally something that will address all the problems which were already long due to solve.
For example take a look at what's under /var/log/. It has become the trashcan of applications where they can dump their crap. Each and every file there has its own format, they couldn't even use a single time/date format. Anyone who has worked with logs knows that syslog has too many shortcomings, even the new ietf standard does. Converting logs to syslog is a simple but inefficient solution, still how many people are out there converting eventlog and other formats to syslog? Trying to extend syslog and syslogd implementations is not easy when you need to squeeze a much broader concept into an existing format and functionality.
Rather than going this way, I said no thanks. This is why I designed nxlog to support different log formats, transports, etc. I'll likely create nxlog modules to support reading and writing the Journal.
Here are some things which I missed or didn't see in the documentation:
- CEE has put a lot of effort into log standardization. Can't some of this be used in the Journal implementation instead of reinventing the wheel?
- What's the encoding used for messages stored in the Journal? UTF-8?
(
Log in to post comments)
