dynamic Trigger dependencies

[chlehmann]

Hi community
Our zabbix-setup is getting more and more complex and we start to face some issues because of that. One - and maybe the most annoying - is the trigger-dependency-thing.

We had to split the ICMP-template into two different ones, one called SLOW. The reason is that with our current cmdb we are not able to easily pass macros to a host, and therefore we can't dynamically set the treshold of the ICMP-ping-down trigger.

Because of this segmentation it's no longer possible to have a dependency from any other template to "ICMP-ping down". I just never know if ICMPing_down or ICMP_SLOWing_down exists on a host. The items are both present, but from other templates. Any ideas of solving this issue?
I'd like to have a way of telling zabbix which item is "master", and if this goes red, everything else will not raise triggers. would that somehow be possible?

Chris

[kloczek]

Two weeks ago I've started writing script which allows list, create, delete and update host macros.
It is still not fully finish but it allows to do above basic operations on host mactos in batch mode which van be plugged in to CMDP pipeline.

https://github.com/kloczek/zapish/blob/master/examples/host_macro