-
Type:
Incident report
-
Resolution: Unresolved
-
Priority:
Trivial
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
Steps to reproduce:
- Install fresh Zabbix 7.0.x version
- Configure a trigger action that will immediatelly run a shell script (via Media Type, with no concurrent sessions) on an event/problem creation or resolution if some tag either exists or does not exist with a certain value
- Wait some time and observe (see screenshot)
- Note: there's nothing in server log, no failure, action is for some reason completely skipped and it happens randomly (random host, trigger, etc...)
Result:
See screenshots from 2 Zabbix v7.0.3 and 7.0.4 environments...
Note: I have not noticed this behavior in Zabbix 6.0.x
Expected:
Trigger action is executed on every generated event/problem (or resolution) based on the trigger action rule definition (with execution status visible in the UI)