3 ms·
This falls under "good intention, but not well planned out" IMO. Single line logs are MUCH easier to process with text-oriented tools, which is why they've stuc
by zdw 15y ago
This falls under "good intention, but not well planned out" IMO. Single line logs are MUCH easier to process with text-oriented tools, which is why they've stuck around for so long.
This solves the encoding problem, but not the "how do I read/search it" problem, which is kicked down the line to other tools. And having a different format for every daemon is just a new problem.
I'd look at how others have dealt with the problem - for example, Logstash, which is a log parsing and movement engine:
http://logstash.net/docs/1.0.17/learn http://logstash.net/docs/1.0.17/learn
Also, timestamps aren't recommended for storing time data - they're not human readable, and convey less information than something like ISO8601 which covers more edge cases.