3 ms·

I tried this, but, the only way to "use" them is to pay absurd amounts of money for cloud tools or setup complex grafana + ... things. Using them from the comm

• rob-olmos 6y ago
  If the logs are stored in JSON, the jq tool can be used. I understand it's more complicated that grep for certain structures, but also having a library of jq filters for the app may be useful and can be shared.
  • mamcx 6y ago
    But that requiere to learn extra stuff that is not the normal flow: Locate that part of the log or scan it quickly.
• gbuk2013 6y ago
  Not at all - grep piped to jq works like a charm - I have made reports using that in the CLI wrapped in a Makefile that were exec friendly. And there are other tools like gron for example. And if you are building something serious and with some sort of scale then you will need to have something like ELK stack anyway to aggregate and display data - there is no getting away from that. Working with unstructured logs however is a mess. Perl / Awk helps of course but it is a lot of extra effort. And in the end, at scale you will just be writing those scripts to turn that mess into structured data to feed into that same ELK stack anyway.
• wsargent 6y ago
  Off the top of my head: https://github.com/koenbollen/jl https://github.com/koenbollen/jl https://github.com/brocode/fblog https://github.com/brocode/fblog https://github.com/gistia/json-log-viewer https://github.com/gistia/json-log-viewer https://github.com/otros-systems/otroslogviewer https://github.com/otros-systems/otroslogviewer