ML condenses billions of logs into a tiny snapshot your LLM can debug

Details

External ID

48578324

Source

HN

Company

—

Product

ML condenses billions of logs into a tiny snapshot your LLM can debug

Website domain

github.com

Launched

June 17, 2026

Cohort

—

Upvotes

13

Upvotes percentile

0.6707650273224044

Tags

—

Fetched at

Sept. 7, 2026, 9:26 p.m.

Updated at

Sept. 7, 2026, 9:26 p.m.

Description

Hi HN, I'm Kaushik, and I built Rocketgraph. I believe that while other spaces have caught up to the AI wave, the observability space is still lagging behind, using the same tools and dashboards that we use to analyse logs from human-written code. But now the code is written and debugged by AI, so we need to rethink how we do observability where the observer itself is an AI.The problem that I run into is when an alert fires, I have to manually check the Grafana dashboards and write LogQL queries, which is pretty much like greping. But production usually breaks due to a schema mismatch, or a DB connection issue or a log line that I haven't seen before that's buried under millions of log lines. Much worse, the alert never fires, and I don't know when to grepRocketgraph fixes that. It turns your logs into patterns by fingerprinting them, then uses ML to anomaly score them by features like frequency, text similarity and other vectors. So, usually this condenses a million logs into 200-300 patterns with anomaly scores and feature vectors that your LLM can easily analyse without sending the entire firehose. This runs at specific points in time, so it's like an online anomaly detection based on logs.Some companies do anomaly detection on metrics, but this is done for logs.Other approaches in this space bolt an AI on top of existing Grafana dashboards, but it's the same thing as manually greping with extra steps.Please check out the example setups to host it locally and run it on your log files. Let me know what you guys think!

• Source listing
• Website