summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2023-05-13 11:50:48 +0300
committerPaul Buetow <paul@buetow.org>2023-05-13 11:50:48 +0300
commit7d8272f3c94bc69ab93e059304d65942e7065055 (patch)
tree1a78e691f9bda36f7fa6f3469e354300611828e5
parent3babd5aaf2f1086d5b9a13a53ba614d49280babb (diff)
remove my job title
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 001def2..dcc2998 100644
--- a/README.md
+++ b/README.md
@@ -175,7 +175,7 @@ To create a high-availability Gogios setup, you can install Gogios on two server
# But why?
-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.
+With experience in monitoring solutions like Nagios, Icinga, Prometheus and OpsGenie, I know that 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.