Zabbix is already translated in quite a lot of languages, but there could always be more, and the available ones could have better coverage. There are several ways how translators’ work can be made easier, and one step is the introduction of string freeze, starting with Zabbix 2.0.3.
Often host level maintenance is too much. Picture a machine running multiple services: While one service has a scheduled downtime, others continue their work and you want to be alarmed about them. Zabbix has no maintenance on trigger level at present, but you can work around it quite easily.
While there are people who have been very active in the Zabbix community, it might not be so easy to start participating, especially if you are not frequenting IRC, which is the main Zabbix community hub. Hopefully the Zabbix community platform – Zabbix.org – can help here.
Zabbix API starts to play significant role especially when it comes to integration of Zabbix with third-party software like configuration and incident management systems as well as for automation of routine tasks. It is incredibly difficult to manage monitoring of thousands of hosts without some automation in place.
The performance of Zabbix is being constantly improved, and there were significant performance improvements back in 1.8. Then pretty much every Zabbix 1.8 series release added some more benefits, reduced database access and so on. With the 2.0 release there are more performance benefits expected, but there’s so little time to gather some information… luckily, some users do provide us with empirical evidence 🙂