Some might recall that back in 2011 we dug into old logfiles and produced a 5 year graph of Zabbix user count in the #zabbix IRC channel. At the same time, monitoring at a higher rate – hourly – was set up, and data collection started. Now that it’s been 2 years since that graph, let’s take a look at the new graph, how the user count has changed in two years and how Zabbix copes with a 7 year graph.
We have decided on the dates and place for Zabbix Conference 2013 – it will again happen in Latvia, and it’s moved a bit more towards the summer – September 6th and 7th.
While other countries were considered this time, we decided to go for Latvia still, as it is easier to organise an event here. Of course, we also had several community members actively bug us about conference being in Latvia again – apparently, they have grown fond of it 🙂
The exact location for the conference has not been decided on yet, but we were advised to warn the potential host about “hundreds of geeks with a wifi need”, as the Zabbix crowd is able to bring a wireless network to its knees in most venues.
We would also suggest to use the chance and see more of Latvia before and after the conference – but definitely plan to arrive early on the previous day as we will have a welcoming event to meet old friends and find new ones.
Many prominent community members have already confirmed their presence – so start planning for September 5-7 in Latvia 🙂
We’ve recently published the documentation for some of the APIs that have been introduced in 2.0 but had not been covered in the manual at all. If you are a Zabbix expert, you’re probably already aware of their existence, but if you don’t know your way around the source code, you might have missed them. Anyway, you can now familiarize yourself with six useful APIs for maintaining your Zabbix configuration. Continue reading “Newly documented APIs”
When we started following the string freeze principle for Zabbix 2.0.3 release, the goal was to give translators some time period before each release, thus increasing the chances of a translation being completely finished. That did help, and 2.0.3 came out with 6 translations at 100%. Now the translation freeze for Zabbix 2.0.5 starts.
“Why on earth was I not notified?!” — ever heard that question from a fellow worker? Setting up notifications can be a challenge — and not only for beginners. Normally, debugging such cases is cumbersome, complex and requires a good understanding of how Zabbix works. Were you ever asked for a list of people who would be notified on some event? It’s hard to tell, until the event actually happens. Or at least it used to:
The Action Simulator tries to relieve you from these problems and make you and your co-workers happy again.
EPEL finally offers Zabbix 2.0 packages. These packages are for you, if you are running RHEL, CentOS, Scientific Linux or any other Red Hat derivative. EPEL aims to provide best quality packages, that follow the same rules and conventions as Red Hat packages and therefore integrate smoothly.
The 2.0.4 release contains a lot of improvements so one tiny change may have passed unnoticed: the version of the API has been bumped to 2.0.4 as well. Indeed, that’s one small change in the code, but a huge decision for the Zabbix developers team. The API version has remained on 1.4 since the release of 2.0, but finally we’ve developed a versioning that will suite our needs. Continue reading “API versioning”