[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: | ZBXNEXT-3487-item_key_helper-3.0.patch ZBXNEXT-3487-item_key_helper-3.2.patch | ||||||||
Issue Links: |
|
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: sasha documentation must be updated:
vso RESOLVED sasha "Items supported by platform" and "Zabbix agent items" sections are not updated. REOPENED sasha Thanks! CLOSED glebs.ivanovskis No "This item is supported since Zabbix x.y.z" lead to ZBX-11733. vso RESOLVED, updated pages: glebs.ivanovskis And https://www.zabbix.com/documentation/3.4/manual/config/items/itemtypes/zabbix_agent/win_keys ? vso RESOLVED, updated pages: 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. 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:
|
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.
vso RESOLVED in r63782 and r63785 wiper CLOSED |
Comment by Vladislavs Sokurenko [ 2016 Nov 15 ] |
Fixed in development branches
|
Comment by Andris Zeila [ 2016 Dec 12 ] |
Successfully tested |
Comment by Vladislavs Sokurenko [ 2016 Dec 13 ] |
Fixed in:
|