Nagios Support Forum

Not sure about 0.4.1 but you can set encoding in modern NSClient++: https://docs.nsclient.org/reference/cli ... r.encoding

This is a bug and will be fixed in the next build of 0.4.3 (out in the next 24 hours).
And back ported to 0.4.2 in the next few days.

// Michael Medin

Just for completion NSClient++ can do this very easily but requires an agent to be installed as well (which was not possible in your case).
// Michael Medin

Now I am just guessing here but... Could it be that the counter in question is affected by cores? In which case the caps is not 100%? For such counters you need to switch to check_nrpe and use the nocap100 flag to get values above 100%. This is a "feature" of the performance data counterd ...

Given that I actually take the documentation thing seriously (for a change) could someone please help me by telling me whats bad with the new documentation site: http://docs.nsclient.org/

// Michael Medin

./check_nrpe -H IP_Address -p 5666 -c CheckEventLog -a filter=new file=all MaxWarn=1 MaxCrit=2 filter-generated=\<30 filter+eventID=="4111" filter+eventType==all filter=all With 0.4.1. would be: ./check_nrpe -H IP_Address -p 5666 -c CheckEventLog -a file=all MaxWarn=1 MaxCrit=2 "filt...

A tutorial for NSClient++ can be found here: http://docs.nsclient.org/tutorial/nagios/nsca.html

This is for the 0.4.2 version but in this context it is the same as 0.4.1

// Michael Medin

The syntax used in this thread is horribly old and does simply not work.

please upgrade to newer version and use the filter syntax present in 0.4.1 it will work much more easily and much more consistently.


// Michael Medin

NSClient++ supports stateful scripts so it could be done there Using lua or python).
But other options would be to manage state manually outside Nagios.

// Michael Medin

Not sure about the official version but from what I heard Op5 has a version of livestatus which works with Nagios 4: https://github.com/op5/livestatus

// Michael Medin