Need to have illegal characters in Nagios SERVICEOUTPUT and LONGSERVICEOUTPUT

nagios

I have a Nagios check_log style perl script that is called via check_by_ssh. The log file entries can contain characters like '>' and '$', which are dangerous and not allowed in SERVICEOUTPUT or LONGSERVICEOUTPUT. The output is stripping these characters making the alerts hard to read. Is there a workaround for escaping characters in SERVICEOUTPUT, or an option to tun on this dangerous activity?

Best Answer

Remove the characters from the illegal_macro_output_chars config option.

Related Solutions

Escaping characters in Nagios for NC_Net

You can enable full debugging in the nagios.cfg to see what the command actually expands to, this will show you if the dollar sign is actually the problem. To do this, set the following:

debug_level=-1
debug_verbosity=2
# DEBUG FILE
debug_file=/usr/local/nagios/var/nagios.debug
max_debug_file_size=1000000

If you have a lot of checks, you need to set the max debug file size because at that verbosity and level the log fills up quick.

And them maybe (example):

sudo /etc/init.d/nagios reload

You will then need to run check, while tailing the log. You also might want to pipe the tail to grep with something like 'check_nt' so you can lessen the noise.

Ubuntu – Need help in understanding NAGIOS NRPE commands

Look at the man pages for check_http and check_ssh. Those two checks are usually ran directly from the nagios server and NOT used in conjunction with NRPE (exceptions exist).

The warning and critical thresholds are related to response time. You can also modify what http response codes are acceptable.

http://nagiosplugins.org/man/check_http http://nagiosplugins.org/man/check_ssh

Please rephrase your second question as it does not currently make sense. Hope this helps

Best Answer

Related Solutions

Escaping characters in Nagios for NC_Net

Ubuntu – Need help in understanding NAGIOS NRPE commands

Related Topic