[ZBXNEXT-7679] Remove/disable trigger because of item not discovered anymore Created: 2022 May 06  Updated: 2022 Jun 08  Resolved: 2022 Jun 08

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Server (S)
Affects Version/s: 6.0.4, 6.2.0alpha2
Fix Version/s: None

Type: Change Request Priority: Minor
Reporter: Aigars Kadikis Assignee: Zabbix Development Team
Resolution: Duplicate Votes: 6
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File keep-lost-period-disable-remove-trigger.png    
Issue Links:
Duplicate
duplicates ZBXNEXT-2020 allow to configure whether not discov... Closed
Sub-task

 Description   

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.

Sometimes it can lead for triggers to go into problem state. 
Installing "Keep lost resources period=0" is not an option.

Solution could be to implement additional functionality to disable or remove trigger right after the item has not been discovered anymore:

 Comments   
Comment by Nathan Slusher [ 2022 May 06 ]

This issue affects us frequently too. We also get alerts for items that are not discovered any more.

I agree that at the very least we should have the option to automatically disable a trigger when the underlying item is no longer present.

Generated at Mon Jun 09 07:19:30 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.