aboutsummaryrefslogtreecommitdiff
path: root/blog/content/notes/tech
diff options
context:
space:
mode:
authoralex <alex@pdp7.net>2026-09-15 20:52:52 +0200
committeralex <alex@pdp7.net>2026-09-15 20:52:52 +0200
commit645732124de4716a338046ae77200e26d0872875 (patch)
tree381461fde15349999c68acd2895e69e07f386898 /blog/content/notes/tech
parentce0726f160e99ba33fafe3f7b1c6880b9a10b43c (diff)
Add idea about alerting being a user interface
Diffstat (limited to 'blog/content/notes/tech')
-rw-r--r--blog/content/notes/tech/a-monitoring-system.gmi1
1 files changed, 1 insertions, 0 deletions
diff --git a/blog/content/notes/tech/a-monitoring-system.gmi b/blog/content/notes/tech/a-monitoring-system.gmi
index a2c0ae62..2c55f3ec 100644
--- a/blog/content/notes/tech/a-monitoring-system.gmi
+++ b/blog/content/notes/tech/a-monitoring-system.gmi
@@ -54,4 +54,5 @@ An adapter executable can be provided to adapt Nagios plugins to the new API.
## TODOs
+* Alerting can possibly be a user interface based on the API (!)
* Are passive checks with liveness useful? Perhaps they overlap a bit with metrics-based alerting, which I would implement as a separate system.