vRealize Operations Manager tracks and analyzes the operation of multiple data sources within the Software-Defined Data Center (SDDC) by using specialized analytics algorithms. These algorithms help vRealize Operations Manager to learn and predicts the behavior of every object it monitors. Users access this information by using views, reports, and dashboards.

Installation Models

vRealize Operations Manager is available in two different deployment models: a preconfigured virtual appliance, or a Windows or Linux installable package. Select the installation method for your deployment according to the following considerations:

  • When you use the vRealize Operations Manager virtual appliance, you deploy the OVF file of the virtual appliance once for each cluster node. You access the product to set up cluster nodes according to their role, and log in to configure the installation.

    Use virtual appliance deployment to easily create vRealize Operations Manager nodes with pre-defined identical size.

  • When you use the Windows or Linux installable package, you run the vRealize Operations Manager installation on each cluster node. You access the product to set up cluster nodes according to their role, and log in to configure the installation.

    Use installable package deployment to create vRealize Operations Manager node with custom identical size.

Architecture

vRealize Operations Manager contains functional elements that collaborate for data analysis and storage, and support creating clusters of nodes with different roles. 

Figure 1. vRealize Operations Manager Architecture


The high-level architecture includes a master node, master replica node, data node, and remote collector

Types of Nodes and Clusters

For high availability and scalability, you can deploy several vRealize Operations Manager instances in a cluster where they can have either of the following roles.

Master Node

Required initial node in the cluster. In large-scale environments, the master node manages all other nodes. In small-scale environments, the master node is the single standalone vRealize Operations Manager node.

Master Replica Node

(Optional) Enables high availability of the master node. 

Data Node

Enables scale-out of vRealize Operations Manager in larger environments. Data nodes have adapters installed to perform collection and analysis. Data nodes also host vRealize Operations Manager management packs.

Larger deployments usually include adapters only on data nodes, not on the master node or replica node

Remote Collector Node

 In distributed deployments, enables navigation through firewalls, interfaces with a remote data source, reduces bandwidth across regions, or reduces the load on the vRealize Operations Manager analytics cluster. Remote collector nodes only gather objects for the inventory and forward collected data to the data nodes. Remote collector nodes do not store data or perform analysis. In addition, you can install them on a different operating system than the rest of the cluster nodes.

The master and master replica nodes are data nodes with extended capabilities.

vRealize Operations Manager can form two types of clusters according to the nodes that participate in a cluster.

Analytics clusters

Tracks, analyzes, and predicts the operation of monitored systems. Consists of a master node, data nodes, and optionally of a master replica node. 

Remote collectors cluster

Only collects diagnostics data without storage or analysis. Consists only of remote collector nodes.

Application Functional Components 

The functional components of a vRealize Operations Manager instance interact to provide analysis of diagnostics data from the data center and visualize the result in the Web user interface. 

Figure 2. vRealize Operations Manager Logical Node Architecture


vROps components in a master node include the product/admin UI and the Rest API/collector. A Controlelr, Analytics, and Persistence component analize capacity and performance.

The components of vRealize Operations Manager node perform these tasks:

Admin / Product UI server

The UI server is a Web application that serves as both user and administration interface.

REST API / Collector

The Collector collects data from all components in the data center.

Controller

The Controller handles the data flow the UI server, Collector, and the analytics engine.

Analytics

The Analytics engine creates all associations and correlations between various data sets, handles all super metric calculations, performs all capacity planning functions, and is responsible for triggering alerts.

Persistence

The persistence layer handles the read and write operations on the underlying databases across all nodes.

FSDB

The File System Database (FSDB) stores collected metrics in raw format. FSDB is available in all the nodes.

xDB (HIS)

The xDB stores data from the Historical Inventory Service (HIS). This component is available only on the master and master replica nodes.

Global xDB

The Global xDB stores user preferences, alerts, and alarms, and customization that is related to the vRealize Operations Manager. This component is available only on the master and master replica nodes.

Management Packs

Management packs contain extensions and third-party integration software. They add dashboards, alert definitions, policies, reports, and other content to the inventory of vRealize Operations Manager. You can learn more details about and download management packs from VMware Solutions Exchange.

Multi-Region vRealize Operations Manager Deployment

The scope of the SDDC design covers multiple regions. Using vRealize Operations Manager across multiple regions requires deploying an analytics cluster that is protected by Site Recovery Manager, and deploying remote collectors in each region.