Zabbix 2.2 features, part 5 – Better value mapping

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.

Continue reading “Zabbix 2.2 features, part 5 – Better value mapping”

Newly documented APIs

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. Continue reading “Newly documented APIs”

Zabbix 2.2 features, part 4 – HTTP proxy for web monitoring

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”