Dopo tanto studio e lavoro svolto con Zabbix, il nostro collega Pietro Antonacci e’ riuscito a certificarsi come Zabbix Trainer 🙂
A breve potrete saggiare la sua esperienza di Web Developer e Specialista Zabbix al corso di Certificazione Zabbix che si terra’ il 9 Novembre 2015.
In bocca al lupo Pietro!
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!
I ragazzi del di Zabbix sono orgogliosi si presentare il primo passo verso la nuova e ricca release 3.0.
Attenzione questa release NON E’ DA USARE IN PRODUZIONE ma solo per poter testare in anteprima le nuove funzionalita e per testare il loro corretto funzionamento.
Link a tutte le nuove caratteristiche : Zabbix 2.5.0 release
La nuova interfaccia Web di Zabbix
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.
