In the previous two blog articles we looked at really great improvements in Zabbix 2.4 to help with debugging/troubleshooting – ability to change loglevel for a running daemon (any sub-process, even) and various smaller validation and error reporting improvements. There is yet another improvement in this area, though – improved debugging capabilities for the built-in web and VMware monitoring for the cases when you really have to dig deep.
Also known as that minor improvement some people just love. We already discussed most web monitoring related improvements for Zabbix 2.4, but there’s this one tiny thing left… an increase for the maximum URL length.
In these Zabbix 2.4 feature series we have already seen some improvements for the built-in web monitoring – the ability to specify custom headers and control redirects. Web monitoring got improved further – let’s explore the new options regarding SSL authentication. There are two of them:
- Verifying SSL certificates
- Supplying client certificate
Continuing with the improvements for the upcoming Zabbix 2.4, there are several improvements for the web monitoring. In previous versions Zabbix always followed redirects and retrieved the full page – now both of these things can be controlled.
In several previous articles in the Zabbix 2.2 series we already discussed several improvements for web monitoring – the ability to template it, customise the amount of retries and the ability to specify an HTTP proxy on the scenario level. There’s more – in 2.2 it will also be possible to parse content from a page and reuse it in further scenario steps.
Zabbix has allowed to check whether a webpage contains a specific string for a long time – using the web.page.regexp agent item one could verify whether page contents match a regular expression or not, and return the matched string. But what if multiple matches were possible, but we were interested in a specific one? There was no built-in way to do that, but it is coming for Zabbix 2.2.
Having explored two other improvements to the built-in web monitoring – ability to template it and change retry count – let’s take a look at another one. Until Zabbix 2.2, it was not possible to set HTTP proxy for web monitoring… well, that’s not entirely true – with a hack one could set HTTP proxy for the whole Zabbix server (or, since Zabbix 2.0, Zabbix proxy), but there was no way to set it per web scenario. Zabbix 2.2 will provide such a feature.
Continue reading “Zabbix 2.2 features, part 4 – HTTP proxy for web monitoring”
Let’s continue our series about the improvements that are coming in Zabbix 2.2. We already examined one web monitoring improvement – ability to template it. But there’s more – in 2.2 you will be able to specify how many times a web scenario should be retried.
Continuing with the series on upcoming Zabbix 2.2, the second feature we will look at will be related to the built-in web monitoring that has been available in Zabbix for quite some time already. One problem some users faced – there was no way to use the extensive Zabbix templating system for web monitoring. This was not an issue if all we wanted to monitor were standard websites, but as soon as there would be a large amount of identical webservers, one would have to either do a lot of manual configuration or some scripting via the Zabbix API. Zabbix 2.2 will greatly simplify this by providing templatable web monitoring. Continue reading “Zabbix 2.2 features, part 2 – Templated web monitoring”