Let’s talk bugs. The important Zabbix bugs. What are those? The ones that have the most votes in the Zabbix issue tracker.
There are currently 1308 open bugreports. When we looked at this number back in November last year, it was a hundred less. That’s a pretty huge number, is everything bad? Not really, as some might be duplicates and some might be incorrect reports. Not many, though, as there’s constant grooming going on. Most of the remaining are valid bugreports, but not too critical – some are even as minor as an offset of a few pixels in some page. Still a bug, but something we can live with, mostly. We already looked at the top-voted bugreport, now is the time to glance at others same as we did with feature requests.
It could be addictive to look at a graph, showing the number of open bugreports. Unfortunately, Jira still lacks the capability to graph open issues over time. For now, here are the top most annoying bugs that the Zabbix community has voted on:
|1||ZBX-2494||deadlock between server and frontend||Aleksandrs Saveljevs||2010-06-01||28|
|2||ZBX-2815||Missing audit records for different actions in zabbix GUI and API||Alexey Fukalov||2010-08-04||23|
|3||ZBX-3924||frontend and daemons use different regexps||richlv||2011-07-06||19|
|4||ZBX-3878||Slide Shows cause the browser to use more and more RAM over time.||dazman||2011-06-10||17|
|5||ZBX-9879||https monitoring breaks when TLS V1.0 protocol disallowed||K. M. Peterson||2015-09-16||17|
|6||ZBX-2866||nested aggregation function do not escape Macros in a right way||Thomas Spengler||2010-08-12||16|
|7||ZBX-4445||Actions are triggered even if hosts are in maintenance||Pier Carlo Chiodi||2011-12-15||15|
|8||ZBX-6463||Zabbix IT Services shows incorrect SLA||saif||2013-04-04||14|
|9||ZBX-6669||remembered host incorrectly used in trigger config popups||richlv||2013-06-06||13|
|10||ZBX-6118||Very low performance changing template linked with many hosts||Oleksiy Zagorskyi||2013-01-14||12|
|11||ZBX-3356||Graphs display data even when no data has been sent for trapper items||james||2010-12-29||11|
|12||ZBX-9867||PidFile location in .conf file ignored, can't restart zabbix||Gene Liverman||2015-03-02||11|
|13||ZBX-8013||Adding trigger dependency between templates fails when template is directly linked with hosts||Mika Tiainen||2014-04-01||11|
|14||ZBX-4646||Month and minute are shortened with "m""||Volker Fröhlich||2012-02-13||10|
|15||ZBX-4500||"fuzzytime" should compare with the time the item was collected"||Kevin Doren||2012-01-02||9|
|16||ZBX-6345||user's permission not affect API||pengyao||2013-03-05||8|
|17||ZBX-5523||Acknowledgement doesn't stop actions from being processed after maintenance ended||Fabien Grumelard||2012-08-30||8|
|18||ZBX-8385||snmpV3 report (responce) "usmStatsNotInTimeWindows" treated as NETWORK_ERROR, which is bad and may mislead||Oleksiy Zagorskyi||2014-06-23||8|
|19||ZBX-8042||On server startup, the value cache being populated freezes the insert of data into the database||Corey Shaw||2014-04-04||8|
|20||ZBX-10229||Latest data slowness using MySQL (late row lookups)||Kenneth Palmertree||2015-12-31||7|
As we already know about the bug number one, let’s take a quick glance at the second place. Zabbix has a nice and promising feature, logging/auditing of all the changes made to the configuration. Unfortunately, this feature got mostly broken with the release of Zabbix 1.8, many changes are not recorded in the audit log anymore. Bugreport ZBX-2815 tracks the status of this problem, but it’s been a while – Zabbix 1.8 was released on 2009-12-07.
This issue is quite important, as it also has security implications. We’ll talk about it in a bit more detail soon.