We are using Zabbix over a year, and it was working OK till we ran into this issue of very slow trigger page loading out of blue, without any change in configuration (cant say same about network guys).
We have separate Zabbix DB Server (MySQL) and Zabbix Web Server (Apache), both running on RHEL 6.6 .
We are using Zabbix 2.2.9 (Planning to upgrade soon !) with 8000+ hosts and we have all the hosts in same group for monitoring team to view all the triggers at the same time. Hence, we have to keep the "Dropdown first entry" to "All".
I know the setup may not be best but we have to live with that for time being.
We have also come to know that in trigger page the more the conditions (non super admin, filters etc), the more loop it goes through and hence more time.
Before
- Trigger page loading was fast (between 10-15 seconds) for super admin in all scenarios
- Trigger page loading was acceptable ( between 20-25 seconds) for normal users (monitoring team) with filter applied on acknowledged triggers
Now
- Trigger page loading is very slow (> 15 seconds) for super admin without any filter
- Trigger page loading is taking eternity for super admin and normal users with filters
There is no problem with the CPU processes etc.
I am not sure if there is any problem with TCP ports or OS etc.
Anyone have an idea on what to look at or any similar experience ?
Thank you in advance,
Shriharsh
We have separate Zabbix DB Server (MySQL) and Zabbix Web Server (Apache), both running on RHEL 6.6 .
We are using Zabbix 2.2.9 (Planning to upgrade soon !) with 8000+ hosts and we have all the hosts in same group for monitoring team to view all the triggers at the same time. Hence, we have to keep the "Dropdown first entry" to "All".
I know the setup may not be best but we have to live with that for time being.
We have also come to know that in trigger page the more the conditions (non super admin, filters etc), the more loop it goes through and hence more time.
Before
- Trigger page loading was fast (between 10-15 seconds) for super admin in all scenarios
- Trigger page loading was acceptable ( between 20-25 seconds) for normal users (monitoring team) with filter applied on acknowledged triggers
Now
- Trigger page loading is very slow (> 15 seconds) for super admin without any filter
- Trigger page loading is taking eternity for super admin and normal users with filters
There is no problem with the CPU processes etc.
I am not sure if there is any problem with TCP ports or OS etc.
Anyone have an idea on what to look at or any similar experience ?
Thank you in advance,
Shriharsh