NSClient++ 0.4.4.15

Prerequisites

• The NSClient++ monitoring agent version 0.4.4.15 installed on the target host
• Permissions to add check commands and services in op5 Monitor

Adding the check command

1. Hover over the "Manage" menu and select "Configure"
2. Click on "Commands" in the "Core Configuration" section

3. Add a new command with the following settings:

   Option	Value
   command_name	check_nrpe_windows_eventlog_id
   command_line	$USER1$/check_nrpe -s -H $HOSTADDRESS$ -c check_eventlog -a file="$ARG1$" "warning=count = $ARG2$" "critical=count = $ARG3$" "filter=source like '$ARG4$' AND id = '$ARG5$'" unique truncate-message=300 'top-syntax=The status is: ${status}: with ${count} entries matching the ID the last 24h Log message:"${list}"'

   
   
   

4. Click the "Submit" button and save the configuration changes.
    

Using the check command in a service

The check command that we created above takes 5 user supplied arguments:

Example use case 1

In the following example we will add a service monitoring an event ID telling us that the Active Directory Web Services doesn't have a valid TLS Certificate.
This event has the ID "1400" and is located in the "Active Directory Web Services" file.

Configuration instructions:

1. Open up your target host in the configuration utility, go to the services section and select "Add new service".

2. Change the following configuration options:

   Option	Value
   service_description	Active Directory Web Services TLS Certificate
   check_command	check_nrpe_windows_eventlog_id
   check_command_args	Active Directory Web Services!1!2!ADWS!1400

     

3. Click on the "Submit" button and save the configuration changes

Additional information

For more advanced information have a look at the NSClient++ 0.4.4 check_eventlog documentation