Why collect additional data?
Why would an administrator want to import data from other monitoring systems or data sources into vROps? Especially, when the data for those systems is already being managed by an existing monitoring solution.
This is a fair question given the absence of some nice to have features like all the data being in one place and on a single pane of glass, but the real power of vROps is the way it handles relationships and the benefits that it provides to the administrators out there.
Say, we have installed vROps and it's doing what it does well, importing vSphere data and providing various types of useful information and reports. When an incident ticket comes in saying that there is a problem with the performance of a VM or a number of VMs, we can look at these VMs in vROps and see which cluster it belongs to, what host it is currently sitting on, and on which datastore the VMs' disks are located. We can see the health and metrics of all the areas of the hypervisor and...
