summaryrefslogtreecommitdiff
path: root/gemfeed
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2023-04-26 23:07:23 +0300
committerPaul Buetow <paul@buetow.org>2023-04-26 23:07:23 +0300
commit92ed703b764b406ce8942db7d72a24cbe2646e50 (patch)
treefae9ea65c3bdcda868fc8e78124bec03ed54222e /gemfeed
parentbd8c03be5c1399a6e0edb3c9329cae168c52920b (diff)
add personal
Diffstat (limited to 'gemfeed')
-rw-r--r--gemfeed/DRAFT-kiss-server-monitoring-with-gogios.gmi2
1 files changed, 1 insertions, 1 deletions
diff --git a/gemfeed/DRAFT-kiss-server-monitoring-with-gogios.gmi b/gemfeed/DRAFT-kiss-server-monitoring-with-gogios.gmi
index caec6aba..cf2cbed3 100644
--- a/gemfeed/DRAFT-kiss-server-monitoring-with-gogios.gmi
+++ b/gemfeed/DRAFT-kiss-server-monitoring-with-gogios.gmi
@@ -33,7 +33,7 @@ With compatibility with the Nagios Check API, Gogios offers a simple yet effecti
## Motivation
-As a Site Reliability Engineer with experience in monitoring solutions like Nagios, Icinga, Prometheus and OpsGenie, these tools often came with many features that I didn't necessarily need. Contact groups, host groups, re-check intervals, check clustering, and the requirement of operating a DBMS and a WebUI added complexity and bloat to my monitoring setup.
+As a Site Reliability Engineer with experience in monitoring solutions like Nagios, Icinga, Prometheus and OpsGenie, these tools often came with many features that I didn't necessarily need for personal use. Contact groups, host groups, re-check intervals, check clustering, and the requirement of operating a DBMS and a WebUI added complexity and bloat to my monitoring setup.
My primary goal was to have a single email address for notifications and a simple mechanism to periodically execute standard Nagios check scripts and notify me of any state changes. I wanted the most minimalistic monitoring solution possible but wasn't satisfied with the available options.