continuent-monitors-nagios 0.6.1 → 0.7.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: e2302ed384f4741778d499ec80bba5c571a55227
-  data.tar.gz: 82ddf98af190fbda192cf15b63c38d4c92154920
+  metadata.gz: ecc7266eb50a3ef4861019ae0e285796519324cd
+  data.tar.gz: 845aecebb16c08949ca3b8db8f26d9bd744c8b49
 SHA512:
-  metadata.gz: c6cf042cf427da93be17409ed7e8c5cf73d1d4634b1e1db8b132b5d8acd0d25df3e44f8b6693e222532c44e5052218c787a289a156301880215439b5a24b91af
-  data.tar.gz: d60d5d2bc9d37ab076f0568c6975e8cf92252c16d6a1e23bcda552c5f84e2b4d9069a5ffa27bf7f232128d226c57b6338abc6808edc2a690e6ada1b6f8c4fbf5
+  metadata.gz: efd057da7e628fc532129390106973bdb63b039a2009743ee5d307709938a3f4f54052c264e91b9bf8e657ff85e6a16e88ae8999531f254c1cb548cc93e7b44f
+  data.tar.gz: 3d7573fdf3117d3b026512a10b3a1cef3800ba5510b405854fcc0d4bde833cbfba29c1ecbdd67d8ce29c55ea6eccd7c3364b08195e2dbcb920c9301049c3bcbf

data/README.md

@@ -3,19 +3,146 @@ continuent-monitors-nagios
 
 A Ruby Gem containing Nagios checks for Continuent Tungsten and Tungsten Replicator
 
-## Installation 
+# Installation 
 
-```gem install continuent-monitors-nagios```
+* Install the Ruby gem
+ 
+ ```sudo gem install continuent-monitors-nagios```
+* Install the Nagios NRPE service
+* Add the IP of your Nagios server to the ```/etc/nagios/nrpe.cfg``` configuration file. For example:
 
-## Example Nagios Service Check
+ ```allowed_hosts=127.0.0.1,192.168.2.20```
+* Add the Tungsten check commands that you want to execute to the ```/etc/nagios/nrpe.cfg``` configuration file. For example:
 
