From 989bb6a71672576870cbe248e105a2b8ff9342b5 Mon Sep 17 00:00:00 2001 From: zzstoatzz Date: Fri, 28 Aug 2026 22:34:03 -0500 Subject: [PATCH] deploy: document how rules.yml reaches the box prometheus The README said the box read its own copy, but until 2026-08-29 nothing was mounted and prometheus.yml had no rule_files. Record the mount, the rule_files entry, and that restart (not reload) applies changes. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01B927dNwNKNYsbQdUoNJwHS --- deploy/README.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/deploy/README.md b/deploy/README.md index 5401247..1381864 100644 --- a/deploy/README.md +++ b/deploy/README.md @@ -114,9 +114,12 @@ semantic row. ## alert rules `prometheus/rules.yml` is the in-repo source for the Prometheus alert rules; -the box's Prometheus reads its own copy from `/opt/stream-experiment/`, so a -rule change here is not live until that copy is replaced and Prometheus -reloaded. Validate with `promtool check rules deploy/prometheus/rules.yml` +the box's Prometheus reads its own copy at `/opt/stream-experiment/rules.yml` +(mounted to `/etc/prometheus/rules.yml`, listed under `rule_files` in +`prometheus.yml`), so a rule change here is not live until that copy is +replaced and Prometheus restarted (`docker compose up -d prometheus`; the +container has no `--web.enable-lifecycle`, so there is no reload endpoint). +Wired up 2026-08-29; before that the box had no rules loaded at all. Validate with `promtool check rules deploy/prometheus/rules.yml` (e.g. via `docker run --rm -v "$PWD/deploy/prometheus:/rules:ro" --entrypoint promtool prom/prometheus check rules /rules/rules.yml`). The rules have no notification route; they surface only in Prometheus/Grafana alert state. -- 2.51.2