[ZBXNEXT-3487] Virtual memory monitoring on Windows Created: 2016 Oct 06  Updated: 2018 Mar 30  Resolved: 2016 Dec 13

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Agent (G), Frontend (F), Templates (T)
Affects Version/s: None
Fix Version/s: 3.0.6, 3.0.7, 3.2.2, 3.2.3, 3.4.0alpha1

Type: New Feature Request Priority: Minor
Reporter: Andris Zeila Assignee: Unassigned
Resolution: Fixed Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows


Attachments: File ZBXNEXT-3487-item_key_helper-3.0.patch     File ZBXNEXT-3487-item_key_helper-3.2.patch    
Issue Links:
Causes
causes ZBX-13676 Description of vm.vmemory.size of wha... Closed

 Description   

The system.swap.size key returns swap usage statistics. Windows doesn't provide swap file information, so the data is calculated from virtual memory (physical + page file) and physical memory statistics. Apparenly the calculation is not so simple and the resulting swap file statistics are approximate.

Additionally it appears monitoring the whole virtual memory statistics is normal on Windows and users expect it also from Zabbix agent. This means it's better to add a new Windows key to allow monitoring of virtual memory statistics directly returned by Windows API.



 Comments   
Comment by Andris Zeila [ 2016 Oct 06 ]

(1) [D] Add an explanation how system.swap.size is calculated on Windows systems.

vso Can possibly use this:
Due to the way Windows API functions report memory metrics, it is impossible to accurately retrieve swap (virtual memory) sizes as Windows reports the total commit memory which is physical memory plus swap file sizes. The only resolution that could be applied was calculatively deducting the swap sizes knowing the page and physical memory sizes.

sasha documentation must be updated:

vso RESOLVED

sasha "Items supported by platform" and "Zabbix agent items" sections are not updated.

REOPENED
vso This is because it's windows only key so it does not need to be present in those 2 places ? I don't see other windows only keys present there..

sasha Thanks! CLOSED

glebs.ivanovskis No "This item is supported since Zabbix x.y.z" lead to ZBX-11733.

vso RESOLVED, updated pages:
https://www.zabbix.com/documentation/3.0/manual/config/items/itemtypes/zabbix_agent/win_keys
https://www.zabbix.com/documentation/3.2/manual/config/items/itemtypes/zabbix_agent/win_keys

glebs.ivanovskis And https://www.zabbix.com/documentation/3.4/manual/config/items/itemtypes/zabbix_agent/win_keys ?

vso RESOLVED, updated pages:
https://www.zabbix.com/documentation/3.0/manual/config/items/itemtypes/zabbix_agent/win_keys
https://www.zabbix.com/documentation/3.2/manual/config/items/itemtypes/zabbix_agent/win_keys
https://www.zabbix.com/documentation/3.4/manual/config/items/itemtypes/zabbix_agent/win_keys

glebs.ivanovskis 3.0 docs should mention minor 3.0 version, 3.2 should mention 3.2 minor version and 3.4 (and all future versions) should mention both 3.0 and 3.2 minor versions where feature first appeared. That's the convention, I guess. (By the way, should we add this to guidelines?)

vso RESOLVED, personally I would prefer it same as Changelog. 3.0 - one, 3.2 - both, trunk - none or in 3.2 also one would be fine.
https://www.zabbix.com/documentation/3.2/manual/config/items/itemtypes/zabbix_agent/win_keys

glebs.ivanovskis I would let martins-v and VSI judge.

Comment by Vladislavs Sokurenko [ 2016 Oct 14 ]

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-3487

Comment by Andris Zeila [ 2016 Oct 17 ]

(2) The *Virtual fields of MEMORYSTATUS and MEMORYSTATUSEX structures returns statistics for virtual address space of the calling process. To get system virtual memory statistics we must use *PageFile fields, which is physical memory plus the size of the page file.

vso RESOLVED in r63184

wiper CLOSED

Comment by Andris Zeila [ 2016 Oct 17 ]

Successfully tested

Comment by Vladislavs Sokurenko [ 2016 Oct 17 ]

Fixed conflicts in development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-3487_3.2

wiper Looks good.

Comment by Vladislavs Sokurenko [ 2016 Oct 17 ]

Fixed in:

  • 3.0.6 r63201
  • 3.2.2 r63202
  • 3.3.0 (trunk) r63203
Comment by richlv [ 2016 Nov 15 ]

(3) the new key "vm.vmemory.size" only appears as a passive item in the frontend item key helper. it should be also added to the list of the active item keys, and the description should match the one in the manual.
it is also not sorted alphabetically as other keys are.

  • the attached patch for 3.0 fixes these issues and also updates the description of the "system.uptime" key to match the manual.
  • the attached patch for 3.2 fixes these issues, updates the description of the "system.uptime" key to match the manual, changes the log.count item key sorting to be consistent with other keys and updates the logrt.count description to match the manual; this patch also applies cleanly to trunk

vso RESOLVED in r63782 and r63785

wiper CLOSED

Comment by Vladislavs Sokurenko [ 2016 Nov 15 ]

Fixed in development branches

  • svn://svn.zabbix.com/branches/dev/ZBXNEXT-3487
  • svn://svn.zabbix.com/branches/dev/ZBXNEXT-3487-3.2
Comment by Andris Zeila [ 2016 Dec 12 ]

Successfully tested

Comment by Vladislavs Sokurenko [ 2016 Dec 13 ]

Fixed in:

  • pre-3.0.7rc1 r64376
  • pre-3.2.3rc1 r64377
  • pre-3.3.0 (trunk) r64378
Generated at Fri Mar 29 07:14:07 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.