Simple discovery question: don't add if already present?

[Linwood]

I want discovery to notice new hosts (i.e. IP's).

I have a rule, when discovered, to add the host to the discovered hosts group, where I can review and decide how to treat it.

I only want hosts (by IP but name is OK) to be put here if they are not already defined in the system. "Defined" here could be "previously seen by this discovery rule" or could be "is already in the host list".

What is happening instead is that hosts (notably ones that go down periodically, appropriately) are firing the trigger even though already handled. If I use "Host discovered" for example, it will fire not only the first time but any time the host is off line for a while.

Now it is not all that hard to see things appear in discovered hosts, and realize they are already defined and remove them, but it is a nuisance.

I fell like this is something that ought to be very simple and I am just missing some variant of the rules, but there are just not many options there and I think I have experimented with them all.

Is the only alternative to just leave them in discovered hosts, and try in some fashion to "notice" them? I really like noting them simply by being present in discovered hosts.

[Linwood]

So... silly question? Not possible?

Silence usually means one or the other, if it's silly in some way, or I am approaching zabbix incorrectly, just say so.

[Linwood]

OK, it was a silly question. In case someone else will benefit...

I believed I needed to put a host in a host group in order to have the host entered. And indeed a host group is necessary, but it is not necessary to do so explicitly. If you take action (such as linking a template) and the host is not in a group, it puts the host automatically in the discovered hosts group (which can be overridden in the admin configuration).

So the way to get what I want is to have discovery running and linking to templates as needed, but do NOT have any of them explicitly add the newly discovered host to a group.

The net result is that RE-discovery of a host leaves the host right where it is.

But the discovery of a host not present will land in Discovered Host group which can be reviewed, processed and emptied. It becomes a queue that the administrator can review and place appropriately into groups, adjust templates, etc. as desired.

It was only because I was explicitly adding it to discovered hosts that ALL my hosts kept re-appearing there.