Windows Secure Web Server (via NRPE)

Description

Monitors an HTTPS server on a Windows server using Nagios Remote Plugin Executor (NRPE). NRPE is used by the Nagios server to communicate with the Windows server. The nrpe.cfg file on the Windows server maps commands issued by the GroundWork server to scripts in the c:\nrpe_nt directory. Commands issued by this profile are installed with this package. If new NRPE commands are added, this file must be modified.

Profile Package

This package includes the following files:

  • Profile definition: service-profile-nrpe-https.xml

  • Plugin script: check_nrpe, check_http

  • NRPE script (installed on the monitored Windows server): nrpe_nt.zip

Installation

GroundWork Monitor includes many monitoring profiles for a variety of devices, systems and applications. Some profiles are pre-imported on a new GroundWork installation and others are distributed with the product. The configuration tool is used to import updated profiles and profiles that require additional setup, services can also be imported, see Importing Profiles.

Services Configuration

For plugin details you can run the service help command from within the nagios container. For example: Get to the nagios container from the gw8 directory: docker-compose exec -u 1000 nagios bash, then to the libexec directory: cd /usr/local/nagios/libexec, and enter a service help command e.g., ./check_snmp --help to receive help content.

Service/Command Line/Plugin CommandCommand Parameters

This column lists the Service Definition name, Service Command name with arguments to be passed to the plugin, and the Plugin Command line which is the plugin script called by Nagios for the service.

Command parameters are in the configuration services section with the following names and default values.

  • tcp_https

  • check_http!3!5

  • $USER1$/check_http -t 60 -H $HOSTADDRESS$ -w "$ARG1$" -c "$ARG2$" -S

Uses check_http plugin to get a web page from $HOSTADDRESS$

  • $ARG1$: Warning seconds, default warning threshold is a 3 second page load time 

  • $ARG2$: Critical seconds, default critical threshold is a 5 second page load time

  • tcp_https_port

  • check_http!3!5!80

  • $USER1$/check_http -H $HOSTADDRESS$ -w "$ARG1$" -c "$ARG2$" -p "$ARG3$"

Uses check_http plugin to get a web page from $HOSTADDRESS$

  • $ARG1$: Warning seconds, default warning threshold is a 3 second page load time 

  • $ARG2$: Critical seconds, default critical threshold is a 5 second page load time

  • $ARG3$: HTTP port, default port is 80

  • nrpe_service_AeLookupSvc

  • check_nrpe_service!AeLookupSvc

  • $USER1$/check_nrpe -H $HOSTADDRESS$ -t 60 -c get_service -a "$HOSTADDRESS$" "$ARG1$"

Uses check_nrpe plugin to connect to NRPE on $HOSTADDRESS$ and execute the get_service command as defined in the nrpe.cfg.

  • $ARG1$: Service Name (not Display Name)

  • OK if service is running

  • CRITICAL is service is stopped

  • UNKNOWN is service is not installed

  • nrpe_service_HTTPFilter

  • check_nrpe_service!HTTPFilter

  • $USER1$/check_nrpe -H $HOSTADDRESS$ -t 60 -c get_service -a "$HOSTADDRESS$" "$ARG1$"

Uses check_nrpe plugin to connect to NRPE on $HOSTADDRESS$ and execute the get_service command as defined in the nrpe.cfg.

  • $ARG1$: Service Name (not Display Name)

  • OK if service is running

  • CRITICAL is service is stopped

  • UNKNOWN is service is not installed

Related Resources