aboutsummaryrefslogtreecommitdiff
path: root/blog/content/notes/tech/a-monitoring-system.gmi
diff options
context:
space:
mode:
authoralex <alex@pdp7.net>2026-09-15 20:47:00 +0200
committeralex <alex@pdp7.net>2026-09-15 20:47:00 +0200
commitc4c2cfff9e4e0e1d2ee1c5d1b0e6e8005662319a (patch)
tree62defdceb7a171b0d114346378d6f3989bc4b1a4 /blog/content/notes/tech/a-monitoring-system.gmi
parentc0d961514cf5d01dcb4599244e81b28486068a77 (diff)
Add note about passive checks/liveness
Diffstat (limited to 'blog/content/notes/tech/a-monitoring-system.gmi')
-rw-r--r--blog/content/notes/tech/a-monitoring-system.gmi4
1 files changed, 4 insertions, 0 deletions
diff --git a/blog/content/notes/tech/a-monitoring-system.gmi b/blog/content/notes/tech/a-monitoring-system.gmi
index 1a4b29b0..a0d1915f 100644
--- a/blog/content/notes/tech/a-monitoring-system.gmi
+++ b/blog/content/notes/tech/a-monitoring-system.gmi
@@ -51,3 +51,7 @@ If the process return code is not 0, then the status is equivalent to:
```
An adapter executable can be provided to adapt Nagios plugins to the new API.
+
+## TODOs
+
+* Are passive checks with liveness useful? Perhaps they overlap a bit with metrics-based alerting, which I would implement as a separate system.