Problem: Web monitoring configuration out of box it a separate thing, however configuring it for new instances is a bit confusing for new users as it utilizes a zabbix agent to perform the monitoring steps. This is in addition to that there is not built-in web monitoring template.

Proposal Items:

1) Create a Web Monitoring template which covers triggers for all the base level web monitoring items with intelligent discovery of trigger names etc based on scenarios and steps.

2) Most people use the server's agent (127.0.0.1) to perform web monitoring checks. This can be confusing to people as they will setup a host to track the web checks, however need to put 127.0.0.1 as the server's agent. Perhaps it would be good to have a separate "web monitoring service" that only did the web monitoring type checks. In addition when people setup web monitoring hosts, sometimes they only want to do that check type and not monitor agent based checks.

Argument: Consider how this is done for SNMP. It makes sense that web checks would have a similar setup and not require an agent definition at all. Many web sites have multiple servers, etc anyways so it doesn't make a lot of sense to try to get something like disk usage or any other agent type items.