Quantcast
Channel: VMware Communities : All Content - vCenter™ Server
Viewing all articles
Browse latest Browse all 5185

VM Max Disk Latency Alarm - BAD TRIGGERS

$
0
0

vCenter Build: 4.1.0, 345043

ESX Build:  4.1.0, 348481

 

I am trying to create an alert for VM Max Disk Latency (ms), I went through configuring the alarm and all seemed good, but as soon as I hit "OK" my inbox was flooded with alert emails like the following:

 

##############################

Target: <computer_name>

Previous Status: Green

New Status: Yellow

 

Alarm Definition:

([Yellow Metric Is above 30KBps; Red Metric Is above 50KBps])

 

Current values for metric/state:

Metric Usage = 47KBps

 

Description:

Alarm Custom Alarm- VM DISK LATENCY' on <computer_name> changed from Green to Yellow

##############################

 

What is going on here? It's like values for the disk latency thresholds in milliseconds are actually configured as KBps I/O for the VMDK. All I could get with my Goole-Foo was some KB about disk latency alarms not triggering in vCenter/ESX versions prior to 4.1 U1, which does not pertain to this environment.

 

Has anyone seen this before/know how to get a VM Max Disk Latency (ms) to actually work?


Viewing all articles
Browse latest Browse all 5185

Trending Articles