←back to thread

134 points dimonomid | 2 comments | | HN request time: 0.001s | source

For more background and technical details, I wrote this up as well: https://dmitryfrank.com/projects/nerdlog/article
Show context
Zopieux ◴[] No.43752026[source]
journalctl is mentioned once in the landing page and it seems to imply that journalctl is not supported per se, as logs need to be stored plaintext to legacy syslog (?).

I do not want to store plaintext logs and use ancient workarounds like logrotate. journald itself has the built-in ability to receive logs from remote hosts (journald remote & gateway) and search them using --merge.

replies(2): >>43752090 #>>43752347 #
1. tstack ◴[] No.43752090[source]
The article makes it sound like it uses various command-line tools (bash/awk/head/tail) to process the logs. So, I imagine it's not a huge leap to extend support to using journalctl to do that work instead.
replies(1): >>43753262 #
2. mamcx ◴[] No.43753262[source]
One small hitch I found is that this kind of tools are fixes in what to process, so for example I can't use them for structured logging. If it has an escape hatch where I can supply my own pipe (for example `process = 'vector ....'`) then it will be enough.