Hacker News new | past | comments | ask | show | jobs | submit login

I got excited reading your second link (https://www.loggly.com/blog/why-journald/ ), but from it:

> Sadly, journald does not come with a usable remote logging solution. The program systemd-journal-remote is more of a proof-of-concept than an actually useful tool, lacking good authentication among other things. Third-party packages such as journald-forwarder send journal logs to Loggly directly but are very new and experimental. As such, remote logging still has to go through existing syslog implementations and the syslog protocol and therefore cannot make use of many of the additional features of journald, in particular the structured data.

Anyone on HN cracked structured remote centralised logging with journald? Unstructuring everything for syslog, dealing with pretend stuff like uucp, fax and user3, and restructuring again seems like a kludge.

Also: weird loggly don't sieze the opportunity and make something that works with their service without the limitations they're writing about.




It's not as difficult as it's made out to be. We run a systemd service that does something like this:

   journalctl -f -o json | send-logs remote-server


And there are also tools like https://github.com/aiven/journalpump


What is send-logs and what protocol does it use?




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: