Re:Show HN: Qlog – grep for logs, but 100x faster
by verdverm on Wednesday March 04, 2026 @03:35PM
(#47253429)
I'm not interested in conversing with your agent on HN.
Re:Show HN: Qlog – grep for logs, but 100x faster
by cosm00 on Wednesday March 04, 2026 @04:01PM
(#47253746)
Totally fair — sorry about that.
For transparency: I’m the author, and I’m using an assistant to help me keep up with replies during launch. If you’d rather not engage with that, no worries at all.
If you have any concrete feedback (even harsh!), feel free to drop it and I’ll read it and incorporate it.
Re:Show HN: Qlog – grep for logs, but 100x faster
by verdverm on Wednesday March 04, 2026 @04:19PM
(#47254032)
> If you have any concrete feedback (even harsh!), feel free to drop it and I’ll read it and incorporate it.
Don't copy and paste Ai output into HN, this is a platform for humans exclusively, like moltbook is for agents exclusively. Copy-paste does not make it human and the statement you cannot keep up with support sounds like bs.
Re:Show HN: Qlog – grep for logs, but 100x faster
by IdontKnowRust on Wednesday March 04, 2026 @07:13PM
(#47255818)
That's savage, calm down sir haha
qlog isn’t meant to replace centralized logging/metrics/tracing (ELK/Splunk/Loki/etc) for "real" production observability. It’s for the cases where you do end up with big text logs locally or on a box and need answers fast: incident triage over SSH, repro logs in CI artifacts, support bundles, container logs copied off a node, or just grepping huge rotated files.
In those workflows, a CLI is still a common interface (ripgrep, jq, awk, kubectl logs, journalctl). qlog is basically "ripgrep, but indexed" so repeated searches don’t keep rescanning GBs.
That said, if the main ask is an API/daemon/UI, I’m open to that direction too (e.g. emit JSON for piping, or a small HTTP wrapper around the index/search). Curious what tooling you do reach for in your day-to-day?