Zabbix discovery not creating new hosts

[Gideon]

Hello Zabbixers!
I have a really weird problem with my discovery. I need to monitor around 500 hosts with my Zabbix. These are camera's, switches, wireless devices, servers and workstations. Everything runs fine, but the servers and workstations are giving me a hard time.

They are Windows 2003/2008/2012 servers, also some Windows 7 workstations. This means we are using the Zabbix agent to do most of the communication.

The problem is that Zabbix is discovering the devices, but only some are created into a host. To be as clear as possible, have some screenshots:

Discovery rule:


Action:


Discovered hosts (Monitoring > Discovery):
Huge img, link to preserve format

If you look at the last screenshot (the link), the discovered host with the ip 172.22.20.15 is not added as a host, though all the demands are met.

Is there a reason why these are not added?

[liquidsnake1989]

I'm interested in knowing this as well.

[ingus.vilnis]

Hi guys,

The problem I think is in condition C Received value = Windows.

https://www.zabbix.com/documentation/2.4/manual/config/notifications/action/conditions

Received value
= - equal to the value.
<> - not equal to the value.
>= - more or equal to the value.
<= - less or equal to the value.
like - contains the substring. Parameter is given as a string.
not like - does not contain the substring. Parameter is given as a string.

So you have specified that the received value has to be exact match to value "Windows". But then check what information system.uname item actually returns on a Windows machine:

[root@hostname ~]# zabbix_get -s 192.168.1.2 -k system.uname
Windows HOSTNAME 6.1.7601 Microsoft Windows 7 Professional Service Pack 1 x64

See, it contains much more info. Please change the condition to Received value like Windows and try again. in that case the keyword will be matched and host added.

And a minor note on the discovery itself. I don't think that in your case you need three separate checks with type "Zabbix agent" if you don't actually utilize them. I think it is completely enough with ICMP Ping and system.uname.

Hope this helps,
Ingus

[liquidsnake1989]

Yes, that was the solution. Luckely we already found that out and fixed it, but thanks for your comprehensive response!