3 ms·
According to the design document [0] the primary reason is this problem with syslog: "Binary data cannot be logged, which in some cases is essential (Examples:
by qznc 13y ago
According to the design document [0] the primary reason is this problem with syslog: "Binary data cannot be logged, which in some cases is essential (Examples: ATA SMART blobs or SCSI sense data, firmware dumps)"
Also, instead of lines of utf8 strings, the systemd format is extensible. This means applications can store additional meta data without some syslog-grepping script breaking.
[0] https://docs.google.com/document/pub?id=1IC9yOXj7j6cdLLxWEBAGRL6wl97tFxgjLUEHIX3MSTs https://docs.google.com/document/pub?id=1IC9yOXj7j6cdLLxWEBA...
- jzwinck 13y agoI can totally relate to wanting to extend log output without (too much) fear of breaking consumers with every change. I was excited to read http://tools.ietf.org/html/rfc5424 http://tools.ietf.org/html/rfc5424 where section 6.3 describes structured data storage in syslog. However, I have yet to see anyone using this in production, and I haven't had the opportunity to try it myself.