ring-sqa 0.1.8 → 0.1.9

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 0c87d85ec1ff9b1daf33b01f7ebe576bb5ad11a2
-  data.tar.gz: e082af98b466f6ceaf40738791152b9e2dc3e3dc
+  metadata.gz: b1dc8b248c33b0beea3dd899e6c852c5d1f5eebd
+  data.tar.gz: a7a77dc93f54498d02b26c3a88a5c6e8fc89bd6b
 SHA512:
-  metadata.gz: 5543b7a43d7669a37ab72886f01525e0a31d42497e5af6b2f145451f4ff7b38e0d2089ce31cfd51314420fd26dcaddf6ccd22c4dca8b6cef51a8982beade2cbd
-  data.tar.gz: 74a9ab99f4a392da8c2d5ca617f6a50aaabc2e5ba378c92b868347aeb972f2f4f9fdbde31a7c29b983f0c07c30e7ec70ef5d899ea39ba0566ed8e1013fbdd9e7
+  metadata.gz: 594658283174f39fd12fc2fe468a9b0205b9a12409ea0f70f08084f2a11be3a688096d3b7a37d91aa6dda81c69a023f5093f4863f0ba14e2d167736053ae72c8
+  data.tar.gz: 60406109b165082403d9d031a1aff416ca6c5473c4d075cad4735ed98ee8313590337a6a4e789b1ebce9e9a501a4ca7dcba857408cec1852e4e9649892c44261

data/lib/ring/sqa/alarm/message.rb

@@ -9,9 +9,10 @@ This is an automated alert from the distributed partial outage
 monitoring system 'RING SQA'.
 
 At #{Time.now.utc} the following measurements were analysed
-as indicating that there is a high probability your NLNOG RING node
-cannot reach the entire internet. Possible causes could be an outage
-in your upstream's or peer's network.
+as indicating that there is a high probability your NLNOG RING node cannot
+reach the entire internet. This could be down to your RING node, its local
+network, or disruption of peering and/or upstream networks (for example
+instability at an IXP or one of your transit providers).
 
 The following #{amount} nodes previously were reachable, but became unreachable
 over the course of the last 3 minutes:

data/lib/ring/sqa/alarm.rb

@@ -47,7 +47,7 @@ class SQA
       if exceeding_nodes.size > 0
           msg = {short: "#{@hostname}: raising #{@afi} alarm - #{exceeding_nodes.size} new nodes down"}
       else
-          msg = {short: "#{@hostname}: raising #{@afi} alarm - many nodes were unreachable in the last monitoring period, there is likely network instability. This could be down to your ring node, its local network, or disruption of peering and/or upstream networks (for example instability at an IXP)."}
+          msg = {short: "#{@hostname}: raising #{@afi} alarm - many nodes were unreachable, general instabiliy"}
       end
       exceeding_nodes = exceeding_nodes.map { |node| @nodes.get node }
 

data/ring-sqa.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |s|
   s.name              = 'ring-sqa'
-  s.version           = '0.1.8'
+  s.version           = '0.1.9'
   s.licenses          = %w( Apache-2.0 )
   s.platform          = Gem::Platform::RUBY
   s.authors           = [ 'Saku Ytti', 'Job Snijders' ]

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: ring-sqa
 version: !ruby/object:Gem::Version
-  version: 0.1.8
+  version: 0.1.9
 platform: ruby
 authors:
 - Saku Ytti
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-02-02 00:00:00.000000000 Z
+date: 2015-02-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: slop