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.
“Why on earth was I not notified?!” — ever heard that question from a fellow worker? Setting up notifications can be a challenge — and not only for beginners. Normally, debugging such cases is cumbersome, complex and requires a good understanding of how Zabbix works. Were you ever asked for a list of people who would be notified on some event? It’s hard to tell, until the event actually happens. Or at least it used to:
The Action Simulator tries to relieve you from these problems and make you and your co-workers happy again.
Update: Presenting the Action simulator at the Zabbix Conference 2013
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.
Zabbix currently is at version 2.0, and this version took quite a long time to get out – almost 2 and a half years. Of course, all that wait was not in vain – Zabbix 2.0 provided a huge amount of new features. It did mean that you and me had to wait for quite some time before benefiting from those features, though, so there will be an effort to make Zabbix 2.2 happen sooner. Let’s start to look at the improvements Zabbix 2.2 will provide – and let’s start with the one that everybody upgrading will notice – automated database schema upgrades.
Introduction
When monitoring Windows servers and services it would be really handy to have a check to see if all the services that are registered with the system to automatically start up during boot, are also started.
EPEL finally offers Zabbix 2.0 packages. These packages are for you, if you are running RHEL, CentOS, Scientific Linux or any other Red Hat derivative. EPEL aims to provide best quality packages, that follow the same rules and conventions as Red Hat packages and therefore integrate smoothly.
To be known, accepted and demanded in the different corners of the world is of course a big honor and the pride of every developing and dynamic company. However, to become recognized by the company’s home country and to be named “the best”, that’s what makes you really proud of who you are and what you are doing, as we all know – the most honest critique and valuation of the things you do comes from the closest people. 🙂
On October 31st we introduced to our truly beloved Facebook followers an autumn contest, called “Zabbix Explorer”. During one month, until November 28th, the most enthusiastic, nimble, persistent and passionate Zabbix fans were competing with each other in order to win the title of ”Zabbix Explorer 2012”! 🙂
The 2.0.4 release contains a lot of improvements so one tiny change may have passed unnoticed: the version of the API has been bumped to 2.0.4 as well. Indeed, that’s one small change in the code, but a huge decision for the Zabbix developers team. The API version has remained on 1.4 since the release of 2.0, but finally we’ve developed a versioning that will suite our needs.
As announced two months ago, translation/string freeze is obeyed now. Zabbix 2.0 branch enters freeze now in preparation for 2.0.4 release.
For 2.0.3 our awesome translators managed to get 6 translations to 100%. How will it go for 2.0.4?