Details
-
Type:
Incident report
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.2.12rc1, 2.4.8rc1, 3.0.2rc1, 3.2.0alpha1
-
Component/s: Proxy (P), Server (S)
-
Labels:
-
Environment:VMware vCenter 4.1
Zabbix 2.4.7
Description
The incorrect datastores IDs causing no performance data and "Performance counter instance was not found." errors for them.
Activity
Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-10320
Show
Andris Zeila
added a comment - Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-10320
(1) Memory allocator used_size field is used for vmware cache free size statistics. However used_size does not account for allocation overhead resulting in slightly misleading statistics. The more correct approach would be to use free_size field.
Andris Zeila RESOLVED in r58555
<dimir> CLOSED
Show
Andris Zeila
added a comment - - edited (1) Memory allocator used_size field is used for vmware cache free size statistics. However used_size does not account for allocation overhead resulting in slightly misleading statistics. The more correct approach would be to use free_size field.
Andris Zeila RESOLVED in r58555
< dimir > CLOSED
Released in:
- pre-2.2.12rc1 58754
- pre-2.4.8rc1 58755
- pre-3.0.2rc1 58756
- pre-3.1.0 58757
Show
Andris Zeila
added a comment - Released in:
pre-2.2.12rc1 58754
pre-2.4.8rc1 58755
pre-3.0.2rc1 58756
pre-3.1.0 58757
Some reading about identifying NFS datastores: http://www.doublecloud.org/2010/10/a-workaround-to-identify-nfs-based-datastore-in-vsphere/