Generally, when we start using Zabbix, only the technicians who have installed Zabbix and are working as supporters for the environment have access to the frontend. But after a while, others will have access to the Zabbix frontend. So, the frontend performance will be tested and required much more than before.
As we already know, users can do amazing things with the software—things that developers cannot even think of during development. For example, in each user's profile configuration, it is possible to change their own settings:
Language
Theme
Auto-login
Auto-logout (minimum 90 seconds)
Refresh (in seconds)
Rows per page
URL (after login)
Well, where is the risk with these settings? You may have noticed that the risk is in Refresh and Rows per page. If the user decides to change Refresh to 5 and Rows per page to 10,000 then what will happen? We will have a problem—a user complaining that Zabbix screens are too slow to load.
Another point is the fact that we will create maps...