Zabbix Frontend needs to be simplified and the additions of a few new features could do this. One of the main issues with Zabbix is that we have all forgotten that not all IT personnel have programming logic or programming experience under their belt; nor do all members of an IT team spend any amount of time setting up Zabbix. A few ways to help coerce the IT members into using Zabbix would be to remove a bunch of the menus that they wouldn't need access to, this could be done via Implementation of more 'Rights Managements' for users and groups, which will help the user not 'fear' Zabbix.

All to often I find myself in a situation where I'm looking at the dashboard, trying to figure out what exactly happened with a host or trying to sift through the all of the alerts that it has generated to be able to see what has actually happened; due to multi-tiered monitoring multiple alerts may trigger while only one of them may be valid. I envision the Zabbix Dashboard having a ToolTipText while hovering over specific Triggered alerts. This way a user without the rights or knowledge about what the trigger does can have the Trigger Description from the item appear right before them. This would greatly help communities where English isn't their mother tongue; as trigger descriptions could be written in another language to help that IT understand it better.
Trigger names aren't the only solution to the problem, one must not simply just 'give the trigger a 256 character name'. In order to keep any type of naming scheme while creating triggers within the organization, one must utilize the description to be able to identify what the problem is.

The other feature I would like to see in Zabbix is a temporary notification displayed or until an acknowledgement has been made, such as with any popular Instant Messaging program. A little partially transparent popup in the bottom right hand corner could help identify issues within the Hosts that Zabbix monitors. This popup can contain the Description of the trigger.

Environments where NMS software isn't deployed these companies are looking at alternatives, and the last thing that a company wants is to have one person with the experience and no one else with any knowledge. I believe Zabbix does this by mistake with such a complex interface.

For large environments, it is common to see monitoring systems being projected onto Television screens/monitors. Currently with Zabbix, you need to log into the Zabbix interface to be able to figure out what is going wrong, you shouldn't have to, you should be able to look at the television screen and be able to identify the issue without wasting valuable time trying to figure out how to use it to fix the situation. Downtime is money, and for companies looking at opensource alternatives; money isn't always available to invest in proprietary systems or in time that is not well spent.

If I can clarify anything better, please let me know. I see a better future for Zabbix. I am optimistic that we can, as a community, take this software to the next level; make it available to everyone without access to Enterprise knowledge.

Key Issue: Zabbix Frontend is designed for an administrator who set up Zabbix, not for the IT team. We need to streamline basic concepts into the Dashboard, "A problem has been identified" and "This is what could have caused the problem."