[ZBXNEXT-985] improve internal cache monitoring item descriptions Created: 2011 Oct 01  Updated: 2015 Jul 03  Resolved: 2015 Jul 03

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Documentation (D)
Affects Version/s: 1.8.8
Fix Version/s: None

Type: New Feature Request Priority: Minor
Reporter: Tobias van Hoogen Assignee: Unassigned
Resolution: Fixed Votes: 1
Labels: cachesize, server
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

All


 Description   

Hi,

The added support for monitoring the internal zabbix processes was great, we finally gained proper insight - thus making tweaking the value's very easy.

http://blog.zabbix.com/monitoring-how-busy-zabbix-processes-are/457/#more-457

In the latest versions of zabbix the following options were added:

      1. Option: CacheSize
      2. Option: HistoryCacheSize
      3. Option: TrendCacheSize
      4. Option: HistoryTextCacheSize

Which is great! However, I really miss insight here: how do I decide on the proper value's for my server? I'd like to propose adding features in the same style as was done for the internal processes.

Thanks!

 Comments   
Comment by richlv [ 2011 Oct 01 ]

do you mean internal items (http://www.zabbix.com/documentation/1.8/manual/config/items#internal_checks) like zabbix[wcache,<cache>,<mode>] and zabbix[rcache,<cache>,<mode>] ?

although admittedly the descriptions of them might be a bit better

Comment by Tobias van Hoogen [ 2011 Oct 01 ]

Wow, that was a very fast followup on a feature request Excellent... we had this discussion with multiple people yesterday, seems we totally overlooked this. So a better description might be a good idea.

Thanks!

Comment by richlv [ 2011 Oct 01 ]

let's reclassify this as a documentation request then

Comment by Martins Valkovskis [ 2015 Jul 01 ]

Descriptions of the relevant items (rcache, wcache) have been improved in subsequent versions (as of https://www.zabbix.com/documentation/2.0/manual/config/items/itemtypes/internal) since the creation of this issue, so perhaps it could be closed now?

Generated at Wed Apr 24 13:47:47 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.