Loading...

XML

Word

Printable

Type: Problem report
Resolution: Fixed
Priority: Major
Fix Version/s: 3.4.4rc1, 4.0.0alpha1, 4.0 (plan)
Affects Version/s: 3.4.1, 3.4.2
Component/s: Frontend (F)
Labels:
- frontend
Environment:

Hide
CentOS7.0
zabbix-agent-3.4.1-1.el7.x86_64
zabbix-release-3.4-1.el7.centos.noarch
zabbix-web-mysql-3.4.1-1.el7.noarch
zabbix-server-mysql-3.4.1-1.el7.x86_64
zabbix-web-3.4.1-1.el7.noarch
zabbix-get-3.4.1-1.el7.x86_64

Show
CentOS7.0 zabbix-agent-3.4.1-1.el7.x86_64 zabbix-release-3.4-1.el7.centos.noarch zabbix-web-mysql-3.4.1-1.el7.noarch zabbix-server-mysql-3.4.1-1.el7.x86_64 zabbix-web-3.4.1-1.el7.noarch zabbix-get-3.4.1-1.el7.x86_64

Sprint:
Sprint 17, Sprint 18, Sprint 19
Story Points:
0.5

I used Event correlation in ZABBIX for the verification work
I moved to the Dashboard, after confirming the operation of Monitoring Problems.
The attached image was displayed.

I edited the following and confirmed that the problem improved.
/usr/share/zabbix/app/views/monitoring.widget.problems.view.php
l.849

before
array_key_exists($problem['correlationid'], $data['correlations'])

after
TRUE == isset($data['correlations']) &&array_key_exists($problem['correlationid'], $data['correlations'])