-```
-check_by_ssh -H $HOSTADDRESS$ -t 30 -o="StrictHostKeyChecking=no" -C "sudo -u tungsten /usr/bin/tungsten_nagios_latency -w 60 -c 120 --directory=/opt/continuent/"
-```
+ ```command[tungsten_nagios_online]=/usr/bin/tungsten_nagios_online```
+
+ If the commands need to be executed with superuser privileges, the ```/etc/sudo``` or ```/etc/sudoers``` file must be updated to enable the commands to be executed as root through sudo as the nagios user. This can be achieved by updating the configuration file, usually performed by using the visudo command:
+ 
+ ```nagios          ALL=(tungsten)  NOPASSWD: /usr/bin/tungsten_nagios_*```
+ 
+ In addition, the sudo command should be added to the Tungsten check commands within the Nagios ```/etc/nagios/nrpe.cfg```, for example:
+ 
+ ```command[tungsten_nagios_online]=/usr/bin/sudo -u tungsten /usr/bin/tungsten_nagios_online```
+* Start the NRPE service:
+
+ ```shell> sudo /etc/init.d/nagios-nrpe-server start```
+*  Add an entry to your Nagois ```services.cfg``` file for each service you want to monitor:
+ 
+ ```define service {
+         host_name database
+         service_description     check_tungsten_online
+         check_command           check_nrpe! -H $HOSTADDRESS$  -t 30 -c check_tungsten_online
+         retry_check_interval    1
+         check_period            24x7
+         max_check_attempts      3
+         flap_detection_enabled  1
+         notifications_enabled   1
+         notification_period     24x7
+         notification_interval   60
+         notification_options    c,f,r,u,w
+         normal_check_interval   5
+ }```
+
+# Global Options
+
+--directory  
+Use this installed Tungsten directory as the base for all operations
+
+--quiet, -q
+
+--info, -i
+
+--notice, -n
+
+--verbose, -v
+
+--help, -h  
+Display this message
+
+--json                      
+Provide return code and logging messages as a JSON object after the script finishes
+
+--net-ssh-option=key=value  
+Set the Net::SSH option for remote system calls. Valid options can be found at http://net-ssh.github.com/ssh/v2/api/classes/Net/SSH.html#M000002
+
+# Global Outputs
+
+Each of these will usually be appended with a text message depending on the individual script being run.
+
+* OK:  
+* WARNING:
+* CRITICAL:   
+* UNKNOWN:
+
+# Available Checks
+
+Use the ```--help``` option for each command to see the full list of available options.
+
+## tungsten_nagios_backups
+Compare the age of the last backup with that given in the option max-backup-age.  
+
+Returns OK with message 'Not running check because this node is not the coordinator' if the host on which this is being run is not the current cluster coordinator.  
+Returns OK if a backup is found to have the same or lesser age and CRITICAL otherwise.
+Returns an error message under the following circumstances:  
+Script is run on a host that does not have a running Manager or a running Replicator.  
+A backup is not found in the configured loacation.  
+
+Available options:
+
+--service String  
+Where String is the replication service or cluster to check
+
+--max-backup-age String  
+Where String is the maximum allowed age in seconds of a backup on any machine. The default value is 86400.
+
+## tungsten_nagios_connector
+
+Check the availability of the Connector.
+
+Returns one of:  
+OK: The connection was successfully created  
+CRITICAL: The server is not a Continuent Tungsten Connector  
+CRITICAL: The Continuent Tungsten Connector is not running  
+CRITICAL: A connection to the Tungsten Connector could not be created  
+
+Available options:  
+--defaults-file String  
+The defaults file to use when connecting to MySQL
+
+--statement String  
+The command to run against the Tungsten Connector. The default command is "tungsten connection status".
+
+## tungsten_nagios_latency
+
+Check that all applied latency values are under a given number of seconds.
+
+## tungsten_nagios_monitor_threads
+
+Check that the number of Java threads for one of the VMware Continuent services is under a given value.
+
+## tungsten_nagios_online
+
+Check that all replication services and datasources are ONLINE.
+
+## tungsten_nagios_policy
+
+Check that the cluster policy is set to AUTOMATIC.
+
+## tungsten_nagios_progress
+
+Check that the VMware Continuent Replicator process is successfully applies a heartbeat event created by the script.
+
+## tungsten_nagios_relative_latency
+
+Check that all relative latency values are under a given number of seconds.
+
+## tungsten_nagios_services
+
+Check that all configured VMware Continuent services are running.
 
 ## Other useful projects
 
 * https://github.com/Ericbla/check_jstat
 
 ## Compatibility
-These checks only work on the continuent-tungsten-2.x series they are not compatible with continuent-tungsten-1.x.
+These checks only work on VMware Continuent 2.0 and later.

data/bin/tungsten_nagios_policy

@@ -39,7 +39,7 @@ class ContinuentNagiosMonitorPolicy
       critical("The Continuent Tungsten Manager is not running")
     end
     
-    status = TI.status()
+    status = TI.status(opt(:service))
     if status.policy() == "AUTOMATIC"
       ok("Cluster is in #{status.policy()} mode")
     else
@@ -51,6 +51,11 @@ class ContinuentNagiosMonitorPolicy
     super()
     
     description("Check that the local cluster is running in the AUTOMATIC policy")
+    
+    add_option(:service, {
+      :on => "--service String",
+      :help => "The replication service or cluster to check"
+    })
   end
   
   def script_name

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: continuent-monitors-nagios
 version: !ruby/object:Gem::Version
-  version: 0.6.1
+  version: 0.7.0
 platform: ruby
 authors:
 - Continuent
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-12-01 00:00:00.000000000 Z
+date: 2015-04-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: continuent-tools-monitoring