Details
-
Type:
Incident report
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 3.2.3
-
Fix Version/s: 3.2.5rc1, 3.4.0alpha1
-
Component/s: Proxy (P), Server (S)
-
Labels:
-
Team:Team A
-
Sprint:Sprint 2, Sprint 3
-
Story Points:5
Description
Create trigger with multiple event generation.
Problem: {test server:trap1.last()}=0 Recovery: {test server:trap2.last()}=1
Make it go in problem state
./bin/zabbix_sender -z 127.0.0.1 -p 10051 -s "test server" -k trap1 -o 0
Now change recovery value
./bin/zabbix_sender -z 127.0.0.1 -p 10051 -s "test server" -k trap2 -o 1
Expected:
You see one problem
Actual:
There are 2 problems, one for problem the other for recovery value change.
The same apply to time based functions which are implemented in ZBX-11444.
Timer function in recovery expression shall not generate multiple problem events.
Create trigger
trap_trig Problem: {test server:trap1.last()}=0 Recovery: {test server:trap1.nodata(60)}=1
Make it go in problem state
./bin/zabbix_sender -z 127.0.0.1 -p 10051 -s "test server" -k trap1 -o 0
Wait more than 1 minute
Expected:
You see only one problem event.
Actual:
New problem event is generated every 30 seconds.