Adding feature to allow zerolog to output SystemD compatible binary logs.

[rs]

Adding feature to allow zerolog to output SystemD compatible binary logs.

[toravir]

From what i read, journalD looks like a Key:Value logging mechanism - Key & Value are both strings. Sent to the systemD which will compress it and store it (log rotate it etc). There are methods to retrieve it / query it etc..

Any client of journalD will need to send a Priority + Message + (Key+Value) Pairs - over a unix socket to journalD or systemD.

Is my understand right ?? If so, this will be another kind of writer - like consoleWriter.. instead of formatting the log message for printing to console - this journaldWriter will convert logs to journalD format (Prio + Msg + KV Pairs) and send it to systemd ??

CBOR (binary) encoding does not add much value to it - since the logs are to be converted to strings to be sent to journalD.

[rs]

My understanding is that journald fields is a flat structure with no typing support. We might just want to create a writer that would set the priority field and set the message field with the JSON payload.

[toravir]

I have written a writer that will write to journald. I tested it by writing an example program. I could use some ideas on how to write a go-test to add tests. First cut diff: toravir@163f52c

[rs]

Fixed by #57

[wvh]

Note to the OP that the way you log to journald (redirecting stdout/stderr or using its socket) is not related to the logs being persistent. If you want journald logs to be persistent, you need to configure it so by setting the Storage option to persistent or creating the output directory if it's set to auto. Otherwise they will be in memory only (for most distributions) and will be lost on reboot.