Back to OP5 Monitor FAQ

OP5 Monitor - How to monitor response-time with NSClient++

To get a more accurate picture of the availability of your IT-services, it’s a good idea to test the IT-services over the network-link that serves your centralized IT-services to other geographic locations.

This how-to paper will describe how to perform the most basic test, a test that checks the average roundtrip-time and measures packet loss using check_ping. The test will be performed by a remote Microsoft Windows server and called via check_nrpe and NSClient++. This test/check/service can then be added to a service group that you can use when generating SLA-reports.

Other, higher level test, can be performed in the same way. For example check_tcp or check_http can be used.

Configuration at your remote windows server Copied

If you want the possibility to supply arguments, like in the above example, you must explicitly allow this using the setting allow_arguments=1 in op5.ini.

In previous versions of check-nt the argument-numbers are numbered with number one starting directly after the plugin-name (in the above example ARG1 is “-H” ARG2 is “mailserver.domain.com”), this is corrected in newer versions of check_nrpe. In newer versions ARG1 is always ARG1. If you’re using old plugins, then this command is the one to put in op5.ini: command[check_ping]=C:\plugins\check_ping.exe -H $ARG6$ -w $ARG7$ -c $ARG8$

Configuration at your op5 Monitor server Copied

["Geneos"] ["FAQ"]

Was this topic helpful?