3 ms·
You can make it all some kind of json object and use plenty of tools to parse. I think text is really awesome though. You can read it with any editor and there
by 7thaccount 2y ago
You can make it all some kind of json object and use plenty of tools to parse.
I think text is really awesome though. You can read it with any editor and there are a zillion easy to learn Linux tools like grep, cut, awk...etc for interactively creating a oneliner in a short amount of time that you can use to get what you want out of the text. I used to have a bunch of those when I was in charge of some applications on a Linux server. Text is very universal and I'm not just talking about log files.
- imglorp 2y agoMissed opportunity: it would really be a different conversation if, around 1980 or so, syslog(3) became a standard and was adopted at that time by everyone. Logs really would be in much the same format and you could use simple text tools on them. After you agreed on the standard parts timestamp, facility, and level, you'd still need some standard structure for the variant message parts though, which is where json is good: it's arbitrarily deep. https://www.man7.org/linux/man-pages/man3/syslog.3.html https://www.man7.org/linux/man-pages/man3/syslog.3.html