Web Monitoring and JSON based service

[jlrd]

I've looked at the documentation and the support forms and it would appear that the in-box Web Monitoring functionality supports only application/x-www-form-urlencoded. It does not have the ability to alter the content type sent as part of the web monitor scenario?

Are there any commonly recommended solutions to achieving this kind of a web monitor via and external check or other Zabbix item type?

Thanks,
Joel.

[inetBrad]

Definitely interested in seeing a solution for JSON-based services

Calling an external application to do the service check with JSON encoded data is not ideal and masks the true performance metrics of the target service I want to measure.

[jlrd]

HTTP header choices via Web Monitoring

I agree this would be a big feature win for Zabbix Web Monitoring. I took a look at the Zabbix feature request items. There was one that fits nicely exactly with the need here.

https://support.zabbix.com/browse/ZBXNEXT-282

Its been in "feature request" state for almost 3 years now

I've heard there are some web monitoring changes planned for 2.2 unfortunately that feature item does not appear to be slated for 2.2. So if anyone else is in need of that feature you may want to hit that URL and lend your voice to its importance.

[joseph_ven]

True!
It would be great to have it!

[jan.garaj]

You have it already in Zabbix 2.4 - https://www.zabbix.com/documentation...web_monitoring

[joseph_ven]

Thanks!
I just finished to upgrade my OS (ubuntu 14.04) and then of Zabbix.
I added this info to the "header" field of my scenario:
Content-Type: application/x-www-form-urlencoded
Accept: */*
Accept-Encoding: gzip,deflate
Accept-Language: en-US,en;q=0.8

However, I am still getting this error when I know that the call just works with the Content-type:
Step "A" [1 of 3] failed: response code "403" did not match any of the required status codes "200"
What else can I do?

[jan.garaj]

Use debugging of web monitoring:

http://blog.zabbix.com/zabbix-2-4-features-part-8-debugging-web-and-vmware-monitoring/3675/

403 means "Forbidden", it can be from app level or from web server - you should to know it.