We use it for for monitoring VMs.
With the vRealize Operations Manager, it gives an idea of what the VMs are using: storage, compute, etc.
We use it for for monitoring VMs.
With the vRealize Operations Manager, it gives an idea of what the VMs are using: storage, compute, etc.
It helps us save money by having less computers, less to manage, and less to worry about if we know exactly what the application is using.
We've been more efficient, so we don't have to spend as much time doing operations and maintenance type work.
If it was cheaper, we wouldn't be sad! We'd prefer if it cost less money to maintain or purchase.
I haven't had any issues yet. It's pretty stable.
Very scalable. Very easy to setup. It's what do we want to do with it because it's so capable, we're just scratching the surface with it right now.
Very good and knowledgeable. When we call and have an issue, they resolve it pretty quickly. We always reach the right person.
We weren't using anything. We had the native Windows monitoring tools, which were in each individual Virtual Machine. We didn't have anything to monitor virtual infrastructure. It made sense since we ran VMware that we would look to use a VMware product.
I was involved in the initial setup. It was straightforward.
We didn't really look at others. We just went with this because it made sense.
Plan ahead. Know exactly what it is you want to monitor. There's a lot of things you can report on. It can be a little overwhelming. So, have a plan.
It makes sense to go with VMware. They know better than probably any other vendor what exactly goes on with their Virtual Machines.
Most important criteria when selecting a vendor: If we already have solutions by that same vendor in-house. That's usually a better way to go, because we don't have to do as much research, then there's the cost. We usually get a better cost if it's just adding onto a part of what we already have instead of buying a new solution outright.