There are some more requirements for a central display: it should open automatically upon boot and display the desired information, for example, a nice geographical map. While this might be achieved with some client-side scripting, there's a much easier solution, which we have already explored.

As a reminder, go to Administration | Users, click on monitoring_user in the Alias column, and look at two of the options: Auto-login and URL (after login):

If we marked the Auto-login option for a user that is used by such a display station, it would be enough to log in once, and that user would be logged in automatically upon each page access. This feature relies on browser cookies, so the browser used should support and store cookies. The URL (after login) option allows the user to immediately navigate to a specified page. All that's left is that the display box launches a browser upon boot and point, to the Zabbix frontend URL, which should be simple to set up. When the box starts up, it will, without any manual intervention, open the specified page (which will usually be a screen or slideshow). For example, to open a screen with an ID of 21 whenever that user accesses the Zabbix frontend, a URL like this could be used: http://zabbix.frontend/zabbix/screens.php?elementid=21. To open that screen in Zabbix's fullscreen mode, a fullscreen parameter has to be appended: http://zabbix.frontend/zabbix/screens.php?elementid=21&fullscreen=1.

When displaying data on such large screens, explore the available options and functionality carefully; perhaps the latest data display is the most appropriate in some cases. When using trigger overviews, evaluate the host/trigger relationship and choose which should be displayed on which axis.