[ZBX-20176] Trigger is still in UNKNOWN status when item becomes supported Created: 2021 Nov 04  Updated: 2024 Apr 10  Resolved: 2021 Nov 29

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 6.0.0alpha5
Fix Version/s: 5.0.18rc1, 5.4.8rc1, 6.0.0alpha7, 6.0 (plan)

Type: Problem report Priority: Critical
Reporter: Kaspars Mednis Assignee: Vladislavs Sokurenko
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Causes
caused by ZBX-19307 Reduce internal locking for the Zabbi... Closed
Duplicate
is duplicated by ZBX-20240 The trigger does not become "Unknown"... Closed
is duplicated by ZBX-20159 "evaluate function" test case failure... Closed
Team: Team A
Sprint: Sprint 82 (Nov 2021)
Story Points: 0.25

 Description   

Steps to reproduce:

  1. Create some item and trigger
  2. Make the item not supported (by sending wrong value type by example)
  3. Item is not supported, but the trigger still shows as enabled
  4. Send another wrong value
  5. Trigger will become unknown
  6. Send correct value, item will become supported
  7. Trigger is still UNKNOWN and is not calculated using this value
  8. Send another correct value
  9. Trigger now becomes enabled and calculates value

Result:
The same history syncer is making item supported, and then complaining that trigger can not be calculated because the same item is still not supported

Zabbix server log (truncated, only important lines left)

 229756:20211104:124536.902 zbx_setproctitle() title:'history syncer #1 [processed 0 values, 0 triggers in 0.000156 sec, syncing history]'
229756:20211104:124536.902 item "Test:test.item" became supported
229756:20211104:124536.902 query [txnlev:1] [update item_rtdata set state=0,error='' where itemid=39229;]
229756:20211104:124536.903 End of DBmass_update_items()
229756:20211104:124536.910 In recalculate_triggers()
229756:20211104:124536.911 zbx_substitute_functions_results() expression[0]:'{26692}=1' => 'ERROR(Cannot evaluate function last(/Test/test.item): item is not supported.)=1'
229756:20211104:124536.911 End of zbx_substitute_functions_results()
229756:20211104:124536.911 End of substitute_functions()
229756:20211104:124536.911 evaluate_expressions():expression [{26692}=1] cannot be evaluated: Cannot evaluate function last(/Test/test.item): item is not supported.
229756:20211104:124536.911 End of evaluate_expressions()
229756:20211104:124536.911 In zbx_process_triggers() values_num:1
229756:20211104:124536.911 In zbx_process_trigger() triggerid:20506 value:0(1) new_value:2
229756:20211104:124536.911 End of zbx_process_trigger():FAIL flags:0
229756:20211104:124536.911 End of zbx_process_triggers()
229756:20211104:124536.911 End of recalculate_triggers()
229756:20211104:124536.911 zbx_setproctitle() title:'history syncer #1 [processed 1 values, 1 triggers in 0.009759 sec, idle 1 sec]'

Expected:
When item becomes supported, trigger is calculated immediately using the value received.
Currently the very first value is always ignored

And vice versa, when item becomes not supported, trigger switches to unknown status immediately.

This may affect many customers, completely ignoring valid collected value is not expected from monitoring software. It will become even worse if the item has large update interval (hours or even days) or preprocessing steps with discard values

 

 Comments   
Comment by Kaspars Mednis [ 2021 Nov 04 ]

Confirmed.

Comment by Vladislavs Sokurenko [ 2021 Nov 08 ]

The problem occurred because after ZBX-19307 items that are already retrieved from cache are reused for triggers, meaning that we should also update item status in already retrieved items.

Comment by Vladislavs Sokurenko [ 2021 Nov 09 ]

Fixed in pull request feature/ZBX-20176-5.0

Comment by Vladislavs Sokurenko [ 2021 Nov 12 ]

Fixed in:

Generated at Fri Jul 04 07:21:48 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.