Low Level Discovery - Disable items not discovered anymore

[hwidjaja]

Using LLD, we can keep lost resources (in days) but the item's status is still enabled.

When the item is not discovered anymore, is it possible to change the item's status to disabled while keeping it before it gets deleted?

[rrupp]

I would really like this feature added as well! Basically, I would like Zabbix low level discovery to work in the following manner:

- If an item is no longer discovered disable it
- If the item is rediscovered, re-enable it
- Eventually if the item isn't discoverable after X amount of time, remove it (this functionality is already there today)

Today, I believe what happens is the item will just fail and go to "not supported" but it will be renabled after X amount of time (depending on your setting for how often you want to re-enable unsupported items). This creates overhead then though as the item will just fail again (until it is discovered again). My company uses low level discovery a fair amount for dynamic JMX items.

[BDiE8VNy]

There is already an issue report about this:
See: ZBX-4475

However, there might be some use cases what rely on this behavior:
See: ZBX-6315

[GateKeeper]

Being ZBX-6315 not cared for a long time I've proposed a patch here: https://support.zabbix.com/secure/at...12/lld-c.patch

That's a raw patch, requires some cleanup at least, but I'd be glad to see someone has at least looked at it and tried. Though, the mess developers have done to flag checking in various places of code (server and web-interface) leads to the requirement of thorough code refactoring at where ZBX_FLAG_* are set/compared.

I've also mentioned that there was a commit in svn-trunk where lld.c was split into lld-trigger.c/lld-graph.c/etc. This makes my patch a bit unappliable against current trunk head.