Book Image

Mastering vRealize Operations Manager - Second Edition

By : Spas Kaloferov, Chris Slater, Scott Norris
Book Image

Mastering vRealize Operations Manager - Second Edition

By: Spas Kaloferov, Chris Slater, Scott Norris

Overview of this book

In the modern IT world, the criticality of managing the health, efficiency, and compliance of virtualized environments is more important than ever. With vRealize Operations Manager 6.6, you can make a difference to your business by being reactive rather than proactive. Mastering vRealize Operations Manager helps you streamline your processes and customize the environment to suit your needs. You will gain visibility across all devices in the network and retain full control. With easy-to-follow, step-by-step instructions and support images, you will quickly master the ability to manipulate your data and display it in a way that best suits you and your business or technical requirements. This book not only covers designing, installing, and upgrading vRealize Operations 6.6, but also gives you a deep understanding of its building blocks: badges, alerts, super metrics, views, dashboards, management packs, and plugins. With the new vRealize Operations 6.6 troubleshooting capabilities, capacity planning, intelligent workload placement, and additional monitoring capabilities, this book is aimed at ensuring you get the knowledge to manage your virtualized environment as effectively as possible.
Table of Contents (17 chapters)

Capacity management for vRealize Operations policies

The first and most important aspect to cover with capacity management in vRealize Operations is all about policies. Policies are the King. The calculations and recommendations for all areas of capacity management are directly related to what policy options are configured and currently active on the selected resource.

It is highly improbable that one policy is suitable for all workload types such as a server, VDI, production, dev/test, and so on. It is important to understand when defining policies that the configuration is usually a trade-off of performance vs. utilization. An example of this is shown in the following diagram: