[ZBXNEXT-7793] Zabbix SNMP Gateway - current Problem triggers table not updated Created: 2022 Jun 10  Updated: 2024 Apr 10  Resolved: 2023 Feb 08

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: None
Affects Version/s: 5.0.24
Fix Version/s: 6.4 (plan)

Type: Change Request Priority: Trivial
Reporter: Oleksii Zagorskyi Assignee: Eriks Sneiders
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Problem-Triggers.png    
Issue Links:
Duplicate
Team: Team INT
Sprint: Sprint 94 (Nov 2022), Sprint 95 (Dec 2022), Sprint 96 (Jan 2023), Sprint 97 (Feb 2023)
Story Points: 1

 Description   

During development of ZBXNEXT-7071, looks like it was decided  that cache will be rebuilt every hour and trigger in problem state will only be available after an hour.

This caused that  

But this is not acceptable for the solution, as "Problem Triggers" view is inconsistent with other views where fresh Problems are counted and visible immediately - "Hostgroups" and "Triggers"

Yes, rebuild mapping table manually (by USR2 signal) helps and shows the fresh Problem triggers, but it's not acceptable by end users to be forced to reload it to see the problems.

https://git.zabbix.com/projects/ZT/repos/snmp-gateway/browse/README.md



 Comments   
Comment by Oleksii Zagorskyi [ 2022 Jun 10 ]

Probably makes sense to report it in current ticket, but as a bug (let me know if separate ZBX is actually required):

 "Problem Triggers" view may show Tempalate names instead of hosts names.

I'm trying to collect more information, as it's strange why we see zero (0) for column "zabbixNbActiveTriggerLastchange".
Maybe issue not with template vs host name, but actually including wrong things to the view.

Comment by Guenther SOMMER [ 2022 Oct 03 ]

From the support ticket our suggestion:

 
About the refresh time - we had some internal discussion about that. A caching is needed for this table, as e.g. we make a snmp-walk over the table, then it should not request each item again and again. But we know that other values are cached for several seconds as well, see:

{{ "CacheLifeTime": 5, // Number of seconds how long query will be cached”)}}

This cache lifetime should be used for that as well and not the cache for the mapping table.

Generated at Sat Apr 12 17:55:33 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.