add retry and retry interval check config options

1 files changed, 6 insertions, 2 deletions

diff --git a/README.md b/README.md
index dcc2998..9c5b8d5 100644
--- a/README.md
+++ b/README.md
@@ -105,11 +105,15 @@ To configure Gogios, create a JSON configuration file (e.g., `/etc/gogios.json`)
   "Checks": {
     "Check ICMP4 www.foo.zone": {
       "Plugin": "/usr/local/libexec/nagios/check_ping",
-      "Args": [ "-H", "www.foo.zone", "-4", "-w", "50,10%", "-c", "100,15%" ]
+      "Args": [ "-H", "www.foo.zone", "-4", "-w", "50,10%", "-c", "100,15%" ],
+      "Retries": 3,
+      "RetryInterval": 10
     },
     "Check ICMP6 www.foo.zone": {
       "Plugin": "/usr/local/libexec/nagios/check_ping",
       "Args": [ "-H", "www.foo.zone", "-6", "-w", "50,10%", "-c", "100,15%" ]
+      "Retries": 3,
+      "RetryInterval": 10
     },
     "www.foo.zone HTTP IPv4": {
       "Plugin": "/usr/local/libexec/nagios/check_http",
@@ -175,7 +179,7 @@ To create a high-availability Gogios setup, you can install Gogios on two server
 
 # But why?
 
-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.
+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, 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.