0040 (ADR-017): Monitoring per machine with Monit, aggregated per site in etcd #45
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/tracker#45
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Decision (maintainer, 2026-09-30). Monit stays per machine and restarts what it can. An agent in the etcd overlay writes a compact Monit summary to the node's registry key; site aggregation is a view over etcd. Prometheus optional (the same agent can expose it). Machine alerting in Monit; mesh alerting via etcd watches. Monit checks are generated from the composition manifest.
Handbook:
docs/decisions/0040-monitoring-with-monit-and-etcd.md(handbook#26)Amends: 0021 ("never restarts a service" becomes "restarts what it can"; peer watching over Monit's HTTP interface becomes etcd watches; checks also come from the manifest).
Review notes (resolved by the maintainer, 2026-09-30: Monit restarts what it can; 0021 superseded on that point)
First tasks