Hi friends,
we are near to a new year and we want say thanks to everyone that trust in us and Zabbix and a very special thanks to every guys of Zabbix Team.
Merry Christmas and Happy New Year (with a new release of Zabbix 3.0)
Zabbix postcard Christmas 2015
Our brand new OctoZab project to manage multiple Zabbix servers has been recently updated.
In this version you’ll get a high demanded feature: the possibility to control which Zabbix servers are managed by OctoZab, along with custom credentials for each of them, directly from the frontend!
OctoZab servers list: add/modify/remove your servers
Moreover, as you can see from opening screenshot, layout aspect has been improved and revisited in order to give a more pleasant dashboard, and putting bases for features to come.
If you haven’t yet noticed, we’ve added a Docker container too, just to make easier for you to test and use the application.
As usual, you can check the source code at our GitHub repo.
Enjoy the update!
Zabbix Team is pleased to announce the availability of Zabbix 2.5.0, first alpha release of Zabbix 3.0.
This release is absolutely not for production. It is a very early Alpha Release!
It is not yet feature complete and does not fully represent expected 3.0 version.
Upgrade notes
Link: Release Notes
Many of us are using Zabbix Server for a lot of customer and sometimes we need to monitoring what happen on every Zabbix Server but we can’t…. at least until now… Is born OctoZab
This is our first prototype of Dashboard and we need suggestions and feedback from Zabbix Community, so feel free to ask everything.
You Could find source at https://github.com/Quadrata-it/octo-zab
We also create a demo site please check it at http://demo.quadrata.it/octozab/
Zabbix is a powerful monitoring tool, that can easily become hard to control with the expansion of the infrastructure underneath.
One of the many features it offers is proxies, useful to monitor geo-dislocated devices. We happened to check a not-so-small Zabbix installation for a customer of ours, made of 1 server and about 12 proxies. Some of these proxies were very work-loaded, and needed some fine tuning.
But before analyze which kind of items were monitored and how they were organized, we first had to understand if hosts on which proxies were working were healthy. That’s where some useful Zabbix metrics come into play: Internal Checks.
And that’s where we found a configuration error, with very small evidency if not checked in first place. All of the proxies were not monitored by themselves. What does this mean? That all of them shared same Zabbix server graphs, and was impossible to understand real behaviour of their internal, data gathering, value cache processes.
The solution? As showed in opening screenshot it’s enough to let them be monitored by themselves!
From then on, we were able to fastly identify slowness culprits and where to begin the tuning.
I’m proud to announce our new Zabbix Certified Specialists of May 2015, if you want to become the next one please check the official zabbix training schedule.
