Show HN: FaultWall – Which tenant is killing your Postgres? Now you can find out

Slow database pages kept waking me up. Every time, same story: dig through pg_stat_activity, find a runaway query, trace it back to one tenant doing something dumb, kill the connection, go back to sleep. Next week, different tenant, same thing.

Datadog never told me the tenant. So I built FaultWall.

Single Go binary, polls pg_stat_statements every 10s, maps queries to tenants via schema detection. Gives you per-tenant QPS, P50/P95/P99 latencies, cost attribution ("acme_corp is 94% of your DB bill"), and an auto-throttler that pg_terminate_backend() before things get bad.

Anomaly detection with self-tuning thresholds (genetic algorithm). MCP server for LLM agent control. I'm building eBPF kernel-level per-query tracing, for better and accurate detection.

  DATABASE_URL=postgres://... ./faultwall

If you run multi-tenant Postgres, try it and tell me what's missing.

MIT, ~2500 lines Go. https://github.com/shreyasXV/faultwall