web site conten monitoring

[cklayus]

I am monitoring websites with specific content expression. the site is in hebrew i have noticed that nagios is unable to handle hebrew expressions. is something that can be resolved?

[mmiltchev]

It will depend on the plugin or wizard are you using to match the content expression. Could you please confirm what plugins/wizards you are having issues with?

[cklayus]

I am using the standard expression check configured using the monitoring wizard

[tmcdonald]

Hebrew might have some problems with UTF-8:

http://wordpress.org/support/topic/hebrew-encoding

Can you run the check form the command line and see if the output is still broken?

Code: Select all

/usr/local/nagios/libexec/check_http -H <host address> -s <string in Hebrew>

Please post the output here.

[cklayus]

[root@monitor nagiosxi]# /usr/local/nagios/libexec/check_http -H www.idi.org.il -s "על המכון"
HTTP OK: HTTP/1.1 200 OK - 94168 bytes in 4.499 second response time |time=4.498622s;;;0.000000 size=94168B;;;0

the check is ok. but on the nagios web interface the result is different

HTTP CRITICAL: HTTP/1.1 200 OK - string '?? ?????' not found on 'http://www.idi.org.il:80/' - 94168 bytes in 4.262 second response time

it looks like nagios is seeing the hebrew string as a bunch of question marks

[tmcdonald]

So it's not a problem in Core. In your XI web interface, please go to Configure -> Core Configuration Manager, and find the service under Services. Click the name and post a screenshot of the page. It should look similar to this:

2014-06-19 08_59_14-Nagios XI - Configuration.png

The check seems to be working for me - I removed a letter and it came back as this:

2014-06-19 09_01_02-Nagios XI.png

Also what version of Nagios XI is this?

[cklayus]

its the latest


as you can see I have question marks instead of the hebrew string. I tried to manually change it to hebrew, no good.

[tmcdonald]

I just tested this on a fresh 2014R1.1 system and I am seeing the same issues you are, so it must have been fixed in a later version. I will update this post when I know more.

UPDATE: 2014R1.2 fixes this issue and will be released some time tomorrow.

[cklayus]

YES the update did the job.

thnx