Network discovery - remove host

[gmichels]

Hi all,

Zabbix server version 2.2.2.

I have a discovery rule in my network which I have assigned two actions for adding and removing hosts. Pretty much copy & paste what is in the manual (https://www.zabbix.com/documentation...discovery/rule).

Actions are working fine, servers get added & removed as expected. One thing I didn't expect though is a removed server to be still showing up in the discovered hosts table.



Is this by design? If so, at one point in time there will be a lot of "red" entries. Red is a visual indicator of a problem, and in this case it really isn't a problem as everything is happening as expected. I can't seem to find a way to remove that host from the table.

Can anyone shed some light in this?

Thank you

[fpaternot]

I'd believe it is corretct. Its not necessarily a problem (trigger). It is just telling you that it was once there but now its not responding anymore..

The host is marked as "Lost" (red). If you reuse that ip to another host, it would then clear it and show as green.

https://www.zabbix.com/documentation/2.2/manual/discovery/network_discovery#discovery

[gmichels]

Agreed it's no problem in the trigger sense, but I believe that table might get full of red stale entries as time passes and servers are added/removed (my company does not usually re-use IPs), because there's no way to clean it up.

I think it lacks this manual|automatic cleanup mechanism, other than that I think it works fine.

[fpaternot]

There are people that use this feature as network/security reports.


You can remove the discovery rule from time to time.. This way the lost hosts would be removed and the whole network would be discovered (and green) again.

[knightsg]

I know this thread is really old, but I'm experiencing this too and while I understand that it can be useful to retain the discovery info, the one issue I'm having with it is that we have an email to a user group set up as part of the discovery condition and we continue to get the notification that the host is down even after the discovery action has removed the host. It only goes away once I clear the host from the dservices and dhosts tables. Is there any solution to this particular problem?