- Crash Detection/Protection
- Debug Symbols
- Configuration Management
- Reload configuration remotely
Here is a collection of guides for using NSClient++ (regardless of monitoring solution).
This is a work in progress so at the moment there is not so much here but hopefully it will expand. This page has a quick overview and is ment to be read first and help you digest the importance of the "sub guides". but for quick reference they are all listed here.
Debugging NSClient++ commands and configurations
First off when you have truble always run NSClient++ in /test mode like so:
nscp service --stop nscp test ... ... exit nscp service --start
Debugging External Scripts
There are several ways you can debug your commands and external scripts with NSClient++:
- From Windows command line:
myscript.bat foo bar echo %errorlevel%
- From NSClient++
nscp service --stop nscp test ... my_command foo bar ... exit nscp service --start
- From NSClient++ command line
nscp client --query my_command -- foo bar
- From NSClient++ via NRPE
nscp nrpe --exec query -H 127.0.0.1 -c my_command -a foo bar
- From "nagios" via command line
check_nrpe ... -c my_command -a foo bar
If for some unknown reason, and thankfully it happens less and less, NSClient++ will crash it can be good to figure out why. And since the primary location of NSClient++ is "production" it is often hard to get access to fully diagnose the error and install tools to help you. Thus nsclient++ has a built-in crash detection and reporting system.