Zabbix 2.4 features, part 1 – Multiple LLD filters

Zabbix 2.4 is the upcoming major Zabbix version. While initially scheduled to be released in May 2014, it will be slightly delayed – Zabbix team is working hard, but there’s still a lot they would like to include in this release. While the new version is being baked, we can already start looking at the new features that will arrive with it. The first one will be a feature that Zabbix Conference 2013 participants voted on – multiple filters for the low level discovery.

Read more

Translating Zabbix 2.2

The Zabbix 2.0 translation team has done a great job, but there’s something else coming closer… no promises, but Zabbix 2.2 will come out one day 🙂

With lots of new features and improvements, translatable strings have changed significantly, too. Even for languages that are in great shape in 2.0, things don’t look that great in 2.2 – yet.

Read more

Monitoring the community – two years later

Some might recall that back in 2011 we dug into old logfiles and produced a 5 year graph of Zabbix user count in the #zabbix IRC channel. At the same time, monitoring at a higher rate – hourly – was set up, and data collection started. Now that it’s been 2 years since that graph, let’s take a look at the new graph, how the user count has changed in two years and how Zabbix copes with a 7 year graph.

Read more

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

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

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