From 2e864e5b818ae63e99a83bc294050dd516846c82 Mon Sep 17 00:00:00 2001 From: Marcel Date: Sat, 16 May 2026 10:54:04 +0200 Subject: [PATCH] docs(infra): remove stale 'observability not yet deployed' note MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Replace with a cross-reference to DEPLOYMENT.md §4 now that the obs stack shipped as docker-compose.observability.yml. Co-Authored-By: Claude Sonnet 4.6 --- docs/infrastructure/production-compose.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/infrastructure/production-compose.md b/docs/infrastructure/production-compose.md index 75b513c3..cf873bfe 100644 --- a/docs/infrastructure/production-compose.md +++ b/docs/infrastructure/production-compose.md @@ -12,11 +12,11 @@ The original spec in this doc proposed an overlay pattern (`docker compose -f do --- -## Observability stack — not yet deployed +## Observability stack -Prometheus, Loki, Grafana, Alertmanager, Uptime Kuma, GlitchTip and ntfy are **not** part of the production deployment that #497 landed. They are tracked as follow-up issue #498. +The observability stack (Prometheus, Loki, Grafana, Tempo, GlitchTip) ships as a separate `docker-compose.observability.yml` alongside the main stack. Configuration lives under `infra/observability/`. -When that lands the observability containers will join `docker-compose.prod.yml` under a dedicated profile so they can be operated alongside the application stack without affecting the application containers' restart cycle. +→ See [docs/DEPLOYMENT.md §4](../DEPLOYMENT.md#4-logs--observability) for the full setup procedure, service URLs, first-run steps, and env var reference. ---