zincobserve VS lnav

Take a look at https://github.com/zinclabs/zincobserve or Zinc cloud It has logs, metrics, traces, dashboards, alerts, functions and more.

For some reason if you do not want to have the complexity of log forwarders you could simply send the json logs using http them to log files in /var/lib/docker/containers . You would then configure vector/fluentbit to send it to appropriate centralized log search tool. A good light weight tool for self hosting would be - https://github.com/zinclabs/zincobserve . From what you have mentioned I think you would rather prefer the cloud service which you can access at https://zinc.dev/

shell wget https://github.com/zinclabs/zincobserve/releases/download/v0.4.4/zincobserve-v0.4.4-linux-amd64-musl.tar.gz tar -zxvf zincobserve-v0.4.4-linux-amd64-musl.tar.gz ./zincobserve

ZincObserve for logs, metrics, traces and dashboards - https://github.com/zinclabs/zincobserve

We are building long term storage for prometheus. Actually we are building an unified system for logs, metrics and traces - see https://github.com/zinclabs/zincobserve . We are working on implementing promql query interface for ZincObserve. We would love to get community feedback on which functions should we prioritize first - https://github.com/zinclabs/zincobserve/issues/582

The Logfile Navigator (https://lnav.org) is a log file viewer/merger/tailer for the terminal. It has some advanced UX features, like showing previews of operations and displaying context sensitive help. For example, the preview for filtering out logs by regex is to highlight the lines that will be hidden in red. This can make crafting the right regex a bit easier since the preview updates as you type. lnav also has some simple bar charting abilities, so you can visualize the results of SQL queries made against the log messages.

See https://lnav.org for a powerful mini-ETL CLI power tool; it embeds SQLite, supports ~every format, has great UX and easily handles a few million rows at a time.

The code base seems like a good reference as a small Python project.

My fav option in this class of apps: https://lnav.org/ It lets you use journalctl with pipes as requested here: https://github.com/Textualize/toolong/issues/4

For local development, I cannot recommend lnav[1] enough. Discovering this tool was a game changer in my day to day life. Adding comments, filtering in/out, prettify and analyse distribution is hard to live without now.

I don't think a browser tool would fit in my workflow. I need to pipe the output to the tool.

[1] https://lnav.org/