Hi.
First of all - long live Zabbix... What a great app. Thanks!!
We are trying to setup Zabbix in such a way that hosts with Zabbix agent installed will be discovered, added and then linked to the correct template based on their OS type (that uses the Zabbix agent to monitor the server) and hosts that don't have Zabbix agent installed will be discovered, added and linked to the correct template based on their OS type (that uses the WMI by the zbxwmi script to monitor the server).
We already have found the correct templates for both cases and if we link the servers to the templates manually it works fine. We tried to configure the discovery and the discovery actions in the following way:
1. We created a discovery rule that scans all of our network via ICMP pings, port 135 TCP and Zabbix agent (querying 'system.uname').
2. We created a discovery action that adds the host and links it to the Windows-WMI template if the returned value is not like Windows and the service port is 135 TCP and the discovery status is up.
3. We created a discovery action that adds the host and links it to the Windows-ZabbixAgent template if the returned value is like Windows and the service type is zabbix-agent.
The problem we're currently facing is that the Windows hosts are getting linked to both templates. I didn't mention it for clarity butwe also have some Linux hosts for which we have defined similar discovery rules and actions (using SSH instead of 135TCP to detect that it isn't Windows). Basically, if there was (or maybe there is?) a way to create a discovery action condition such as (A AND B) OR (D AND E). I think that I could have accomplished this...
Any help would be appreciated...
Yuval.
First of all - long live Zabbix... What a great app. Thanks!!
We are trying to setup Zabbix in such a way that hosts with Zabbix agent installed will be discovered, added and then linked to the correct template based on their OS type (that uses the Zabbix agent to monitor the server) and hosts that don't have Zabbix agent installed will be discovered, added and linked to the correct template based on their OS type (that uses the WMI by the zbxwmi script to monitor the server).
We already have found the correct templates for both cases and if we link the servers to the templates manually it works fine. We tried to configure the discovery and the discovery actions in the following way:
1. We created a discovery rule that scans all of our network via ICMP pings, port 135 TCP and Zabbix agent (querying 'system.uname').
2. We created a discovery action that adds the host and links it to the Windows-WMI template if the returned value is not like Windows and the service port is 135 TCP and the discovery status is up.
3. We created a discovery action that adds the host and links it to the Windows-ZabbixAgent template if the returned value is like Windows and the service type is zabbix-agent.
The problem we're currently facing is that the Windows hosts are getting linked to both templates. I didn't mention it for clarity butwe also have some Linux hosts for which we have defined similar discovery rules and actions (using SSH instead of 135TCP to detect that it isn't Windows). Basically, if there was (or maybe there is?) a way to create a discovery action condition such as (A AND B) OR (D AND E). I think that I could have accomplished this...
Any help would be appreciated...
Yuval.