4 ms·
JSON encoded logs are really only useful if you’re putting them into something like splunk. The problem with splunk is that it’s way less expressive than perl,
by hedora 6y ago
JSON encoded logs are really only useful if you’re putting them into something like splunk.
The problem with splunk is that it’s way less expressive than perl, grep, etc, so there are certain useful analyses that simply can’t be run.
To work around that, I see applications duplicate information over and over in their log output.
The end result vs text files is a 2x blow up because of JSON, then a 5-10x blow up because of splunk.
It’s not hard to implement a distributed log processor on top of ssh, and I think open source solutions exist. I don’t know why more companies don’t do that.
As a side benefit, your log files stay human readable. In addition to being more flexible, in practice, the result is something like an order of magnitude cheaper and faster than splunk.