summaryrefslogtreecommitdiff
path: root/gemfeed
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2023-05-21 13:05:57 +0300
committerPaul Buetow <paul@buetow.org>2023-05-21 13:05:57 +0300
commitc573ee021e452bf53e4e6887eea03824f7f5a38c (patch)
tree5ab8f491f80b10a52a279f6f2dacd17c69fd5a95 /gemfeed
parent3a3c25f17303894e4b7ffa7a62d7015ea8d978fc (diff)
Update content for md
Diffstat (limited to 'gemfeed')
-rw-r--r--gemfeed/DRAFT-kiss-server-monitoring-with-gogios.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/gemfeed/DRAFT-kiss-server-monitoring-with-gogios.md b/gemfeed/DRAFT-kiss-server-monitoring-with-gogios.md
index 9772ca10..b3f3537d 100644
--- a/gemfeed/DRAFT-kiss-server-monitoring-with-gogios.md
+++ b/gemfeed/DRAFT-kiss-server-monitoring-with-gogios.md
@@ -33,7 +33,7 @@ https://asciiart.website/index.php?art=objects/computers
## 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 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.
+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, 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.