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
Few months ago, our Zabbix friends have inaugurated a very cool and useful portal share.zabbix.com to share and rate template, scripts, tools and much more for Zabbix. I think it’s a great news do spread and use Zabbix much easy for everyone.
Anche quest’anno e’ ora di pensare alla Zabbix Conference, noi saremo presenti da giovedi’ 10 a Domenica 13 Settembre 2015.
Il tema della conferenza e’ molto interessante ed e’ “Share your Passion“, sara’ focalizzato sull’esperienza degli utenti Zabbix provienti da tutto il mondo, in oltre sara’ il luogo adatto per discutere di tutti i temi legati a Zabbix con i migliori professionisti giunti dalle piu’ importanti aziende Enterprise del mondo.
Se qualcuno volesse avere infomazioni sull’evento, non esitate nel contattarmi.
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.
I’m proud to announce our new Zabbix Certified Specialists of February 2015, if you want to become the next one please check the official zabbix training schedule.
Today i want show a problem discovered on one of our Zabbix Server and the Housekeeper process.
Housekeeper (Zabbix documentation)
The Housekeeper is a periodical process, executed by Zabbix server. The process removes outdated information and information deleted by user.
Most of us know the two parameters inside zabbix_server.conf to limit the process behavior:
HousekeepingFrequency
The Housekeeper is a periodical process, executed by Zabbix server. The process removes outdated information and information deleted by user.
MaxHousekeeperDelete
No more than ‘MaxHousekeeperDelete‘ rows will be deleted per one task in one housekeeping cycle.
Actually for most of the times no one care so much about that but today we fall on a big Zabbix Server slow down and this problemi s coming from Housekeeper.
Today we understood much better the logic behind the Housekeeper process, i will try to explain below.
Few days ago we have removed 3 items prototypes from a template that it was linked to 60 hosts and for every hosts that prototype items is near to 300 real items.
So how many orphaned items we have? 3 (proto items) *60 (hosts)*100(expanded proto items)=18000 !
But the huge strange behaviour is here, MaxHousekeeperDelete. If we set to MaxHousekeeperDelete=500 zabbix will try to remove 500 history value per orphaned items.
So what happend?
In the beginning the Housekeeper process it will try to remove 18000×500=9.000.000 of history value!!!!
For example if we look on Zabbix server Log:
————–
housekeeper [deleted 68 hist/trends, 4522000 items, 0 events, 0 sessions, 0 alarms, 0 audit items in 2649.273207 sec, idle 1 hour(s)]
————–
The “4522000 items” is the deleted orphaned items value for a single Housekeeper process.
To discuss about this strange logic we have opened an official trouble ticket in Zabbix
Never see a so great tool to debug our Linux server, please check this post How to monitor and troubleshoot a Linux server using sysdig
Anche quest’anno il LinuxDay di Torino e’ stato un successo!
Tanti curiosi e tanti ottimi talk su Software Libero e sulle nuove tecnologie nate negli ultimi anni.
Chiaramente non potevamo mancare col nostro software di monitoring preferito: Zabbix.
Di seguito qualche immagine della manifestazione.
