NSClient++ Help (#1) - check_nt vs check_nrpe (#599) - Message List
I had configured a couple checks using check_nt (disk size to name one) when someone told me check_nt is obsolete, and check_nrpe is preferred. I went ahead and tried to change my checks, but when I did I noticed the output was pretty much entirely different.
Where it used to show something like this in check_nt: OK: 1784/10240MB free (17% free)
(or something like that...) it now shows: OK: C:: 15.9G
Which is hardly useful information. Is there a way to change this without TOO much effort (I know I know, everything can be changed in an opensource project, but I'm not going to go ahead and start editing the source), and most important of all: is check_nt really obsolete and should I use check_nrpe instead of it?
Thanks in advance
-
Message #1835
Which command is it your using?
NRPE commands have "options" to control output and such so probably you can customize it a bit. But you might not get a 100% match with check_nt at all times.
Michael Medin
mickem06/11/10 06:51:06 (3 years ago)-
Message #1839
Which command is it your using?
NRPE commands have "options" to control output and such so probably you can customize it a bit. But you might not get a 100% match with check_nt at all times.
Michael Medin
I have figured it out by using -a ShowAll=long, which I must have overlooked on the wiki the first couple times I read it.
That being said, I still wonder about the use of check_nrpe over check_nt where both can supply the desired results.
hafos06/11/10 11:25:24 (3 years ago)-
Message #1840
The main difference is that check_nt is limited to 11 command where as check_nrpe will given you access to many many more. You also have "more control" over the NRPE commands (as they allow arguments).
There is also other technical aspects.
Michael Medin
mickem06/11/10 13:25:53 (3 years ago)
-
-
