| |||||||||||||
The Journal - a proposed syslog replacementThe Journal - a proposed syslog replacementPosted Nov 18, 2011 18:00 UTC (Fri) by quotemstr (subscriber, #45331)In reply to: The Journal - a proposed syslog replacement by cmorgan Parent article: The Journal - a proposed syslog replacement
> Data is split into fields, making it easier to analyze programmatically.
syslog lines are broken into fields too. How often do you need to break down these logs _further_? The theoretical benefit of programmatic analysis doesn't seem worth the trouble of changing everything and the persistent trouble of a binary log format.
(Log in to post comments)
The Journal - a proposed syslog replacement Posted Nov 18, 2011 18:05 UTC (Fri) by cmorgan (guest, #71980) [Link]
> syslog lines are broken into fields too. How often do you need to break down these logs _further_? The theoretical benefit of programmatic analysis doesn't seem worth the trouble of changing everything and the persistent trouble of a binary log format.
Some people do have a use for breaking the data down further. Being able to organize log entries by nested modules/submodules.
Try to have an open mind. systemd was a great idea for several reasons. So much so that most distributions have adopted or plan to adopt it. If this idea solves issues it too will be adopted. We can't forget that sometimes things evolve. In this case, would you care as much if a tool would provide you with the same looking output that you see today? What difference would there be in that case? Everyone can win (or at least break even).
|
|||||||||||||