I'm going to have to agree with Jas on this one.

CPU, Memory, Heartbeats, Hosts down, etc can all be alerted through either vCenter, or other methods.

Things like data timeouts, slowness, etc, are things we need to look at regularly. The SAN may not indicate to us that it sees anything wrong, but VI3 might have issues that the SAN doesn't care about.

Jase

Jase McCarty
http://www.jasemccarty.com
Co-Author of VMware ESX Essentials in the Virtual Data Center
(ISBN:1420070274) from Auerbach
_{Please consider awarding points if this post was helpful or correct}

My previous post was meant as sort of a joke, but in truth when I come against a "How did that happen" kind of issue as often as not human error is involved. A system/cluster/network that has been working fine and suddenly goes south is usually caused by a hardware failure or human action and human action edges out hardware failure by a fair margin.

Even performance degradation issues can be tracked to admin actions.

So from a troubleshooting standpoint who last logged onto the system(s) in an admin capacity is something to look for in the logs.

From a pure monitoring standpoint the security implications of who is accessing the systems is also worthy of note.

Hello,

Root sessions
SCSI Errors
SCSI Reservations
CPU issues
vmhba issues


Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
Blue Gears and SearchVMware Pro Blogs
Top Virtualization Security Links