Here's an example: at top level of vcenter, I set the "Datastore Overprovisioning" alarm to Trigger a warning over 150% and an Alert over 200%. Action is to send an email to our vSphere admins.
Any generated alarms come across as follows:
+ Previous Status: Gray+
+ New Status: Red+
+ Alarm Definition:+
+ Current values for metric/state:+
+ Metric Space potentially used = 25,063KB+
+ Alarm 'Datastore Overprovisioning' on USPV_2_3B80_02 changed from Gray to Red+
So the alarm definition should be "Yellow Metric is above 150%; Red Metric is above 200%".
The Current values should read "Metric Space potentially used = 250.63%"
So why does the alarm come across as percentage * 100 in KB? I can interpret this alarm for what it is, but it is pretty darned confusing to everyone else on my team.
Anyone else observed this in vCenter 4.x?
Anyone have an idea on how to fix this?
Thanks much! Figured I'd check with community before filing a support case.
Yes, I have the same thing with Datastore Usage (Datacenter level).
VC 4.1.0 Build 258902
This should be 90% and 95% for the trigger. Metric Space is 98.19%
I haven't done any other alarms yet so not sure how deep this runs.
Previous Status: Gray
New Status: Red
Current values for metric/state:
Metric Space actually used = 9,819KB
Alarm 'SSI> Datastore Usage' on Storage-33 changed from Gray to Red
I ran into problems with memory and CPU usage on guest machines. False alarms triggered. I disabled them this morning as the frontline support team was threatening to storm my office because of the false emails. We'll just monitor the VMs other ways, but wondering if anyone else has had this problem in addition to the datastore problem?
We eventually did get some feedback , that apparently the issue would be resolved in update 1 which we have not implemented just yet so I can’t verify if the issue has been resolved yet