Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
VMware Performance and Capacity Management, Second Edition

You're reading from   VMware Performance and Capacity Management, Second Edition Master SDDC Operations with proven best practices

Arrow left icon
Product type Paperback
Published in Mar 2016
Publisher
ISBN-13 9781785880315
Length 546 pages
Edition 2nd Edition
Tools
Arrow right icon
Authors (2):
Arrow left icon
Sunny Dua Sunny Dua
Author Profile Icon Sunny Dua
Sunny Dua
Iwan 'e1' Rahabok Iwan 'e1' Rahabok
Author Profile Icon Iwan 'e1' Rahabok
Iwan 'e1' Rahabok
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Preface Part 1 FREE CHAPTER
1. VM – It Is Not What You Think! 2. Software-Defined Data Centers 3. SDDC Management 4. Performance Monitoring 5. Capacity Monitoring Part 2
6. Performance-Monitoring Dashboards 7. Capacity-Monitoring Dashboards 8. Specific-Purpose Dashboards 9. Infrastructure Monitoring Using Blue Medora 10. Application Monitoring Using Blue Medora Part 3
11. SDDC Key Counters 12. CPU Counters 13. Memory Counters 14. Storage Counters 15. Network Counters Index

Storage counters at the cluster level

vCenter does not provide information for storage at the cluster level but vRealize Operations does, including counters such as IOPS, Throughput, and Latency. The main reason why you should not look at storage at the cluster level when working with classic arrays is that the cluster is a compute cluster; it is not a storage cluster, so the boundary a cluster provides for compute may not apply to storage.

Can you think of another reason?

The data at this level, like for the ESXi host level, includes all the local datastores. This can impact the overall result, especially those that give an average of all the datastores. If you have a cluster with 10 nodes that share five datastores, you will have 15 datastores in the clusters. The 10 local datastores will skew the total result, masking important data such as average latency.

For a view beyond disk and datastore, the datastore cluster is what you should look into.

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image