Differences between CloudHealth native and CloudHealth-vRealize Operations (vRops) integration configurations for the ‘Data Center’ module

Products

• CloudHealth

Issue/Introduction

Please review the table below to understand the differences between the two configuration options.

Resolution

Function / Use Case	Native CloudHealth Data Center configuration	vRealize Operations (vRops) Integration
vCenter account addition	Yes	No need to add accounts explicitly, CloudHealth will sync these accounts from vRealize Operations.|
Data Collection	via CloudHealth Aggregator Deployment to collect data from one or more vCenter accounts	CloudHealth aggregator, as CloudHealth will use vRealize Operations Management pack directly to retrieve data from vRealize Operations.
Benchmark Pricing	User will add/edit in CloudHealth	User will add/edit in vRealize Operations, no benchmark edit in CloudHealth
Showback via Cost History Report	Yes	Yes
Perspective Support	Yes	Yes
Multicloud Cost History	Yes	Yes
Cost Driver History Report	Yes	Yes, this report reflects any change made to benchmark pricing in VROPS (not available for any version below vRealize Operations 8.4)
Machine Usage Report	Yes	Yes
Performance Reports	Machine, File Systems, Memory, Network	Machine, Memory
Metrics Reports	Machine, Block Device, File System, Memory, Network	Machine, Memory
Assets	Data Centers, Clusters, Hosts, Datastores, Machines, File Systems, Network Interfaces, CPUS, Block Devices, Daily Usage	Data Centers, Clusters, Hosts, Datastores, Machines, Daily Usage
Migration Assessment	Yes	Yes
Rightsizing	Yes	No
Rightsizing Policies	Yes	No
Standard Policies	Yes	Yes
FlexOrgs Support	Yes	Yes