惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
Visual Studio Blog
Engineering at Meta
Engineering at Meta
月光博客
月光博客
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
T
Tailwind CSS Blog
博客园 - Franky
The GitHub Blog
The GitHub Blog
大猫的无限游戏
大猫的无限游戏
The Cloudflare Blog
B
Blog RSS Feed
云风的 BLOG
云风的 BLOG
小众软件
小众软件
罗磊的独立博客
Microsoft Azure Blog
Microsoft Azure Blog
I
InfoQ
美团技术团队
H
Hackread – Cybersecurity News, Data Breaches, AI and More
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
V
V2EX
C
Check Point Blog
WordPress大学
WordPress大学
博客园 - 【当耐特】
博客园 - 司徒正美
D
Docker

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
How I Built AI-Powered Log Triage in Go (and Made It 100x...
Aryan Goyal · 2026-06-16 · via DEV Community

Aryan Goyal

I built LogSense to do AI root-cause analysis on production errors without dashboard fatigue or runaway token costs.

Early access is open — join the waitlist at Logsense

I got tired of two things:

  1. Paying premium observability prices for noisy error triage
  2. “AI analysis” tools that still process duplicate stack traces like they’re unique incidents

So I built LogSense.

LogSense = drop in an API key, get AI root-cause analysis on every error. No dashboards. No rules.

The core idea is simple:

Same error 1000 times = 1 LLM call.

That one design choice changed the economics completely.


The Problem With Naive AI Log Analysis

Most pipelines treat every incoming log line as independent work.

If one bug explodes during an outage, you might see thousands of near-identical stack traces.

Naive flow:

  • ingest logs
  • call LLM per event (or per tiny batch)
  • pay repeatedly for the same root cause

That gets expensive fast, and signal quality drops because you’re summarizing noise, not incidents.


The Architecture I Built (Go + Gin + RabbitMQ + K8s)

At a high level:

  1. Ingest: app logs arrive via API
  2. Fingerprint: normalize + hash error signatures
  3. Deduplicate: group repeated errors by fingerprint window
  4. Analyze once: one LLM call per unique fingerprint
  5. Fan out results: attach RCA + remediation hints to all grouped events

This means volume spikes do not linearly increase AI cost.


Fingerprinting: The Cost + Signal Moat

The fingerprinting layer does the heavy lifting.

For each error event, LogSense normalizes unstable fields:

  • timestamps
  • UUIDs/request IDs
  • dynamic numbers/IDs
  • environment-specific noise

Then it hashes the stable structure (message + stack shape + service context).

So these:

  • panic: nil pointer at user_id=12345
  • panic: nil pointer at user_id=67890

collapse into the same canonical signature if they’re the same underlying defect.

Result: one root-cause analysis for one issue, regardless of repetition count.


Why This Matters in Production

During incident windows, repeated errors dominate traffic.

Without dedup, your AI bill scales with chaos.

With dedup, your AI bill scales with unique failures.

That’s the model LogSense is built around:

  • faster triage
  • better incident grouping
  • predictable AI spend

Example Flow (Pseudo-Go)

func process(event LogEvent) {
    normalized := normalize(event)
    fp := fingerprint(normalized)

    if cache.Exists(fp) {
        cache.IncrementCount(fp)
        return
    }

    analysis := llm.Analyze(buildPrompt(normalized))
    cache.Store(fp, analysis)
    publish(analysis)
}

Early access is open — join the waitlist at Logsense