No more flapping. Define triggers the smart way.

May 27, 2013 10Comments 27445Views By

Zabbix trigger expressions provide an incredibly flexible way of defining problem conditions. If you can express your problem using plain English or any other human language, there is a great chance it could be represented using triggers.

I’ve noticed that even experienced Zabbix users are not always aware of the true power of triggers. The article is about defining problems in a smart way so that all alerts generated by Zabbix will be about real issues. No flapping, no false alarms anymore. Interested?

Read more

Zabbix 2.2 features, part 7 – Value extracting from logfiles and more

May 8, 2013 3Comments 53294Views By

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[].

Read more

Zabbix 2.2 features, part 6 – Returning values from webpages

May 7, 2013 3Comments 8468Views By

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.

Read more

Zabbix 2.2 features, part 5 – Better value mapping

February 21, 2013 5Comments 5065Views By

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.

Read more

Monitor the latest Zabbix news and information

Categories

Zabbix resources

Professional services

Privacy Policy

Linkedin Twitter Facebook-f Reddit Youtube

© 2001-2025. All Rights Reserved.