deadman_check 0.1.8 → 0.1.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 4ea1ce99451bd5223168a7755de036f3aca76902
4
- data.tar.gz: 1d2c3fb3aba11a4a263558682de9a2706e9ac701
3
+ metadata.gz: f145354377f3f75eea633dcf696c89919925ed5d
4
+ data.tar.gz: effa93a10f04b9af3d47768f72623318d5f3d519
5
5
  SHA512:
6
- metadata.gz: c22bb434ad1d1b09c61e80634ad512c777f03b2d84fa86c48b1d3f72743dd215d95944a513dfb8a8be6ce3dd143773015704ce475ffd953c1b6140b05872f672
7
- data.tar.gz: 3fba3fd6897ba75bc6a4e48337001d4707ee42d7dfa8f28bd46935e071fe10e7735cb2a2ef2caabd5a2b735cb74f6a2475aa9a412c8adab852638df1f72c0825
6
+ metadata.gz: 27ba3dc497d30fb69d403bae165e74dbbabc75c6be9ecd64b83c859f5298b3762d17080e131a58e033c0b76866ee5a089de4281e4e52bfadd967201db297ef76
7
+ data.tar.gz: d31f59f0c35ba7dfb2aa09426015243cf480852635e4db8a9b38a3f33522d947fda8400026f6537bf96aa2cf5b101ac98dc3785ac607600ce165195dd097741d
data/.travis.yml CHANGED
@@ -9,6 +9,7 @@ script:
9
9
  - bundle exec rake test
10
10
  deploy:
11
11
  provider: rubygems
12
+ gem: deadman_check
12
13
  gemspec: deadman_check.gemspec
13
14
  api_key:
14
15
  secure: rcQ8I4cBn+UpROxhBUsldKbpiiZ9QNUEep8fLGbmcU6QqN5NA2VrdW/DDzXrgXPPLoTDxRF32K2clIjT6WHYopVOvCeAA0+kNjACtGEV8DKL5VlBz0yWvLqM5L7y6ZhmiL/XUibmN7jcvqqI96h2QRr3qeO4a3XUlAIBqotjMopkqqBcHfq9+19p8CS3yS9Y85c1mM5EDcP7E/3Sa3umK7vvoMh+ulz1mic/CNKSnJOdhicqspvpPLUP0vOZ4Jlnn8I41clkBA0FcbOvEmEU2GNtMR8xDS9e0t+aVBAD92AiKYlHNzWp/84r3ZNjMURmltSLRHOQKYQhFdNJUNxZj9f44mPZcMIqD1kkKFkrdzjRzqpGxldrlUwgGkdiFev9d3x8XYMybDI3SmFDPNfa8d7DeW/AYIwkW6j7rdaFQQLzG4AZnoaW6FOmldePk0hPDT47wdpVy5nItH8ZQax8qJmDOX46IRr4fZ6piXiWZlSIfdwUtdBD47fmZS9xxi+mKTggZYiy+th3txqaXORJCCaaJVo5Yg1hbMN73+yKtLtzmsw/nKr1yVVX3KhYQkNix3ZskNhuOJ2aN2stnVsYKbL0Y924sVp7OrSyg5cWqXEXYcWGpXOKlaABa593QFGwQGl6wo7JiFO7giMQw0n6B4xkRv910BBXSVzafHk+jwk=
data/README.md CHANGED
@@ -2,16 +2,24 @@
2
2
 
3
3
  [![Build Status](https://travis-ci.org/sepulworld/deadman-check.svg)](https://travis-ci.org/sepulworld/deadman-check)
4
4
  [![Gem Version](https://badge.fury.io/rb/deadman_check.svg)](http://badge.fury.io/rb/deadman_check)
5
+ [![Docker Image](https://images.microbadger.com/badges/image/sepulworld/deadman-check.svg)](http://microbadger.com/images/sepulworld/deadman-check "Get your own image badge on microbadger.com")
6
+ [![Docker Image Version](https://images.microbadger.com/badges/version/sepulworld/deadman-check.svg)](http://microbadger.com/images/sepulworld/deadman-check "Get your own version badge on microbadger.com")
5
7
 
6
- A monitoring companion for Nomad periodic jobs that alerts if periodic jobs are
7
- not processing as expected. The deadman-check has 2 modes, one to run with the
8
- 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
9
- is intended to run as a separate process that will monitor the Consul key's EPOCH
8
+ A monitoring companion for Nomad periodic [jobs](https://www.nomadproject.io/docs/job-specification/periodic.html) that alerts if periodic isn't
9
+ running at the expected interval.
10
+
11
+ The deadman-check has 2 modes:
12
+
13
+ 1. Run with the 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.
14
+
15
+ 2. Run as a separate process that will monitor the Consul key's EPOCH
10
16
  time value and alert if that value fails to meet a time 'freshness' threshold that
11
17
  is expected for that job.
12
18
 
13
- * Requires a Consul instance
14
- * Alerting requires a SLACK_API_TOKEN environment variable
19
+
20
+ ### Requirements
21
+ * [Consul](https://www.consul.io/) instance
22
+ * Alerting requires a SLACK_API_TOKEN environment variable to be set (use [Slack Bot integration](https://my.slack.com/services/new/bot))
15
23
 
16
24
  ## Example Usage
17
25
 
@@ -19,6 +27,7 @@ Let's say I have a Nomad periodic job that is set to run every 10 minutes. The N
19
27
 
20
28
  ```hcl
21
29
  job "SilverBulletPeriodic" {
30
+ datacenters = ["dc1"]
22
31
  type = "batch"
23
32
 
24
33
  periodic {
@@ -48,6 +57,7 @@ run post updates to a Consul endpoint (10.0.0.1 for this example)
48
57
 
49
58
  ```hcl
50
59
  job "SilverBulletPeriodic" {
60
+ datacenters = ["dc1"]
51
61
  type = "batch"
52
62
 
53
63
  periodic {
@@ -100,6 +110,7 @@ Next we need a job that will run to monitor this key.
100
110
 
101
111
  ```hcl
102
112
  job "DeadmanMonitoring" {
113
+ datacenters = ["dc1"]
103
114
  type = "service"
104
115
 
105
116
  group "monitor" {
@@ -1,3 +1,3 @@
1
1
  module DeadmanCheck
2
- VERSION = "0.1.8"
2
+ VERSION = "0.1.9"
3
3
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: deadman_check
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.8
4
+ version: 0.1.9
5
5
  platform: ruby
6
6
  authors:
7
7
  - zane
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2017-03-26 00:00:00.000000000 Z
11
+ date: 2017-04-06 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: bundler