deadman_check 0.1.7 → 0.1.8

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 0a661c7d591f4c003c5e6b043495762145d81de8
-  data.tar.gz: 2d674e9a4c583a73cd4429b26b10c4da63ac371a
+  metadata.gz: 4ea1ce99451bd5223168a7755de036f3aca76902
+  data.tar.gz: 1d2c3fb3aba11a4a263558682de9a2706e9ac701
 SHA512:
-  metadata.gz: 70642a6c928dd6b65fc653062135937ea9850b9742d996a4ef8a713c6ecc86fd63009e563314d88ab226f6f6509748f48a38beedab7adbe80c43d1a3ade26fcc
-  data.tar.gz: 7e571ea87707d4021dfa3a234dea38f307221936d14d8797854dc7c0a42ca7900d0e910e418c747a60806c4a16376ffe80b8053b8cceb4c2af1570f6c459518b
+  metadata.gz: c22bb434ad1d1b09c61e80634ad512c777f03b2d84fa86c48b1d3f72743dd215d95944a513dfb8a8be6ce3dd143773015704ce475ffd953c1b6140b05872f672
+  data.tar.gz: 3fba3fd6897ba75bc6a4e48337001d4707ee42d7dfa8f28bd46935e071fe10e7735cb2a2ef2caabd5a2b735cb74f6a2475aa9a412c8adab852638df1f72c0825

data/README.md

@@ -5,8 +5,8 @@
 
 A monitoring companion for Nomad periodic jobs that alerts if periodic jobs are
 not processing as expected. The deadman-check has 2 modes, one to run with the
