To Use Nagios Plugins In Verax NMS

This lesson shows how to use Nagios plugins to monitor devices in Verax NMS Express. Verax NMS is a cross-platform network and application monitoring software.

Tools used

Nagios plugin for CPU check in a Shell Script format (.sh file)

Verax NMS Express ver. 1.9.5:

Adding Nagios Plugin To The Device

download a plugin use plugin for checking CPU usage over the SNMP. Insert  plugin in a folder on the same server where Verax NMS Express is installed.


let’s add shell script sensor to the device

  1. Log into the Verax NMS, select Home from the main menu and select the right device from the aspects tree.
  2. In Monitors tab select Add option and click Go. The system will display a pop-up dialog with sensors available for your device.
  3. Select Shell Script Sensor from the sensors tree and click Next.
  4. Now you have to specify your sensor parameter

System will ask you to enter the following sensor-specific parameters

  • Host – in most cases, the host address is an IP address of the device.
  • Path to script – path to the script file located on the server where Verax NMS Express is installed./root/nagios/

    For me it’s:

  • Output data format – an output data format which is expected to be returned by the script.
    • Ignore – only the return code/time of response is taken into account.
    • Nagios format – format of the script output is compatible with Nagios.In this case set out format to “Nagios” which is by default: ‘label’=value[UOM];[warn];[crit];[min];[max]
  • Script arguments (not mandatory) – arguments are passed due to the uploaded script. You can use the following placeholders in the arguments:
    • %DEVICE_IP% – IP address of the device.
    • %SNMP_COMMUNITY% – SNMP community string for the device.
    • %TIMEOUT% – Timeout value for the sensor.
    • %WARNING_THRESHOLD% – Value for the warning threshold for the sensor.
    • %CRITICAL_THRESHOLD% – Value for the critical threshold for the sensor.
  • Environment variables (not mandatory) – provide a simple way to share configuration settings between multiple applications and processes in Linux. Each of the variables should be definied as “key=value” and they should be separated by “;”.
  • Exit codes greater than this value [warning (exit code 1), error (exit code 2), unknown value (exit code 3)] – it means that if the script’s exit code will be greater than or equal to chosen return code, sensor’s execution will result with error.


Leave a comment