[ZBXNEXT-3269] Recommend using redis as zabbix’s valuecache implementation Created: 2016 May 05  Updated: 2022 Jul 10  Resolved: 2022 Jul 10

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Server (S)
Affects Version/s: None
Fix Version/s: None

Type: New Feature Request Priority: Major
Reporter: Dominic Xu Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: cache, redis, valuecache
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate

 Description   

zabbix use a custom hashset function to implement valuecache , this method on a small memory of the original machine is better, now uses redis or memcached as valuecache implementation than the more common some of it?

Only need to re-design and implement valuecache.c, so we can easily support redis or memcached.



 Comments   
Comment by Aleksandrs Saveljevs [ 2016 May 05 ]

Could you please elaborate a bit on the possible benefits of using Redis as opposed to Zabbix's own implementation?

Comment by Dominic Xu [ 2016 May 05 ]

We can very quickly get the latest values for item.

Now if we want to get the latest value, we need to call the API interface or through zabbix‘s database to cross-table query.

Comment by Dominic Xu [ 2016 May 05 ]

And, This place is recommended to design a hook.

Comment by Aleksandrs Saveljevs [ 2016 May 05 ]

So the feature request is not so much about Redis, but more about a convenient and efficient way of getting latest values from Zabbix? If so, ZBXNEXT-1836 may be a better solution.

Note that Zabbix does not store all historical data in the value cache. It only stores the values it needs for trigger calculation (and maybe a few other things like calculated items), so if an item does not have a trigger, the value cache will not contain data for this item. In general, the contents of the value cache should not be relied upon.

Comment by Alexei Vladishev [ 2022 Jul 10 ]

I do not think it will ever be implemented.

Generated at Mon Apr 28 09:51:07 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.