Scope is the topologyObject type/query result which is used as the entry point into the topology structure for the rule you want to create.
In this case, VMWDatastore.
The vBundle derived metric is likely using that scope in it's calculation as well. ( since vBundle is deprecated, I no longer have it readily available, so can't be sure.)
In this case, the spaceAvailable metric is already existing on the VMWDatastore objects, so you don't need to create a new derived metric.
Simply copy the rule you currently use, give it a new name, and change the condition(s) to use the spaceAvailable metric instead of the vBundle derived metric.
On a 249.8GB datastore, it alerted when free space dropped below 100 GB.
On a 2TB datastore, it alerted sometime around 158 GB free (can't find the exact value, is it possible it dipped below that and it wasn't recorded in the max/min?)
Is this a case where #spaceAvailable# could be off by a factor of 10?
The value in "vBundle.datastore.storage.free.fatal" is 20. The intent is that it alert when under 20 GB free. Does the code above not do this?
john_s_main
132 Posts
392
0
Posted April 21st, 2013 08:00
set scope to VMWDatastore
#spaceAvailable# metric is in megabytes