If you go down the thin provisioning route, you should must monitor the disk usage. Thin provisioning can lead to oversubscription of physical disk space, that is allocating more disk space that you do really have physically and end up with a corrupted VMDK disk for example!
The following alarm triggers are helpful:
- Datastore Disk Usage %
- Datastore Disk Overallocation %
N.B. Swap files, redo logs and linked clones for snapshots DO NOT make use of thin provisioning.
A good reading regarding thin provisioning and performances: Performance Study of VMware vStorage Thin Provisioning