The very first alpha versions of long-awaited Zabbix 3.0 were available for testers already some time ago. Now we are getting much closer to the final release of Zabbix 3.0 with the new 3.0 beta available for everyone. Many people would like to give it a try, but sometimes a nice tutorial helps to understand all concepts involved in this process.
Zabbix Conference 2015 was a great event with a very busy agenda, plenty of presentations, discussions and meetings. And hard work should always be rewarded! This year was no exception, so we threw in our Zabbix official party, which all attendees were invited to join.
Just because we’re partying, however, doesn’t mean we can’t do something special.
After having a brimming first day and an even more exciting night, the participants gathered their strength for another round of insightful talks, case studies and intriguing ideas, shared on the Zabbix conference.
This was the 5th time we all gathered together in Riga, and we must say it was the most impressive year by far. The spirit of the Zabbix Conference 2015 still lingers in the air, as we step into a new week at the office.
On the first official day of the conference the participants gathered excited at the registration from 9am sharp, already discussing the experiences and topics revolving around Zabbix.
There have been two types of graphs in Zabbix until now:
Simple ones were available for any numeric item, but could only display that one item. Custom graphs could have multiple items on them, but could only be created by users with administrator privileges.
Zabbix 2.4 adds a capability to graph any items on the same graph, at any time, by any user – essentially, creating ad-hoc graphs.
In the previous two blog articles we looked at really great improvements in Zabbix 2.4 to help with debugging/troubleshooting – ability to change loglevel for a running daemon (any sub-process, even) and various smaller validation and error reporting improvements. There is yet another improvement in this area, though – improved debugging capabilities for the built-in web and VMware monitoring for the cases when you really have to dig deep.
We already looked at one incredibly useful feature, available in 2.4 – ability to change log level while Zabbix daemons are running. Zabbix 2.4 also provides several other improvements that should help a lot with problem troubleshooting.
One day after the Zabbix Conference 2014, on September 13th, Zabbix team and some delegates from the conference participated in the biggest charity sports event in the Baltics – Nike Riga Run, aimed to raise funds for the charity organization Ziedot.lv children’s treatment and rehabilitation project.
Zabbix Team is very proud and honored that the 4th Zabbix annual event, Zabbix Conference 2014, has gathered almost 200 attendees from all over the world, making this year’s event the most large-scale among all the previous Zabbix conferences.
Historically, issues that might arise when using Zabbix have not been easy to troubleshoot. Not everything that would be useful is always logged. Log level can be increased, but those who still remember the first time they saw what DebugLevel=4 can do will understand why that option usually helped more advanced users. Besides, changing the log level required restart of the daemon, which in many cases would obscure the problem or introduce various other problems like delaying data on proxies in larger installations.
In what could be claimed to be one of the greatest improvements in 2.4 and maybe even beyond that, ability to change log level for a running daemon is coming.
Finally the 4th Zabbix Conference is only one week away and soon Zabbix Team will meet all of the registered participants and guests in Riga, Latvia, to spend 2 days at the most exciting, fun and, of course, full of new knowledge and findings IT event, dedicated to the Zabbix Monitoring Solution!
In Zabbix versions before 2.4, notification (action) conditions were limited to three predefined options – “AND”, “OR”, “AND/OR”. Zabbix 2.4 adds a new option – Custom expression. This results in full freedom when deciding how all the different conditions should be handled.
