[ZBXNEXT-1547] additional trigger dependency calculation algorithms Created: 2012 Dec 13  Updated: 2025 Mar 06

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: API (A), Frontend (F), Server (S)
Affects Version/s: None
Fix Version/s: None

Type: New Feature Request Priority: Trivial
Reporter: richlv Assignee: dimir
Resolution: Unresolved Votes: 21
Labels: triggerdependencies, triggers
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File zbx_dependency_relationship_backend.patch     File zbx_dependency_relationship_frontend.patch    
Issue Links:
Duplicate
is duplicated by ZBXNEXT-7504 Allow logic (AND/OR etc...) to confir... Closed
is duplicated by ZBXNEXT-3181 Allow selecting condition between dep... Closed
is duplicated by ZBXNEXT-9866 Allow AND/OR for trigger dependencies Closed

 Description   

currently a trigger that depends in several other triggers is "muted" if one of those triggers fires. a more fine grained control would be desirable.
for example, there could be 3 options :

a) OR (works as the current implementation - mutes if any one trigger fires)
b) AND (mutes only when all triggers have fired)
c) % (mutes if more than n% of triggers have fired)

 Comments   
Comment by Marc [ 2012 Dec 14 ]

Maybe in a similar way conditions are defined for actions.
d) AND/OR

<richlv> hmm, in action conditions we have condition types that can be used to determine and/or. how should it work in trigger deps ?

Comment by Volker Fröhlich [ 2013 Mar 01 ]

Loosely connected to ZBXNEXT-1461

Comment by Gustavo Moura de Sousa [ 2013 Mar 18 ]

I would like to have this feature implemente too.
I would be very usefull.

Comment by diana vasconcelos [ 2013 Mar 20 ]

yes it would be very useful to have the possibility to configure relationships between dependancy.

Comment by Benjamin Gronvall [ 2013 Dec 23 ]

I would love this to be implemented on priority. There are several instances in my networking infrastructure where this would provide greater monitoring flexibility.

Comment by Gustavo Moura de Sousa [ 2015 Aug 20 ]

Today if a host depends on two hosts, but only if botth are down, we have to generate a third trigger.
It will be nice if we could configure dependency between hosts as
ZBXNEXT-46

Comment by Kevin Daudt [ 2016 Jul 26 ]

I've attached that partially implement this.

Included:

  • Server side changes to check the dependency relationship
  • Frontend-changes to change the relationship

Missing:

  • API changes to take the relationship into account for the front-end. The current code is not recursive, making it harder to check this relationship recursively.
  • Setting the amount of dependencies. Only AND/OR.

Feedback would be appreciated.

Comment by Alexei Vladishev [ 2016 Aug 03 ]

Thanks for the patch! I like the functionality however it's not clear if it will be integrated into Zabbix or not. We are evaluating different options of simplifying management of dependencies and still not sure what might be the best implementation.

Comment by Kevin Daudt [ 2016 Aug 04 ]

Thanks. I'm curious to see any improvements to dependency management.

Comment by Raymond Kuiper [ 2025 Mar 06 ]

As a follow-up on ZBXNEXT-9866:

dimir can you make sure the issue is assigned to someone?

Comment by dimir [ 2025 Mar 06 ]

Unfortunately it won't do any good if I assign it to a random person. I can assign it to myself if you insist.

Generated at Fri Apr 11 22:08:24 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.