do storage item keys (see https://www.zabbix.com/documentation/2.2/manual/config/items/itemtypes/simple_checks/vmware_keys) provide some of the desired functionality ?

on the second thought, that's per vm and total was probably requested

Has there been any changes on this? It surprises me that something as basic as "how much space remains on my datastore" does not appear to be implemented.

I did few quick tests and it does not look good. It might be the test vSphere setup, but it reported no real-time statistics for datastore objects. This means we can't just simply drop in datastore performance entity support.

One way to get latest data would be specifying start time, but as maxSample appears to be ignored in this case, we would still need to know the data gathering interval.

I tired of trying to use perfcounters and other things.
So i decided to use snmp monitiring. I have downloaded here template "ESXi snmp" and it's work great. Only one problem, I cant get datastore "label"(name), just #snmpindex that is number, or #snmplabel that is number too...

Maybe this help https://www.zabbix.com/forum/showthread.php?t=52084

is it any solution in zabbix 3.0?

While using performance counters would not be simple, we could get the capacity, free space and uncommited space from datastore configuration summary.

So the plan is to add a key to monitor datastore capacity statistics - vmware.hv.datastore.size[<url>,<uuid>,<datastore>,<mode>] where:

• url - VMware service URL
• uuid - VMware hypervisor host name
• datastore - datastore name
• mode:
  • total - maximum capacity of this datastore, in bytes (default)
  • free - available space of this datastore, in bytes
  • pfree - available space of this datastore, in percentage
  • uncommitted - total additional storage space, in bytes, potentially used by all virtual machines on this datastore

However storage capacity counters will not be used. This data will be taken from datastore summary property.

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

(1) [SP] A small improvement would be to check for zero capacity in

[...]
SET_DBL_RESULT(result, (double)datastore->free_space / datastore->capacity * 100);
[...]

wiper RESOLVED in r63554

<dimir> CLOSED

Just a note that it looks like while developing this functionality wiper has fixed potential Zabbix server/proxy crash that could happen during datastore summary request if there was a problem with connection to the web server (libcurl error).

Before this fix function vmware_service_create_datastore() would still allocate and return datastore object (with NULL name and uuid) in case of libcurl error.

Released in:

• pre-3.0.6rc1 r63584
• pre-3.2.2rc1 r63586
• pre-3.3.0 r63587

Documented in:

• 3.0
  • https://www.zabbix.com/documentation/3.0/manual/introduction/whatsnew306
  • https://www.zabbix.com/documentation/3.0/manual/config/items/itemtypes/simple_checks/vmware_keys
• 3.2
  • https://www.zabbix.com/documentation/3.2/manual/introduction/whatsnew322
  • https://www.zabbix.com/documentation/3.2/manual/config/items/itemtypes/simple_checks/vmware_keys
• 3.3
  • https://www.zabbix.com/documentation/3.4/manual/config/items/itemtypes/simple_checks/vmware_keys

Official templates updated at https://www.zabbix.org/wiki/Zabbix_Templates/Official_Templates

sasha "Template changes" section must be moved from What's new to Template changes page

REOPENED

• 3.0
  • https://www.zabbix.com/documentation/3.0/manual/installation/template_changes
• 3.2
  • https://www.zabbix.com/documentation/3.2/manual/installation/template_changes

wiper RESOLVED

sasha Thanks a lot! CLOSED