[ZBX-9933] Triggers stay in PROBLEM state for ressources that are not discovered anymore Created: 2015 Oct 02  Updated: 2019 Feb 05  Resolved: 2017 Oct 31

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: None
Affects Version/s: 2.4.6
Fix Version/s: None

Type: Incident report Priority: Major
Reporter: Tatapoum Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: lld, triggers
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates ZBX-12434 No one clear missed objects from problem Closed

 Description   

There is an annoying behavior of Zabbix with LLD. When a resource is not discovered anymore, if it was related to a trigger in PROBLEM state, the trigger never comes back to OK state. The trigger stays in PROBLEM even after the "Keep lost resources period". As there is no way to manually reset or clear a trigger created by a LLD rule, we have to unlink and clear the template and link it again to make the trigger disappear. For example, we have database state triggers that still fill the dashboard whereas they we deleted monthes ago.
This can be very problematic for "software" resources discovered with LLD (databases, filesystems, virtual servers, etc), as they are more likely to be removed when a problem occurs.

 Comments   
Comment by Oleksii Zagorskyi [ 2015 Oct 03 ]

Triggers should be deleted together with items according to "Keep lost resources period".
Triggers can not stay orphaned without items!

Describe please exact lld rule, item prototype, trigger prototype, trigger which stays in PROBLEM, returned JSON for the lld rule.

Comment by richlv [ 2017 Mar 29 ]

they might want to keep item/trigger in place for a while, but disable the trigger

Comment by richlv [ 2017 Oct 31 ]

i'd say that this is a feature request to allow configuring trigger state for items that are not discovered anymore, similar to ZBXNEXT-2020 (asks to allow enabling/disabling such items).

related - there was a documentation note added in ZBX-10684

Comment by Vladislavs Sokurenko [ 2017 Oct 31 ]

Closing as a duplicate of ZBX-12434, pleas upgrade and issue should go away immediately .

Comment by richlv [ 2017 Nov 01 ]

vso, if the description in that issue is correct, it is only concerned about removing problems when the trigger is already gone, not when it is still there and to be deleted later.

if so, i propose reopening this issue.

Comment by Vladislavs Sokurenko [ 2017 Nov 01 ]

Issue description states

For example, we have database state triggers that still fill the dashboard whereas they we deleted monthes ago.

Maybe something else was also nice to have, I would open separate feature request for that and reopen this only if problems are still not deleted. Do you still experience issue after upgrade ?

Comment by richlv [ 2017 Nov 01 ]

hmm, good point, but back in 2.4 there were no "problems" as a separate entity, so it could have been only about triggers

Comment by Vladislavs Sokurenko [ 2017 Nov 01 ]

There were events. Now events are also deleted by housekeeper if item/trigger deleted

Comment by richlv [ 2017 Nov 01 ]

if a trigger is deleted, events shouldn't matter much, right ?
in 2.4, that does not pop up in the dashboard, monitoring->triggers or elsewhere.

Comment by Vladislavs Sokurenko [ 2017 Nov 02 ]

One thing that it does not pop up the other thing is performance impact.
Also it might be different for discovered triggers, judging by user report. You can try and confirm this behaviour.

Comment by richlv [ 2019 Feb 05 ]

The underlying problem does not seem to be resolved; ZBXNEXT-2616 goes in a similar direction.

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