One of the promises of Zabbix is an ability to monitor pretty much anything. That is possible using various extending capabilities on the Zabbix server, binary agent and elsewhere. Maybe we can monitor some aspects of Zabbix community using Zabbix itself?
In the past, quite often Zabbix users have been puzzled regarding some server tuning parameters – for example, how many pollers do they need? It was usually determined based on experience, testing and a bit of guesstimating. No more fuzzy attempts – get hard facts with Zabbix 1.8.5.
UPDATED 2011.11.02: new downloadable template version v2
UPDATED 2012.05.08: new downloadable template version v3 (for Zabbix 2.0.0rc3)
There are many browsers in the world. Some better, some worse, some unusable. But some are just legendary. Probably no other browser version has ever been written and spoken about as much as one some of Zabbix users might have also heard about.
With all the snow outside, Zabbix developers have been busy indoors, working on neat features for Zabbix 2.0. While many of those are low level and don’t result in visually pleasing screenshots, just today a significant change was merged to cutting edge development branch – trunk.
The development of a monitoring solution, now called Zabbix, started way back in 1999. From the functional perspective, Zabbix is much more capable now than it was 11 years ago. However, is it possible that some of this functionality is still backed by code from those ancient times? How did the source code change over the years? In this article, we will take a look at how the software developed over time source code-wise.
Zabbix has built-in web monitoring, which provides scenario support – user workflow emulation on the webpage. There are also some neat predefined graphs on the scenario level. Dedicated Zabbix translator zalex_ua has shared some of these predefined graphs… from scenario with 20 steps.
So in part 1 we found out that Zabbix 1.8.1 provided significant performance improvements over 1.6, mostly because of reduced database access. But those who have been following “What’s new” section in Zabbix manual might be aware that both 1.8.2 and 1.8.3 promised even better performance. After 1.8, that sounds quite optimistic, doesn’t it? Let’s try to get some data on that then. To have comparable data we hunted down Zabbix user verwilst again and coerced him to provide some fresh graphs – thanks again.
Zabbix is being constantly improved – functionality, usability and also performance wise. Let’s look at some practical effects on what all these performance improvements have provided in 1.8 series.
As some might recall, Zabbix 1.8 alone was promising a huge performance improvement. Back in February we actually got a confirmation on that, thanks to Zabbix user verwilst. In the first part, let’s rehash what we found out that time regarding upgrade from 1.6 to 1.8.1.