aboutsummaryrefslogtreecommitdiff
path: root/blog/content/notes/tech
diff options
context:
space:
mode:
authoralex <alex@pdp7.net>2026-09-15 20:49:12 +0200
committeralex <alex@pdp7.net>2026-09-15 20:49:12 +0200
commitce0726f160e99ba33fafe3f7b1c6880b9a10b43c (patch)
treedcb8f33cc2017b37e99e3ae6455ea545ff61bd52 /blog/content/notes/tech
parentc4c2cfff9e4e0e1d2ee1c5d1b0e6e8005662319a (diff)
Add note about metrics-based alerting
Diffstat (limited to 'blog/content/notes/tech')
-rw-r--r--blog/content/notes/tech/a-monitoring-system.gmi2
1 files changed, 1 insertions, 1 deletions
diff --git a/blog/content/notes/tech/a-monitoring-system.gmi b/blog/content/notes/tech/a-monitoring-system.gmi
index a0d1915f..a2c0ae62 100644
--- a/blog/content/notes/tech/a-monitoring-system.gmi
+++ b/blog/content/notes/tech/a-monitoring-system.gmi
@@ -17,7 +17,7 @@ However, Nagios has some problems:
I think this can be improved by:
* Instead of providing a user interface, provide an API as a first-class citizen.
-* Do not implement metrics. Metrics collection is better implemented separately.
+* Do not implement metrics. Metrics collection is better implemented separately. Probably you could implement checks that alert over data in the metrics system.
* Make the configuration a JSON-like format that can be generated easily.
* Only implement checks, dependencies and alerting rules.
* Use JSON output as the main API for commands.