-Nomad periodic job as an additional [task](https://www.nomadproject.io/docs/job-specification/task.html) to update a key in Redis with current EPOCH time. The other mode is of deadman-check
-is intended to run as a separate process that will monitor the Redis key's EPOCH
+Nomad periodic job as an additional [task](https://www.nomadproject.io/docs/job-specification/task.html) to update a key in Consul with current EPOCH time. The other mode is of deadman-check
+is intended to run as a separate process that will monitor the Consul key's EPOCH
 time value and alert if that value fails to meet a time 'freshness' threshold that
 is expected for that job.
 
@@ -44,7 +44,7 @@ job "SilverBulletPeriodic" {
 ```
 
 To monitor the SilverBulletPeriodicProcess task let's add a deadmad-check task to
-run post updates to a Redis endpoint (10.0.0.1 for this example)
+run post updates to a Consul endpoint (10.0.0.1 for this example)
 
 ```hcl
 job "SilverBulletPeriodic" {
@@ -90,6 +90,8 @@ job "SilverBulletPeriodic" {
 }
 ```
 
+<img width="1215" alt="screen shot 2017-03-26 at 3 28 50 pm" src="https://cloud.githubusercontent.com/assets/538171/24335809/276147ec-1239-11e7-83d8-0fca95bebdc2.png">
+
 Now the key, deadman/SilverBulletPeriodicProcess, at 10.0.0.1 will be updated with
 the EPOCH time for each SilverBulletPeriodic job run. If the job hangs or fails to run
 we will know via the EPOCH time entry going stale.
@@ -133,8 +135,9 @@ job "DeadmanMonitoring" {
 }
 ```
 
-Monitor a Redis key that contains an EPOCH time entry. Send a Slack message if EPOCH age hits given threshold
+Monitor a Consul key that contains an EPOCH time entry. Send a Slack message if EPOCH age hits given threshold
 
+<img width="752" alt="screen shot 2017-03-26 at 3 29 28 pm" src="https://cloud.githubusercontent.com/assets/538171/24335811/2e57eee8-1239-11e7-9fff-c8a10d956f2e.png">
 
 # Non-Nomad Use:
 
@@ -171,14 +174,14 @@ $ deadman-check -h
 
   DESCRIPTION:
 
-    Monitor a Redis key that contains an EPOCH time entry.
+    Monitor a Consul key that contains an EPOCH time entry.
       Send a Slack message if EPOCH age hits given threshold
 
   COMMANDS:
 
     help           Display global or [command] help documentation
-    key_set        Update a given Redis key with current EPOCH
-    switch_monitor Target a Redis key to monitor
+    key_set        Update a given Consul key with current EPOCH
+    switch_monitor Target a Consul key to monitor
 
   GLOBAL OPTIONS:
 
@@ -211,19 +214,19 @@ $ deadman-check key_set -h
 
   EXAMPLES:
 
-    # Update a Redis key deadman/myservice, with current EPOCH time
+    # Update a Consul key deadman/myservice, with current EPOCH time
     deadman-check key_set --host 127.0.0.1 --port 8500 --key deadman/myservice
 
   OPTIONS:
 
     --host HOST
-        IP address or hostname of Redis system
+        IP address or hostname of Consul system
 
     --port PORT
-        port Redis is listening on
+        port Consul is listening on
 
     --key KEY
-        Redis key to monitor
+        Consul key to monitor
 ```
 
 ### Usage for switch_monitor command
@@ -245,7 +248,7 @@ $ deadman-check switch_monitor -h
 
   EXAMPLES:
 
-    # Target a Redis key deadman/myservice, and this key has an EPOCH
+    # Target a Consul key deadman/myservice, and this key has an EPOCH
      value to check looking to alert on 500 second or greater freshness
     deadman-check switch_monitor \
       --host 127.0.0.1 \
@@ -257,13 +260,13 @@ $ deadman-check switch_monitor -h
   OPTIONS:
 
     --host HOST
-        IP address or hostname of Redis system
+        IP address or hostname of Consul system
 
     --port PORT
-        port Redis is listening on
+        port Consul is listening on
 
     --key KEY
-        Redis key to monitor
+        Consul key to monitor
 
     --freshness SECONDS
         The value in seconds to alert on when the recorded

data/deadman_check.gemspec

@@ -9,11 +9,11 @@ Gem::Specification.new do |spec|
   spec.authors       = ["zane"]
   spec.email         = ["zane.williamson@gmail.com"]
 
-  spec.summary       = %q{Monitor a Redis key that contains an EPOCH time entry.
+  spec.summary       = %q{Monitor a Consul key that contains an EPOCH time entry.
     Send email if EPOCH age hits given threshold}
-  spec.description   = %q{A script to check a given Redis key EPOCH for
+  spec.description   = %q{A script to check a given Consul key EPOCH for
     freshness. Good for monitoring cron jobs or batch jobs. Have the last step
-    of the job post the EPOCH time to target Redis key. This script will monitor
+    of the job post the EPOCH time to target Consul key. This script will monitor
     it for a given freshness value (difference in time now to posted EPOCH)}
   spec.homepage      = "https://github.com/sepulworld/deadman-check"
   spec.license       = "MIT"

data/lib/deadman_check/version.rb

@@ -1,3 +1,3 @@
 module DeadmanCheck
-  VERSION = "0.1.7"
+  VERSION = "0.1.8"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: deadman_check
 version: !ruby/object:Gem::Version
-  version: 0.1.7
+  version: 0.1.8
 platform: ruby
 authors:
 - zane
@@ -127,9 +127,9 @@ dependencies:
       - !ruby/object:Gem::Version
         version: 1.2.4
 description: |-
-  A script to check a given Redis key EPOCH for
+  A script to check a given Consul key EPOCH for
       freshness. Good for monitoring cron jobs or batch jobs. Have the last step
-      of the job post the EPOCH time to target Redis key. This script will monitor
+      of the job post the EPOCH time to target Consul key. This script will monitor
       it for a given freshness value (difference in time now to posted EPOCH)
 email:
 - zane.williamson@gmail.com
@@ -180,6 +180,6 @@ rubyforge_project:
 rubygems_version: 2.6.8
 signing_key: 
 specification_version: 4
-summary: Monitor a Redis key that contains an EPOCH time entry. Send email if EPOCH
+summary: Monitor a Consul key that contains an EPOCH time entry. Send email if EPOCH
   age hits given threshold
 test_files: []