Dynamic trigger dependencies between LLD triggers and other hosts
Hello everyone,
I have created an LLD rule in Zabbix that discovers all interfaces belonging to PortChannels and, for each interface, dynamically creates the corresponding items and triggers, also using the interface description.
My infrastructure is structured as follows:
The problem I would like to solve is related to trigger dependencies.
I would like to dynamically associate each interface discovered by the LLD with its corresponding floor switch, so that the trigger generated by the LLD takes the status of that floor switch into account.
More specifically, I would like the following behavior:
If the trigger for an interface on HOST A fires, I want to receive a notification only if the corresponding floor switch is UP according to its ICMP Ping item.
If the floor switch is DOWN, I do not want to receive a notification for the PortChannel interface, because in that case the interface problem may simply be a consequence of the floor switch being unreachable.
So, essentially, I would like to create a relationship such as:
HOST A → LLD-discovered PortChannel interface → associated floor switch → ICMP Ping status
The difficulty is that both the interfaces and their corresponding triggers are created dynamically by the LLD. I also have multiple floor switches, so I would like to avoid manually creating a dependency for every single trigger.
What would be the correct way to implement this kind of dynamic dependency in Zabbix?
Is it possible to achieve this using LLD macros, trigger prototypes, or trigger dependencies, without having to manually configure each individual relationship?
I have created an LLD rule in Zabbix that discovers all interfaces belonging to PortChannels and, for each interface, dynamically creates the corresponding items and triggers, also using the interface description.
My infrastructure is structured as follows:
- HOST A is the main switch where the LLD is running.
- The LLD discovers the interfaces that are members of PortChannels and automatically creates the corresponding items and triggers.
- Each of these interfaces is connected to a specific floor switch.
- Each floor switch is configured in Zabbix as a separate host and is monitored using an ICMP Ping item.
The problem I would like to solve is related to trigger dependencies.
I would like to dynamically associate each interface discovered by the LLD with its corresponding floor switch, so that the trigger generated by the LLD takes the status of that floor switch into account.
More specifically, I would like the following behavior:
If the trigger for an interface on HOST A fires, I want to receive a notification only if the corresponding floor switch is UP according to its ICMP Ping item.
If the floor switch is DOWN, I do not want to receive a notification for the PortChannel interface, because in that case the interface problem may simply be a consequence of the floor switch being unreachable.
So, essentially, I would like to create a relationship such as:
HOST A → LLD-discovered PortChannel interface → associated floor switch → ICMP Ping status
The difficulty is that both the interfaces and their corresponding triggers are created dynamically by the LLD. I also have multiple floor switches, so I would like to avoid manually creating a dependency for every single trigger.
What would be the correct way to implement this kind of dynamic dependency in Zabbix?
Is it possible to achieve this using LLD macros, trigger prototypes, or trigger dependencies, without having to manually configure each individual relationship?