Zabbix is already translated in quite a lot of languages, but there could always be more, and the available ones could have better coverage. There are several ways how translators’ work can be made easier, and one step is the introduction of string freeze, starting with Zabbix 2.0.3.
Often host level maintenance is too much. Picture a machine running multiple services: While one service has a scheduled downtime, others continue their work and you want to be alarmed about them. Zabbix has no maintenance on trigger level at present, but you can work around it quite easily.
The performance of Zabbix is being constantly improved, and there were significant performance improvements back in 1.8. Then pretty much every Zabbix 1.8 series release added some more benefits, reduced database access and so on. With the 2.0 release there are more performance benefits expected, but there’s so little time to gather some information… luckily, some users do provide us with empirical evidence 🙂
Zabbix agent currently supports only one server in active mode – the first host from the Server configuration parameter is used. While for most users that is enough, some installations require a more advanced approach with the agent being able to report to multiple servers in the active mode.
Well… when we wrote that second day of CeBIT 2012 was very busy, we had not seen the third day yet. In retrospective, second day wasn’t that busy, actually.
The first day of CeBIT2012 was extremely busy and very productive for the Zabbix team.
We were pleasantly surprised to meet lots of old friends – thank you all for visiting us.
We also made new friends from many countries across the world, and we hope for a long lasting cooperation with every one of you.
While it is possible to monitor various aspects of virtual environments with current versions of Zabbix, it does require some time to set it all up and isn’t as integrated as it could be.
A more integrated experience for virtual environment monitoring is currently being considered for development. It might cover VMware, Xen, KVM (and possibly other environments), and include easy-to-set-up monitoring of both hypervisor and guest virtual machine statistics.
Everything happens for the first time. This statement comes true with Zabbix rather often lately. Could be due to a rapid growth.
Normally, Alexei is the one that directs Zabbix development: which bugs are meant to be fixed and which features are meant to be implemented. However, sometimes Alexei is too busy to pay enough attention to what developers are doing, and that is a chance to do some hacking. Here is one of them.
Zabbix is used to monitor many of the world’s biggest environments. But it also monitors its own (albeit small) environment. And this environment recently saw a shark attack.
Zabbix daemons use various approaches to improve performance. One such measure, introduced in Zabbix 1.8, is configuration cache. It resulted in massive performance improvements (up to 10 times), mostly because of a significantly reduced database access (that we looked at in previous blog posts). This cache slightly changes how Zabbix operates, though, and can introduce some delays in configuration information processing. Zabbix 1.8.6 provides a new feature to help with configuration cache management.
…in the configuration files, that is. For a long time, if you made a mistake in a configuration parameter’s name, Zabbix processes would not really tell you about that. This is finally changing with Zabbix 1.8.6.