[ZBX-10320] Zabbix uses incorrect datastore IDs which causes no performance data for them. Created: 2016 Jan 28 Updated: 2017 May 30 Resolved: 2016 Feb 29 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Proxy (P), Server (S) |
| Affects Version/s: | None |
| Fix Version/s: | 2.2.12rc1, 2.4.8rc1, 3.0.2rc1, 3.2.0alpha1 |
| Type: | Incident report | Priority: | Major |
| Reporter: | Oleg Ivanivskyi | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | vmware | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
VMware vCenter 4.1 |
||
| Issue Links: |
|
||||
| Description |
|
The incorrect datastores IDs causing no performance data and "Performance counter instance was not found." errors for them. |
| Comments |
| Comment by Andris Zeila [ 2016 Jan 29 ] |
|
Some reading about identifying NFS datastores: http://www.doublecloud.org/2010/10/a-workaround-to-identify-nfs-based-datastore-in-vsphere/ |
| Comment by Andris Zeila [ 2016 Feb 12 ] |
|
Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-10320 |
| Comment by Andris Zeila [ 2016 Feb 18 ] |
|
(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. wiper RESOLVED in r58555 <dimir> CLOSED |
| Comment by dimir [ 2016 Feb 24 ] |
|
Successfully tested. |
| Comment by Andris Zeila [ 2016 Feb 29 ] |
|
Released in:
|