[HN Gopher] Show HN: Qlog - grep for logs, but 100x faster
       ___________________________________________________________________
        
       Show HN: Qlog - grep for logs, but 100x faster
        
       I built qlog because I got tired of waiting for grep to search
       through gigabytes of logs.  qlog uses an inverted index (like
       search engines) to search millions of log lines in milliseconds.
       It's 10-100x faster than grep and way simpler than setting up
       Elasticsearch.  Features: - Lightning fast indexing (1M+ lines/sec
       using mmap) - Sub-millisecond searches on indexed data - Beautiful
       terminal output with context lines - Auto-detects JSON, syslog,
       nginx, apache formats - Zero configuration - Works offline - Pure
       Python  Example: qlog index './logs/*/*.log' qlog search "error"
       --context 3  I've tested it on 10GB of logs and it's consistently
       3750x faster than grep. The index is stored locally so repeated
       searches are instant.  Demo: Run `bash examples/demo.sh` to see it
       in action.  GitHub: https://github.com/Cosm00/qlog  Perfect for
       developers/DevOps folks who search logs daily.  Happy to answer
       questions!
        
       Author : cosm00
       Score  : 5 points
       Date   : 2026-03-04 20:17 UTC (2 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | losalah wrote:
       | maybe release an npm package for it as well. However, nice tool
       | honestly!
        
         | cosm00 wrote:
         | Good idea -- thanks!
         | 
         | Right now qlog is a Python CLI, so the cleanest "npm" story is
         | probably a small wrapper package that installs qlog
         | (pipx/uv/pip) and shells out to it, so Node projects can do
         | `npx qlog ...` / `import { search } from 'qlog'` without
         | reimplementing the indexer.
         | 
         | A native JS/TS port is possible, but I wanted to keep v0.x
         | focused on correctness + format parsing + index compatibility
         | first.
         | 
         | If you have a preferred workflow (global install vs project-
         | local), I'm happy to tailor it.
        
       | verdverm wrote:
       | This is not how DevOps folks think about logs, no way a cli based
       | tool would ever be used.
        
         | cosm00 wrote:
         | Totally fair pushback.
         | 
         | 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?
        
           | verdverm wrote:
           | I'm not interested in conversing with your agent on HN.
        
             | cosm00 wrote:
             | 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.
        
               | verdverm wrote:
               | > 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.
        
       | BorisMelnik wrote:
       | I spend a lot of time auditing access logs and use grep a lot -
       | will try this
        
         | cosm00 wrote:
         | Awesome -- thank you!
         | 
         | Access logs were one of the main motivations (lots of repeated
         | queries like IP/user-agent/path/status). If you try it, two
         | tips:
         | 
         | 1) Index once, then iterate on searches: qlog index
         | './access*.log' qlog search 'status=403'
         | 
         | 2) If you're hunting patterns (e.g. suspicious UAs or a
         | specific path), qlog really shines because it doesn't have to
         | rescan the whole file on each query.
         | 
         | If you run into anything weird with common log formats
         | (nginx/apache variants), feel free to paste a few sample lines
         | and I'll make the parser more robust.
        
       ___________________________________________________________________
       (page generated 2026-03-04 23:01 UTC)