-
Incident report
-
Resolution: Fixed
-
Major
-
None
-
3.2.4, 3.2.5rc1
-
3.2.4, Centos7
-
Sprint 4, Sprint 5
-
2
Global correlation doesn't work if events are created at the same time.
To reproduce:
1. Create test item with key:
test
and type Zabbix trapper
2. Create anoter test item with key:
test2
and type Zabbix trapper
2. Create two triggers. both with exactly the same expression:
{host:test.last()}=0
add Tag called 'Test' with no value.
3. Create another trigger with expression:
{host:test2.last()}=0
add Tag called 'Test' with no value.
4.Create global correlation rule:
with conditions:
and action: 'close new event'
5. Now , from console run zabbix_sender cli:
zabbix_sender -z 127.0.0.1 -s "Zabbix server" -k test -o 0
you would see that both triggers are created active .
NOT CORRELATED as expected!
6. Now run:
zabbix_sender -z 127.0.0.1 -s "Zabbix server" -k test2 -o 0
Because of time delay between 5 and 6, you would see that new event from third trigger is correlated properly.
Same issue is seen with some real SNMP based triggers
- is duplicated by
-
ZBX-17769 event correlation not working when correlated items are reported in one zabbix_sender session
- Confirmed