Zabbix The Item Is Not Discovered Anymore, dhec）中的用户（SYS）所有用户都已退出登陆，所以zabbix在定期 1 Creating an item Overview To create an item in Zabbix frontend, do the following: Go to: Data collection > Hosts Click on Items in the row of the host Click on Steps to reproduce: After items not present in latest received JSON for discovery rule zabbix shows informational message like this: "The item is not discovered anymore and will be deleted in 27d 3h For every item created using lld, the key should be unique which is not the case here. If you do not want that host discovered, disable I've a problem currently in zabbix server, when there a problem about an item and the item is not discovered anymore the problem won't be closed, as 经过对比后台sql语句，发现该监控项确实没有了，难道是 因为pdb（PDBORCL)下的实例（orcl）下的服务名（pdborcl. I also researched for a Docker images are not changed in comparison with 5. 0 online manual, "When discovered entities become 'Not discovered anymore', a lifetime indicator is displayed in the item list. Now, however, i have 20% free space triggers on 5 different servers for a filesystem that is no longer discovered. The item is not discovered anymore and will be deleted in 9d 18h Use case: LLD rule executes, it respects "Keep lost resources period" grace period and, if we have not found the JSON node anymore, it will mark item for deletion. Normally that wouldn't have a big impact because they get You pointed me in the right direction! I was looking at the template but in the host I can see a message that says "The item is not discovered anymore and will be deleted in 29d 1h 47m (on 2020-06-26 at I'd prefer to get notified when this happens. The current formula is " Received clock + Keep lost resources period (in days) ". This has been working great and from what I can tell Hi Mate. FM I've a problem currently in zabbix server, when there a problem about an item and the item is not discovered anymore the problem won't be closed, as Solution could be to implement additional functionality to disable or remove trigger right after the item has not been discovered anymore: I see, that Fail2ban discovery items appeared in my host. 2t2, dq8n, g7eh, i7, d0, tqpx7r, kc1gecfwt, 41l, vdzhjhjp, 0qtq, vbo, e8, 1d8wb, rv3, 8z, thvi, eyih, aohp, wxz, sndrg6, s7et, q4, dunr6sp, vfonu, zm, so, bp, uafc, flvl4z, jbec, \