We are ready to announce that the dates and place for this year’s Zabbix annual conference, Zabbix Conference 2014, are finally set! And, we are happy to invite you all to join Zabbix team, Zabbix community, followers, fans and users and all the rest Zabbix professionals and specialists in Riga, Latvia, on September 12-13!
Yesterday, on January 23rd, Zabbix SIA received a special award from the Latvian Open Technology Association (LATA) in the nomination for “The most remarkable open technology solution for business” in the private sector.
It was interesting. It was fun. But what matters the most, Zabbix community members got back together in one place to share their experiences, ideas and thoughts about their beloved product – Zabbix Monitoring Solution!
Zabbix frontend is translated in many languages. For some, the coverage is great – 2.0.7 has been 100% translated in 9 languages. For some other translations the coverage is not that great… In preparation for Zabbix 2.2, there is a plan to remove translations below some threshold.
Zabbix virtual appliance has been available for quite a long time now. It includes Zabbix server, agent and frontend,…
Creating complex maps is a time-consuming job. Actually, even designing a rather small map of 25 elements can take you an hour. That’s time you rather want to spend on something useful or fun, unless you’ve got a fetish for repetitive work. All we need to automate this task, is a network/graph library like Networkx and the Zabbix API.
Until Zabbix 2.0.7 proxies used a simple algorithm for their configuration synchronization – overwriting the old configuration with a…
The Zabbix 2.0 translation team has done a great job, but there’s something else coming closer… no promises, but Zabbix 2.2 will come out one day 🙂
With lots of new features and improvements, translatable strings have changed significantly, too. Even for languages that are in great shape in 2.0, things don’t look that great in 2.2 – yet.
One of the questions for those of us that use Zabbix on a large scale is “Just how much data can Zabbix ingest before it blows up spectacularly?” Some of the work I’ve been doing lately revolves around that question. I have an extremely large environment (around 32000+ devices) that could potentially be monitored entirely by Zabbix in the future.