[ZBX-8607] vm.memory.size[pavailable] on Windows doesn't work as expected Created: 2014 Aug 12 Updated: 2019 Dec 10 |
|
Status: | Open |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Agent (G) |
Affects Version/s: | 2.2.5 |
Fix Version/s: | None |
Type: | Incident report | Priority: | Trivial |
Reporter: | Dmitry Samsonov | Assignee: | Unassigned |
Resolution: | Unresolved | Votes: | 1 |
Labels: | memory, windows | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Windows Server 2003 x64 |
Issue Links: |
|
Description |
From the documentation: Actual values: C:\zabbix\tmp>zabbix_agentd.exe -t vm.memory.size[pavailable] C:\zabbix\tmp>zabbix_agentd.exe -t vm.memory.size[cached] C:\zabbix\tmp>zabbix_agentd.exe -t vm.memory.size[inactive] C:\zabbix\tmp>zabbix_agentd.exe -t vm.memory.size[free] C:\zabbix\tmp>zabbix_agentd.exe -t vm.memory.size[total] C:\zabbix\tmp>zabbix_agentd.exe -V (0+3863650304+285749248)/4292448256*100=96.67, but pavailable report "6.755881". |
Comments |
Comment by Oleksii Zagorskyi [ 2014 Aug 13 ] |
As for doc statement "pavailable - inactive + cached + free memory in relation to 'total'." - it's first of all related to *nix. |
Comment by Dmitry Samsonov [ 2014 Aug 13 ] |
Oleksiy, yes, I also suppose so, but can't find it in documentation. Thanks in advance. |
Comment by Dmitry Samsonov [ 2014 Aug 17 ] |
According to various windows documentations cached is not part of available. However, it would be nice to have some words about vm.memory.size in windows here https://www.zabbix.com/documentation/2.2/manual/appendix/items/vm.memory.size_params . Thank you. |
Comment by Oleg Ivanivskyi [ 2016 Jun 28 ] |
This issue is still active for Linux. Zabbix agents 2.2 and 2.4 cannot get inactive memory from 3.10 Linux kernel. |