Dear all
I have a question regarding LLD network interface discovery.
(The situation is the same for a ZABBIX prod instance running with version 2.4 and a staging instance running with ZABBIX 3.0.)
I have a group of nodes with many network interfaces, which are discovered properly with the standard LLD settings.
Now I have a requirement, to set a very specific trigger on just one specific interface on each node within this host group.
The interface name is bondx, where bond means bonding interface and x can be a any number. For example, there are bond5 and
bond7 interfaces on each node.
The requirement now is to configure a trigger an just the bond5 interface on each node within this host group.
1) The approach how it works:
a) Under the LLD configuration for the network interfaces, I changed the filter setting for the network interface discovery rule:
This filter setting contains a rule "A" with a macro "{#IFNAME}" matching the "@Network interfaces for discovery" regular expression.
Under Administration -> General -> Regular Expression, I have changed the expression "Network interfaces for discovery" to exclude the
bond5 interface from being discovered through adding the expression
^bond5 [Result is FALSE]
b) In the second step I have configured the bond5 interface manually in a template, which is linked to this host group and configured the
corresponding trigger within the same template.
2) The Approache, which I initially tried but did not work:
a) At first I tried to implement approach 1) through a separate LLD discovery rule (the same as the pre-configured network
interface LLD rule) but with a filter, which just filters the for the bond5 interface. Then I planned to add a corresponding
trigger prototype, which should provide the same functionality given by approach 1).
The problem occured, when I configured the LLD rule for bond5, an error message came up saying, that the key "net.if.discovery"
(the discovery rule key) is already used on the same host (which came up for all hosts of this host group).
I understand that the same item key cannot be assigned to a host twice. But it seems, there is the same rule applied also for
discovery keys. If the same discovery key is used in combination with different filters, then the use of the same discovery key should
be allowed to be used multiple times on the same host.
My questions are:
Q1: Can the same discovery key be applied to the same host multiple times or not, if the key is combined with different filters?
If yes, what did I do wrong?
Q2: What is the best approach to apply different triggers to the same LLD items (which are discovered by the same discovery rule)?
I have a question regarding LLD network interface discovery.
(The situation is the same for a ZABBIX prod instance running with version 2.4 and a staging instance running with ZABBIX 3.0.)
I have a group of nodes with many network interfaces, which are discovered properly with the standard LLD settings.
Now I have a requirement, to set a very specific trigger on just one specific interface on each node within this host group.
The interface name is bondx, where bond means bonding interface and x can be a any number. For example, there are bond5 and
bond7 interfaces on each node.
The requirement now is to configure a trigger an just the bond5 interface on each node within this host group.
1) The approach how it works:
a) Under the LLD configuration for the network interfaces, I changed the filter setting for the network interface discovery rule:
This filter setting contains a rule "A" with a macro "{#IFNAME}" matching the "@Network interfaces for discovery" regular expression.
Under Administration -> General -> Regular Expression, I have changed the expression "Network interfaces for discovery" to exclude the
bond5 interface from being discovered through adding the expression
^bond5 [Result is FALSE]
b) In the second step I have configured the bond5 interface manually in a template, which is linked to this host group and configured the
corresponding trigger within the same template.
2) The Approache, which I initially tried but did not work:
a) At first I tried to implement approach 1) through a separate LLD discovery rule (the same as the pre-configured network
interface LLD rule) but with a filter, which just filters the for the bond5 interface. Then I planned to add a corresponding
trigger prototype, which should provide the same functionality given by approach 1).
The problem occured, when I configured the LLD rule for bond5, an error message came up saying, that the key "net.if.discovery"
(the discovery rule key) is already used on the same host (which came up for all hosts of this host group).
I understand that the same item key cannot be assigned to a host twice. But it seems, there is the same rule applied also for
discovery keys. If the same discovery key is used in combination with different filters, then the use of the same discovery key should
be allowed to be used multiple times on the same host.
My questions are:
Q1: Can the same discovery key be applied to the same host multiple times or not, if the key is combined with different filters?
If yes, what did I do wrong?
Q2: What is the best approach to apply different triggers to the same LLD items (which are discovered by the same discovery rule)?
Comment