Skip to main content

Local AI root-cause analysis for production logs. Nothing leaves your machine.

Project description

logsleuth

Local AI root-cause analysis for production logs. Nothing leaves your machine.

Feed it an incident's worth of logs — gigabytes are fine — and get back a structured root-cause report: symptom, timeline, hypothesis with cited evidence, ruled-out red herrings, next steps. All inference runs locally via Ollama, so you can use it on logs you'd never paste into a cloud AI: they're full of PII, tokens and internal hostnames, and your security team knows it.

$ logsleuth incident.log

## Root cause hypothesis
PostgreSQL connection pool size reduction (from 50 to 10) during deployment.
Confidence: High.
- Deployment log explicitly sets PG_POOL_MAX=10 (line 1316)
- "pg pool timeout" errors start immediately after the deployment
- Latency grew from 56.9ms to 217.9ms (x3.8), idle connections dropped to 0

## Ruled out
- "healthz" noise present before the incident — baseline, not cause
...

Why

  • Your logs never leave the machine. No API keys, no cloud, no data processing agreements, no argument with the CISO. Works air-gapped.
  • It reads all of it. A deterministic preprocessor crunches the full file — deduplicates error patterns, computes numeric trends (heap, latency, disk, queue depths), finds deploys/migrations/flag flips, detects error concentration by node/pod/build — and hands the model a dense evidence pack. No more guessing which 10KB of a 2GB log to paste into a chatbot.
  • It distrusts loud noise. Patterns present since the start of the file are flagged as baseline; the report explicitly lists red herrings it didn't blame.
  • Honest by design. The model is instructed to cite only real lines and to say "insufficient evidence" rather than invent a story.

Benchmark

10 blind scenarios (written after the code was frozen, generators included in bench/): Kafka rebalance storms, expired TLS certs, clock skew, cache evictions after a config change, backup-window IO saturation, connection leaks, third-party rate limiting, NFS-stalled thread pools, bad canaries, flapping health checks.

Result: 8/10 correct root causes with qwen3:8b on a MacBook M1 Pro (16GB), ~80 seconds per analysis. The two misses stopped one causal hop short of the true root cause (named the saturated resource, not what saturated it). Reproduce it yourself: python bench/run_bench.py.

Install

pipx install logsleuth       # or: pip install logsleuth   (installs the `logsleuth` command)
ollama pull qwen3:8b          # one-time, ~5GB
logsleuth /var/log/app/incident.log

No other dependencies — pure stdlib.

Usage

logsleuth incident.log                  # analyze a file
kubectl logs deploy/api | logsleuth -   # or pipe anything into it
logsleuth incident.log --json           # machine-readable output
logsleuth incident.log --dry-run        # show the evidence pack, prove nothing else is sent
logsleuth incident.log --model qwen3:14b  # bigger machine, smarter analysis

--dry-run prints exactly what would be passed to the local model — audit it, then grep your favorite secret to confirm it's not there.

Choosing a model

Your machine Model Notes
8GB RAM qwen3:4b fast, decent
16GB RAM qwen3:8b default, benchmark numbers above
32GB+ RAM qwen3:14b / qwen3:32b noticeably deeper analysis
On-prem server anything Ollama serves point LOGSLEUTH_OLLAMA_URL at it

How it works

raw logs ──► deterministic preprocessor ──► evidence pack ──► local LLM ──► report
             (dedup, trends, changes,        (~25KB max)       (Ollama)
              dimensions, context windows)

The preprocessor is the point: local 8B models are good analysts but bad readers of 2GB files. logsleuth does the reading with boring, auditable code and saves the model for the part it's actually good at — causal reasoning over dense evidence.

Roadmap

  • Deeper causal-chain analysis (the 2/10 benchmark misses)
  • logsleuth-8b: a fine-tuned model distilled from thousands of incident analyses
  • Watch mode / webhook: auto-analyze on alert
  • Team features: shared incident history, PagerDuty/Opsgenie integration

License

MIT

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

logsleuth-0.1.0.tar.gz (9.3 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

logsleuth-0.1.0-py3-none-any.whl (9.8 kB view details)

Uploaded Python 3

File details

Details for the file logsleuth-0.1.0.tar.gz.

File metadata

  • Download URL: logsleuth-0.1.0.tar.gz
  • Upload date:
  • Size: 9.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.6

File hashes

Hashes for logsleuth-0.1.0.tar.gz
Algorithm Hash digest
SHA256 5ed333a46e9812f671607cf67177366dc1960a9e397fda34dfe2b815fca1d18b
MD5 5249cd01b8ee5304b843a2acb142ca28
BLAKE2b-256 f6f5815f6b1868f5a62b7eaecd637d848ead7bd0f1f831770f3302f2370301da

See more details on using hashes here.

File details

Details for the file logsleuth-0.1.0-py3-none-any.whl.

File metadata

  • Download URL: logsleuth-0.1.0-py3-none-any.whl
  • Upload date:
  • Size: 9.8 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.6

File hashes

Hashes for logsleuth-0.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 e0a9879305839d2f773701ee25829317d5d9d0f7197c6e6fa966969a92a78918
MD5 467a4b7e8d6080aa49fe6dafd4a65106
BLAKE2b-256 ad110f8637e8f0c8c9adba8ab6ae3990dfc024e3db09a9ae35a65d1700a2c718

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page