N8n-trace – Grafana-like observability for n8n workflows
Grafana for n8n workflows, but adoption depends on n8n's self-hosted user base.
Observability engine for AI coding agents. Custom columnar log store, MCP-native, self-hosted on a $4/mo VM. No dashboards — your AI assistant sees production.
MCP-native observability with Postgres introspection and error grouping, not just an API wrapper.
DevOps engineers and backend teams using AI assistants for production debugging
Datadog MCP integrations · Sentry for error grouping · Grafana Loki for log search
What it covers:
- Log ingestion with full-text search (SQLite FTS5), filters by service, level, trace ID, exception class, metadata - Read-only Postgres introspection — query stats from pg_stat_statements, index analysis, lock chains, bloat estimates, replication lag. All queries validated SELECT-only via SQL AST parsing (pg_query) - Sentry-style error grouping by fingerprint with user impact analysis - User analytics — session journeys, conversion funnels, path analysis, top endpoints - VM monitoring — CPU, memory, disk, network via gopsutil - Rule-based threshold watches with auto-resolve
The AI assistant can also take actions: resolve errors, create watches, set up health checks, kill slow queries, and save persistent notes across sessions.
Tools return suggested_tools with pre-filled arguments, so the assistant chains through investigations without prompt engineering.
Stack: Go, SQLite (WAL + FTS5), Chi, HTMX. Single binary, no external dependencies. Runs on a $4 VPS.
Client libraries: Ruby gem for Rails (auto-captures SQL, N+1s, view renders, ActiveJob, PII redaction) and a 3.1KB browser JS client for frontend error tracking.
Grafana for n8n workflows, but adoption depends on n8n's self-hosted user base.
Single Docker container with SQLite beats LangSmith's heavy Postgres dependency.
Yet another observability stack when Grafana and Honeycomb already dominate the market.
LLM logging dashboard, but Langsmith and Llamaindex already do this.
Control plane with token budgets and MCP rules goes beyond passive observability.
Finally, an MCP server that uses your actual cookies instead of spawning headless browsers.