icmp_ping_5.0_trigger_dependency.png
[ZBX-17854] Trigger dependency Created: 2020 Jun 01 Updated: 2020 Jun 08 Resolved: 2020 Jun 08 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 5.0.1 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Trivial |
| Reporter: | Dej Tronschik | Assignee: | Kristians Pavars |
| Resolution: | Won't fix | Votes: | 0 |
| Labels: | dependency, trigger | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS7, postgresql 9.2.24, z-agent/get/sender/server-pgsq/web* 5.0.1 |
||
| Attachments: |
icmp_ping_5.0_trigger_dependency.png
|
| Description |
|
Steps to reproduce:
Result: No trigger PROBLEM value follows for dependent values See screenshot attached. |
| Comments |
| Comment by Kristians Pavars [ 2020 Jun 02 ] |
|
Hi Dej,
That is the intended functionality of dependent items. With such dependency the dependent trigger will not change state as long as the trigger it depends on is in 'PROBLEM' state - and thus no dependent actions will be taken and no notifications sent. You can read more about dependencies in Zabbix documentation: https://www.zabbix.com/documentation/current/manual/config/triggers/dependencies
With this I will be closing this ticket as it won't be fixed.
Regards, Kristians Pavars |
| Comment by Dej Tronschik [ 2020 Jun 04 ] |
|
I was firmly convinced that in previous 4.x version I've always got actions on this dependent trigger in "High ICMP ping loss" and "High ICMP ping response time" actions for target units... |