jrader wrote:I tested the Powershell to check Automatic Services, but I still need to find a way to exclude certain services. Also need a way to check large disk like we do with the NSClient now (not based on % but on GB free). Anyone done this?
- Code: Select all
./check_ncpa.py -H <yourIPaddress> -t '<your token>' -M 'disk/logical/C:|/used' -w 80 -c 90
Fun fact, you can browse NCPA's API to see exactly what metrics you can grab from NCPA. Go to
https://<yourserverIPaddress>:5693, (and by yourserverIPaddress, I mean the server you are trying to monitor, not your Nagios Core or XI system), and put in the token for the system. You can click on API, browse the API using the end point navigation on the left side of the screen. And if you hit the "Run As A Nagios Check" box, you'll be presented with everything you need to create an active or passive check, hitting whatever API endpoint you're on.
dynamicnagios wrote:Is there any significant reason to migrate over to NCPA? We're in the same boat, and I know the Nagios team officially supports/develops NCPA but I haven't seen a feature that justifies the work required to migrate yet. Aside from the obvious that NSClient 5.x appears to be wonky with the latest versions of Nagios CORE.
Aside from the feature mentioned above, NCPA also helps you set up passive service checks. If you're not using passive service checks, and you can't find any reason to put in the work for the migration to NCPA, then I would recommend just migrating to NCPA as you deploy new systems.