WEB Templating in 1.8

[untergeek]

I had heard many rumors that WEB scenarios could be templated started in 1.8

1.8 is here and there doesn't seem to be an information supporting this in the documentation.

We have dozens of hosts we want to monitor with the only thing different in the URL being the fully qualified domain name in the URL. If we could template this, or worse but still acceptable would be to have an API plugin to add this information directly to Zabbix.

I also can't find any WEB objects in the Zabbix API.

The way I figure it, I'm just looking in the wrong place or the rumor has proven false. Can someone set me straight?

[mucknet]

I had heard many rumors that WEB scenarios could be templated started in 1.8

1.8 is here and there doesn't seem to be an information supporting this in the documentation.

We have dozens of hosts we want to monitor with the only thing different in the URL being the fully qualified domain name in the URL. If we could template this, or worse but still acceptable would be to have an API plugin to add this information directly to Zabbix.

I also can't find any WEB objects in the Zabbix API.

The way I figure it, I'm just looking in the wrong place or the rumor has proven false. Can someone set me straight?

I'm in search of the same thing, and running into the same problem. Can anyone at least verify that there aren't any methods for bulk addition or templating of web scenarios, so that I can stop looking

[Alexei]

Stop looking. Initially the functionality was planned for inclusion into 1.8, however it is not there yet.

[kdx200rider]

Web monitor templates

I am disappointed to hear that web monitoring templates will not be part of 1.8, this is becoming a sore point with my organization regarding Zabbix. The amount of time we spend updating individual web monitors is daunting. How soon can we expect web templates?

[danrog]

Not that this will cover everything, but you can add graphs and triggers for web scenarios with the current API.

[untergeek]

I reinvented the wheel. I created an entire templatable ecosystem based on external scripts parsing files with URLs, the results of which are sent using zabbix_sender. Since the scripts are run from the same host as the zabbix server, it's pretty much instantaneous. I created items in a template which are based around port numbers. Each template (port 80, 443, etc) has 5 items: URL (updated once daily), download speed, total download time, http response code, and "did we see the content we expected?". With the URL, I am able to have the trigger show which URL failed, so that's rather useful.

We had similar frustrations because we have hundreds of servers using similar URIs, only the host names/FQDNs were different. This helps us solve a problem we thought would be resolved in 1.8.

[untergeek]

Oh, and I also created graphs to track download time and download speed as part of those templates.