Book Image

VMware vRealize Operations Essentials

By : Matthew Steiner
Book Image

VMware vRealize Operations Essentials

By: Matthew Steiner

Overview of this book

This book will enable you to deliver on the operational disciplines of Performance, Health, Capacity, Configuration, and Compliance by making the best use of solutions provided by vRealize Operations. Starting with architecture, design, and sizing, we will ensure your implementation of vRealize Operations is a success. We will dive into the utilization of a solution to manage your vSphere infrastructure. Then, we will employ out-of-the-box Dashboards and the very powerful Views and Reporting functionality of vRealize Operations to create your custom dashboards and address your reporting requirements. Next, we go through the Alerting framework and how Symptoms, Recommendations, and Actions are used to achieve efficient operations. Later you will master the topic of Capacity Planning, where we look at how important it is to craft appropriate policies to match your requirements, and we’ll consider attitude toward capacity risk, which will aid you to build future project requirements into your capacity plans. Finally, we will look at extending the solution to manage Storage, Applications, and other IT infrastructures using Management Packs from Solution Exchange, as well as how the solution can be enhanced with the integration of Log Insight.
Table of Contents (18 chapters)
VMware vRealize Operations Essentials
Credits
Foreword
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Symptom Definitions


As mentioned earlier, it is one or more Symptom Definitions that defines when an alert is triggered. There are four different Symptom Definition types:

  • Metric/Property

  • Message Event

  • Fault

  • Metric Event

If you are creating your own custom alerts, you will generally be working with Metric/Property Symptom Definitions. The other three are generally used by vRealize Operations itself, or by Solutions.

Symptom Criticality

The description of every symptom includes its Criticality. This is a measure of how important the symptom is. There are four levels of Criticality:

  • Info: Typically used to describe the object state, for example, Virtual machine is powered off, which is a symptom that might be used to suppress alerts that aren't relevant when a machine is powered off

  • Warning: This is the first level of criticality; this will typically set a badge color yellow

  • Immediate: This is something that requires immediate attention and the badge color will turn orange

  • Critical: This is something...