[ZBX-23124] Items without keeping history stay in Not supported status Created: 2023 Jul 19  Updated: 2024 Apr 10  Resolved: 2024 Feb 23

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F), Server (S)
Affects Version/s: 6.4.3
Fix Version/s: 6.0.27rc1, 6.4.12rc1, 7.0.0beta2, 7.0 (plan)

Type: Problem report Priority: Trivial
Reporter: Tomáš Skočdopole Assignee: Andris Zeila
Resolution: Fixed Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2023-07-19-05-42-56-036.png     PNG File image-2023-07-19-05-55-50-489.png     PNG File image-2023-07-19-05-58-15-115.png    
Team: Team A
Sprint: S2401-2, S24-W6/7
Story Points: 1

 Description   

Some items with the MSSQL by ODBC template assigned to a host being monitored via proxy are showing a status "Not supported", even though data is being collected correctly.

 

Execute now or Test does not fix the item state from Not supported to normal.

 

I have noticed that temporarily switching these items to "Keep history", refreshing the cache, and using Execute now causes the status to return to "normal". After disabling "Keep history", the item's status remains "Enabled" and continues to function correctly until a potential issue occurs.

 

 

Steps to reproduce:

  1. Create a host with MSSQL by ODBC template
  2. Verify everything is monitored correctly
  3. Arrange a problem (stop monitored MSSQL server or make network issue)
  4. Wait until item gets status Not supported
  5. Fix the problem from 3.
  6. Check the Latest data

Result:

Items without keeping history (Get last backup, Get performance counters,...) stays in Not supported state, but dependent items are collecting data normally.


Expected:
Get job status was manually corrected via workaround above

Get last backup and Get performance counters are in bad state

If you require any further details or logs, please let me know, and I will be happy to provide them.

 Comments   
Comment by Tomáš Heřmánek [ 2023 Jul 19 ]

When you enable history on this affected item, your status is recalculated to enabled (normal state). This is problem mainly on master items.

Comment by Tauri Jaanus [ 2023 Aug 16 ]

Same problem in 6.4.5 and with zabbix proxy in data flow.

Comment by Andris Zeila [ 2024 Jan 18 ]

The only way how I could reproduce the issue is by having item fail, then assigning host to proxy (changing proxies). Might this be the case ?

Normally after failing item starts working again proxy will send the first gathered value to server even if item's history is disabled. However if the item failed on server/other proxy then after assigning host to a new proxy the item states are not synced, so proxy thinks item was okay and will not send the 'recovery' value.

Comment by Andris Zeila [ 2024 Jan 23 ]

While working on it I found out that it's easy to get items without history to be stuck in non-supported state on server by restarting proxy when the item becomes not supported. This 'subissue' will be fixed also for 6.0

Comment by Andris Zeila [ 2024 Jan 23 ]

Fixed in development branches:

Comment by Andris Zeila [ 2024 Feb 16 ]

Released ZBX-23124 in:

  • pre-6.0.27rc1 b61afa194f7, bf4f17d9167
  • pre-6.4.12rc1 1e66493cc76
  • pre-7.0.0beta2 36cb7b7ba77
Generated at Fri Jun 19 04:22:31 EEST 2026 using Jira 10.3.18#10030018-sha1:5642e4ad348b6c2a83ebdba689d04763a2393cab.