[ZBXNEXT-2520] No way to monitor vhosts using web.page.get, web.page.perf, or web.page.regexp Created: 2014 Oct 19 Updated: 2017 Jun 16 Resolved: 2014 Oct 21 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Agent (G) |
| Affects Version/s: | 2.4.0, 2.4.1 |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Major |
| Reporter: | tagwolf | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Zabbix Server and Agent 2.4, Ubuntu Linux 14.04 |
||
| Issue Links: |
|
||||||||
| Description |
|
I cannot monitor vhosts via my internal network or using agents on the hosts. The reason for this is that the "Host:" option used in the check does NOT pass that header to curl correctly. Resulting in a failed check. Example Shell Check to get a webpage vhost equivalent to web.page.get(-H Host:www.example.com web01.example.com,/,80) curl -H 'Host: www.example.com' http://web01.example.com:80/ What is actually happening with web.page.get is: curl http://web01.example.com:80/ Which results in the incorrect content being returned and making checking a pages contents on local machines impossible. Can you guys please fix the web.page.* items so they can perform basic vhost monitoring. Web monitoring is not applicable here as we need to do comparison checks and store the actual CONTENT of several pages. |
| Comments |
| Comment by Marc [ 2014 Oct 19 ] |
|
Do you think of adding an optional Item key parameter for HTTP header or of implicitly adding the 'Host' header field? |
| Comment by Aleksandrs Saveljevs [ 2014 Oct 20 ] |
|
|
| Comment by tagwolf [ 2014 Oct 20 ] |
|
I did not know that web.page.* wasn't using curl. That makes no sense. Why are you using two different libraries for http requests? My suggestion would be to use the fastest and most needed feature set one (curl). Main reason being, it's currently impossible to monitor a vhost in that case without creating a custom user parameter. Can developers give some idea of where this might sit on the roadmap? The other ticket is still open, major, and last comment was ~6 months ago. I think this would be beneficial to a lot of people. I am saying this because I've needed to use it at the past 3 companies I've been at and got all excited when I was the new web.page.* items assuming I could pass basic headers, and check ssl, etc. If there's anything I can do to help development wise, please let me know. I've been looking at zabbix agent, server and web code for about 6 years now. |
| Comment by Aleksandrs Saveljevs [ 2014 Oct 21 ] |
|
Let's close it as a duplicate then. Regarding development, you are always welcome to contribute patches, although this case is a significant development and a proper design and specification has to be created first. |
| Comment by Oleksii Zagorskyi [ 2017 Jun 16 ] |
|
As I see zabbix agent (at least 2.2.9) sets these headers (when trying to test "www.zabbix.com"): GET / HTTP/1.1 Host: www.zabbix.com Connection: close not sure why this issue has been created at all ... |