[ZBX-25093] Unsupported items not clearing out Created: 2024 Aug 22  Updated: 2025 Mar 18  Resolved: 2025 Mar 18

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Documentation (D)
Affects Version/s: 7.0.3
Fix Version/s: 6.0.40rc1, 7.0.11rc1, 7.2.5rc1, 7.4.0beta1 (master)

Type: Documentation task Priority: Trivial
Reporter: Tammy T Assignee: Andrii Fediuk
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2024-08-22-10-57-44-557.png     PNG File image-2024-08-22-10-58-06-271.png     PNG File image-2024-08-22-10-58-29-809.png    
Team: Team A
Sprint: S24-W34/35, S24-W40/41, DOC S25-W2/3
Story Points: 0.25

 Description   

Issue I noticed during tests while implementing a template:{}

Steps to reproduce:

  1. Create item without custom on fail to test item return on servers 
  2. After fixing issues, implement on template custom on fail to discard value 
  3. clear history and trends of all items
  4. unsupported items generated during tests/implementation are not resolved even without no data, after +1 month waiting and multiple manual executions of housekeeper. 
  5. Behavior found also on disabled hosts where I cleaned the history of the unsupported items with no success (tried enabling the host to try to clean history and force housekeeper execution also with no success)

Result:


Expected:
Without history, the unsupported item error to disappear 



 Comments   
Comment by Tammy T [ 2024 Aug 22 ]

Reattaching images that broke:


Comment by Alexander Vladishev [ 2024 Aug 22 ]

As I understand from the description, the issue is that items that do not receive historical data remain in the Unsupported state. This is expected behavior. An item transitions to a normal state only when it receives new valid historical data.

Comment by Ilja Fedotjevs [ 2024 Aug 26 ]

Hi Tammy,
is there anything else we can help you with or this report can be closed?

Thanks!

BR,

Zabbix support

Comment by Tammy T [ 2024 Aug 26 ]

Thank you for the answer Alexander, so, just to make it clear for me: unsupported items have a similar behavior to problems, where it only reevaluates if receives new data even if there is no historical data at all for that item anymore?

Comment by Alexander Vladishev [ 2024 Aug 26 ]

Yes, items and triggers change their state only when new data is received. However, if a trigger expression contains a time-based function, such a trigger will be also recalculated every 30 seconds. See Triggers calculation time.

Comment by Tammy T [ 2024 Aug 26 ]

Thank you for the explanation. I will check if there are any feature requests related to this, but for now, you can close this ticket.
Have a great day

Comment by Tammy T [ 2024 Aug 26 ]

Suggestion: Add this information about unsupported items to the documentation. I could not find anything related to that there

Comment by Alexander Vladishev [ 2024 Aug 26 ]

Thank you for the suggestion. We will add this to the documentation.

Comment by Andrii Fediuk [ 2025 Mar 04 ]

Updated documentation:

  • Creating an item: 6.0, 7.0, 7.2, 7.4 (The "Unsupported items" section has been updated).
Generated at Mon Apr 07 00:43:39 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.