• nagios-plugins
  • Overview
  • Plugins
    • check_epson_wf3520
      • Description
      • Usage
    • check_dyndns
      • Description
      • Usage
    • check_voo
      • Description
      • Usage

This repo contains Nagios plugins that I've either written from scratch or adapted from pre-existing scripts to suit my needs.

This plugin is designed specifically for the Epson WF-3520 multifunction printer. It may or may not work with other Epson printers with adaptations. I'm more than happy to adapt it based on pull requests to cover more devices. It fetches the status of the 4 ink cartridges and the waste container by parsing the contents of the device's web interface.

This plugin requires the urllib2 python module.

Just drop the script on your monitoring server and invoke it with the printer IP address:

Usage: check_epson_wf3520.py [options]

Options:
  -h, --help            show this help message and exit
  -H HOST, --host=HOST  Printer IP address. Default [localhost]
  -p PORT, --port=PORT  Listening port of the printer web server. Default [80]
  -w WARNING, --warning=WARNING
                        Warning threshold. Default [15]
  -c CRITICAL, --critical=CRITICAL
                        Critical threshold. Default [10]

This plugin checks if the provided dynamic DNS hostname matches the current public IPv4 address of the host that runs the plugin. It can optionally attempt to restart ddclient if there is a mismatch.

This last feature requires that nrpe can launch command as sudo. This can have sudoers and SELinux implications, depending on the distribution you're using.

This plugin requires wget and the Nagios check_dns plugin. If you're a CentOS/RHEL user and have SELinux enabled, you may need an additional SELinux policy to allow NRPE to invoke wget and do HTTP requests. The check_dyndns.te file contains a policy that will allow that specific action.

  Use: /usr/lib64/nagios/plugins/check_dyndns -H host [ -s dns server ] [ -r ]

  -H|--host     Hostname to check
  -s|--server   DNS server to use.  Default: 8.8.8.8
  -r|--restart  Attempt a ddclient service restart if there is an IP/name mismatch

This plugin parses the HTML output of the Voo modem web interface and extracts the SNR (Signal to Noise) information for all the downtream channels. It can be useful to track connectivity issues as well as monitor the impact of works on your line.

I can only check it with the Technicolor as it is the one I have but it is my understanding the WebUI is the same on the Netgear modems, so it should work. If that's not the case, I'm happy to assist to make it more universal.

Always check github for the latest release.

This plugin can be fetch the modem credentials from an HashiCorp Vault KV v2 secrets engine instead of having the credentials hardcoded in a YAML file.

If you want to use Vault (These instructions assume you're familiar with how Vault works):

• Enable the KV v2 secrets engine on your server if not done already.
• Store the credentials as login and password metadata in your path of choice inside the KV v2 mount point.
• Create a policy that enables the read operation on the <your KV v2 mount point>/data/<your chosen path inside the mount point> target
• Enable the AppRole auth backend on your server if not already done.
• Add an AppRole associated with the previously mentioned policy.
• Fill in the YAML config file accordingly, following the indications below.

The plugin assumes TLS connection is established with Vault.

usage: check_voo.py [-h] [-H MODEMADDRESS] [-c CONFIGFILE] [--perfdata] [-v]
                    [-V]

Nagios-compliant plugin to check the connectivity status on a VOO Technicolor modem in bridge mode

optional arguments:
  -h, --help            show this help message and exit
  -H MODEMADDRESS, --host MODEMADDRESS
                        IP address of the VOO modem. Default [192.168.100.1]
  -c CONFIGFILE, --config-file CONFIGFILE
                        Configuration file location Default [check_voo.yml]
  --perfdata            Append perfdata to the plugin output.
  -v, --verbose         Produce verbose output.
  -V, --use-vault       Get the modem credentials from HashiCorp Vault.

When not using Vault, the configuration file is expected to present the following contents:

login: <your Voo modem login>
password: <your Voo modem password>

If using Vault:

server: <Vault server URL>
role: <AppRole role-id>
secret: <AppRole secret-id>
mountpoint: <The mount point of the target KV v2 engine>
path: <The path inside the mountpoint that contains the modem credentials>