Skip to content

docs(lab): the stack has been deployed, and it has seven rules (#101) #398

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Gerrrt merged 1 commit into from
Sep 8, 2026
Merged

docs(lab): the stack has been deployed, and it has seven rules (#101) #398

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions stacks/lab/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,8 +44,9 @@ compose.yaml four services, one network, health-gated ordering
.env.example non-sensitive tunables — edit this, not .env
prometheus/
prometheus.yaml four scrape jobs; no alerting block, no file_sd
rules/lab.rules.yaml 4 rules — this stack watching itself, nothing else
tests/lab.test.yaml promtool unit tests; all four rules, firing + quiet
rules/lab.rules.yaml 7 rules — four for this stack watching itself,
three for the domain ADR-0029 sized
tests/lab.test.yaml promtool unit tests; all seven rules, firing + quiet
loki/loki-config.yaml single-binary, filesystem, 15-day retention, no ruler
grafana/
provisioning/ two datasources + dashboard provider
Expand Down Expand Up @@ -117,10 +118,13 @@ and their unit tests.
What `make validate` still does **not** prove about this stack, in the order it
matters:

- **That it runs.** Nothing here has ever been deployed — the guest is [#262].
Every check is static: configs parse, images resolve, healthcheck binaries
exist inside their pinned images. None of it says the four services come up
and talk to each other.
- **That it runs.** It has — `alexander` was built and this stack brought up
on 2026-09-05 ([#262]) — but nothing in `make validate` knows that. Every
check is static: configs parse, images resolve, healthcheck binaries exist
inside their pinned images. None of it says the four services come up and
talk to each other; that is
[`build-the-lab-guest.md`](../../docs/runbooks/build-the-lab-guest.md) §7,
by hand.
- **That its Grafana serves.** `check_dashboard_roundtrip.sh` boots the pinned
Grafana against the estate's dashboards; this stack has none to round-trip,
so that check has nothing to say here.
Expand Down