-
Type:
Problem report
-
Resolution: Commercial support required
-
Priority:
Trivial
-
None
-
Affects Version/s: 5.0.27
-
Component/s: Frontend (F)
-
Environment:O.S - Redhat 7.9
Description CPU Memory
Zabbix Web 4 8G
Zabbix Server 4 24G
MySQL DB Server 4 32G
Proxy 1 12 32G
Proxy 2 4 12G
Proxy 3 4 8G
Number of hosts (enabled/disabled) 12615 12614 / 1
Number of items (enabled/disabled/not supported) 834056 520595 / 268845 / 44616
Number of triggers (enabled/disabled [problem/ok]) 414530 267396 / 147134 [3047 / 264349]
Number of users (online) 546 11
Required server performance, new values per second 2625.3O.S - Redhat 7.9 Description CPU Memory Zabbix Web 4 8G Zabbix Server 4 24G MySQL DB Server 4 32G Proxy 1 12 32G Proxy 2 4 12G Proxy 3 4 8G Number of hosts (enabled/disabled) 12615 12614 / 1 Number of items (enabled/disabled/not supported) 834056 520595 / 268845 / 44616 Number of triggers (enabled/disabled [problem/ok]) 414530 267396 / 147134 [3047 / 264349] Number of users (online) 546 11 Required server performance, new values per second 2625.3
Steps to reproduce:
Keep the Zabbix portal standby for at least 30 minutes.
Result:
See screenshot...
Expected:
To get the live data without going in loading state.
To resume monitoring we need to do hard refresh entire page manually.
