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.
In the previous article in 2.2 series we explored a new ability to extract values from a webpage. This was not the only feature that was extended this way – several other items gained similar functionality – notably, file content parsing and logfile parsing. The latter has been a popular feature request and should be good news for many users.
And now for some more detail on changes for item keys vfs.file.regexp[], vfs.file.regmatch[], log[] and logrt[].
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.
So who cares about monitoring the environment?
Exciting news! After a lot of hard work and hundreds of cups of coffee we’re proud to announce that the new documentation of the Zabbix API is complete. The improved API documentation provides both a high level overview of the available methods and in-depth descriptions of each method separately.
Zabbix Conference 2013 is coming. And for the third time it will happen at the hometown of Zabbix – Riga, Latvia.
Zabbix Conference 2013 location has been decided upon, and we are pleased to let you know that it’s Riga,…
We’ve had two awesome events already – Zabbix Conference 2011 and Zabbix Conference 2012. They both were held in…
Value mapping is a neat, little feature in Zabbix that allows to see what a numeric code actually means. Well, what did that mean? For example, a UPS device might return “2”, which means “all is OK”, and “3”, which means “battery low”. There will be many different devices with different numeric codes, so remembering what they all mean is nearly impossible. Value mapping will show a human readable description, but the raw value will still follow in the parentheses – for example, Normal (2).
Until Zabbix 2.2, this was only supported for integers. Zabbix 2.2 will allow to configure value mapping also for decimal and string values.
We’ve recently published the documentation for some of the APIs that have been introduced in 2.0 but had not been covered in the manual at all. If you are a Zabbix expert, you’re probably already aware of their existence, but if you don’t know your way around the source code, you might have missed them. Anyway, you can now familiarize yourself with six useful APIs for maintaining your Zabbix configuration.
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.
When we started following the string freeze principle for Zabbix 2.0.3 release, the goal was to give translators some time period before each release, thus increasing the chances of a translation being completely finished. That did help, and 2.0.3 came out with 6 translations at 100%. Now the translation freeze for Zabbix 2.0.5 starts.
