Observability
by @ops Go + MongoDB + Kafka: Logging/Observability Pipeline
A centralized logging and observability backend: Go ingestion API, MongoDB for flexible, schema-less log storage, and Kafka as the durable ingestion buffer so log volume spikes never take down the pipeline.
Loads this recipe straight into the wizard — every setting stays editable before you generate anything.
The stack
Install
# pulls this exact recipe straight from the Vault $ npx stacktora install go-logging-observability --remote $ stacktora sync # generate the files
What you get
More from the Vault
Centralized Logging & Metrics Pipeline
A self-hosted log/metrics ingestion API on ClickHouse — built for high-volume writes — with Redis for buffering and dedup ahead of it. For teams past the point where grepping log files or a single Postgres table cuts it.
Go + Postgres + Redis: Certificate & Domain Expiry Monitoring
Watches SSL certificate and domain expiration dates, a worker checking on schedule — distinct from Uptime & Status: that checks if an endpoint responds right now, this catches the thing that fails silently weeks in advance until it suddenly doesn't.
Incident Management & On-call Backend
Internal incident tracking, on-call rotation state, and postmortem records — distinct from the Uptime & Status Page recipe, which is the external, customer-facing side. This is what your team sees when something breaks, not what your customers see.
Uptime & Status Page Backend
Monitor a set of URLs, record pass/fail history, and serve a public status page from the same data — the same shape as Stacktora's own dogfooding project for this exact use case. A worker performs the periodic checks; Postgres holds the history.