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.
Just a couple of pictures of what’s happening at the home of Zabbix. Short version – winter is here.
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.
The opensource conference T-DOSE in Eindhoven, Netherlands took place a bit more than a week ago. It provided good coverage of different subjects, including KVM, Devops, Open GIS, puppet and lots more. And, of course, Zabbix.
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.
For a long time Zabbix has gone largely unnoticed in the world of monitoring systems. Despite being around for almost 10 years and having several unique features for the time (and still today) like Zabbix proxy, it was not something one would expect to see in user surveys. Times, they seem to be a-changin’.
It’s been a while since the first public release of Zabbix – almost 10 years. That’s something worth celebrating, right? There also could be some event where Zabbix users could share their experiences, meet the developers and gain new knowledge about Zabbix. So what’s the plan?
More than a month ago probably the furthest ever training of Zabbix happened. It was also a very exciting environment where Zabbix was being introduced. Meet Montevideo, Uruguay and Plan Ceibal.
Zabbix manual can be both source of joy and frustration. While some areas are easy enough to find and documented in detail, some are a bit lacking. Improvement has to start somewhere, so here’s an attempt at “rebooting” Zabbix manual.
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.