VMware Aria Operations Reviews

vROps has been able to cut down our time to be able to find our problems, if we have something arise in our infrastructure. We have certainly found anomalies, and it has alerted us to those anomalies and where we can find the problems, thus getting our meantime realized solution down. We've also been able to rightsize our VMs because of vROps. It's able to tell you if you're over-provisioning VMs and reduces memory, if it's not being used, and these sorts of things, so we're rightsizing our VMs.

It also gives you predictive timelines for when you're gonna run out of capacity in your resources, so you may plan accordingly for all of your resource planning.

• Probably in the configuration of it.
• Configuring the different types of alerts.
• Maybe streamlining the process a little more.
• Make it a little more user-friendly, possibly.
• It's a little difficult to configure, maybe.

It is a stable solution. Upgrades have been smooth. We haven't had any problems there, but a little bit of time configuring it. Although, I noticed in their latest release (6.2), it's much cleaner. It seems a little easier to configure, manage, and navigate.

It's not a scale-out architecture, but definitely as much infrastructure as we throw at it, it's able to monitor it. If your infrastructure grows, or even into the Cloud, they have plugins that can monitor VMs, AWS, and Azure.

The support is VMware, and it's good support, as you'd expect.

It's fairly straightforward. There was initially, when I set it up, a version 5, and it had a little bit of different components that you had to configure and put together. I believe it's a little easier these days.

It's a very good product. It's really given us a lot of insight.

Most important criteria when selecting a vendor: The partnerships with other vendors and integration with other products that we have, therefore their reputation in that, and their support.

It has a lot of great reporting features in it that help us scale with our products, and to scale with different things that we're trying to work on, on a day to day workload. It's a great tool to analyze those type of things for us.

Honestly, I think it's pretty good right where it's at. It could always add more features. But for right now, it's got more than what we know how to run. It's just a great product.

Very stable. It's something I check every morning when I come in. It just runs. It has a lot of great features for a lot of our applications where we're trying to figure out what's going on with them in the background.

It scales great. It basically watches an application and tells us where we might have too much CPU, or not enough memory. It helps us fine tune things pretty nice.

It's awesome. I mean, we get help if we need anything, but a lot of times you don't even have to do anything, because the product just runs.

It's pretty straightforward. We didn't have any trouble setting it up.

It's a good product. It definitely helps troubleshooting, and helps you find things a lot faster than just trying to dig for a needle in a haystack. It's definitely a reliable product, and it's definitely helped us save a lot of time.

The value from vROps, from a traditional sense that we had, is the visibility into the back-end, to know when we are having issues with VMs before it actually becomes an end user issue. Especially with hard drives, making sure we extend those out, memory and CPU utilization, as well as overloading host.

I would like to see a free offering. Cost is always a factor in any sort of line. Obviously, the value added is there and it's worth it.

The automation piece could be done simpler.

REST APIs: more REST API calls. It seems like all of the technologies are facilitating those calls back and forth. The more we can get inside vROps, the easier it's going to be to integrate other product lines with it as well.

It's very stable. We've had no issues with it that I can be aware of; even through the upgrade process everything has been very clean.

It will scale, we've seen that as we've ramped up, we've had a 30% increase year-over-year over the last five years. We've never had any issue with the VMware or vROps installations at any of them. As a matter of fact, we only see increased usage and availability with it.

Tech support has been very good. Quite honestly, sometimes they're better than we are. As opposed to getting back to them, they almost hassle us to make sure that they're getting the information. They want to make sure that they get the solution in hand and they close those tickets. It seems that we don't move as timely as they do lots of times.

It's fairly straightforward, obviously, with their initial installation. The more you become an automated system, the more you really delve into the dynamics of vROps, it can become more complicated, but no more so than any other product line. I feel like it's the easiest of any product line to get through. Obviously, there's intricacies with any of this technology.

In terms of the most important criteria when selecting a vendor, I feel like you have to look at it all. You have equal shares.

I work in an industry that is a very secure environment, and you have to have the long-term stability there. One thing that we're asking all vendors that we're looking at their product lines is, "Are you viable five, 10, 20 years from now?" We don't have that three-year turnover rate that a lot of other industries have. We want to make sure that whoever we partner with is going to be there, to support us for the long haul. We don't want it to be purchased and gobbled up, in an environment that is today.

We know that VMware isn't going to be. It is a very well-maintained product line throughout its life expectancy and will continue to be.

As I said, I would probably give it a 10, or greater if I could, if it had more of those REST APIs. They open it up a little bit more to integration with, honestly, the competition, as well as some of the newer technologies that are coming out. I feel they'll have to, and they'll mature in that respect over the next year to two years, but I wish we had a little bit more today.

The ability to monitor our trending and growth in our environment. It gives us an idea of when we're running out of capacity, how quick our growth is occurring, where it's occurring.

Knowing our environment, being able to properly size and prepare for what the future holds.

Maybe to get a little bit more granular with storage and i-apps.

Also, some of the configuration settings are a little bit overwhelming to try and understand all of the implications and ramifications of what they do, so something not quite too intense to configure initially.

We have no problems with it.

So far it's met our environment very well.

So far I've only had to use it one time and they were very helpful. We did have some storage issues with it. They resolved it within probably one or two phone calls, so I was very happy.

We didn't have very good visibility in our environment at all. The standard C# and web client just wasn't giving us the visibility we needed. vROps did that very well.

Very straightforward.

In choosing a vendor, obviously we have to look at their ability to answer all of our questions, make sure that their solution is in fact going to meet our needs and their tech support later on.

It was real simple, and once you get involved with it, it's just a matter of getting some hands on time and playing with it.

We're running a couple of different flavors of vRealize Operations. vRealize Operations gives us the ability and the insight to be able to see what our VMs are actually doing.

• Who's the hungriest?
• Have we got any runaways?
• Have we got any noisy neighbors?

We can address those things. We can separate our test from our production, and make sure our production workloads are getting the launch share of the resources.

I think some of the improvements should be to the adapters, and the adapters which are available to customers. I know there's a lot in the marketplace, but we're looking for more, because we are a pretty large-scale company throughout the State of Louisiana. We've got a lot of different products, and we're looking for a lot of visibility from those other products that we have inside of vRealize Operations.

vROps has gone through a maturation process, and we've grown along with it. We've come to appreciate the things which are offered.

It is a very stable product.

It's quite scalable. We're adding additional vCenters at different regions to a single instance of our vRealize Operations for our virtual server management.

vROps tech support is super. Any issue that we've had, even in a how-to perspective, they've been able to assist us. We've had some things happen late at night or early in the morning where we've needed to open a preemptive service request, for an upgrade, support for a module, or a plugin that we needed to do, and they've been right there for us.

The vRealize Operations setup, installation, and configurations are pretty straightforward. We, as a customer, actually did two of our environments ourselves. We used an implementation service for the first. Then, we used that as a blueprint and a pattern to deploy our other two environments.

It's great from a scalability perspective, and it gives us all of the metrics that we need. Our configuration, or dashboard configuration, and deployment are quite easy.

We use vRealize Operations Manager primarily for capacity management within our environment. To understand the capacity that we're using for vSAN storage, for compute and CPU capacity within our virtualization environment.

vROps is, by its nature, a very complex product. We have seen a lot of improvements around the usability of the product. With each subsequent version, the product is becoming much more user friendly. It's much faster to get up to the speed on the product, to become familiar with it, and to use the built-in dashboards. Especially, the included dashboards around the vSAN Management Pack, that are now integrated into the product, and are available to use immediately upon installation, without any additional configuration.

Those are areas that the product has been improving drastically, and we are working with VMware as a reference customer, and as design partner, based on our experience, to help continue improving the product.

vROps is stable, it's a mature product. We're using the latest release, which is 6.6.1

vROps is extremely scalable. It can size from a small, to a medium, to a large environment. There are options to have HA enabled or disabled, so the product scales extremely well.

VMware has a number of support options related to vROps. It's supported as standard production support. It's also supported out of VCS and MCS support. We are a VCS business-critical support customer, and we have had a good support relationship with the product.

With newer versions of vROps, VMware has improved the setup experience drastically. The new versions of the product install very quickly, very cleanly. Adding additional nodes to the environment is very fast, very easy to do.

For us, the most important criteria when selecting a vendor are that we look for a company that's going to support our business cases, that has an established track record of stability, and performance. Someone that's going to stand behind us and support us as we utilize their product. Those things are extremely important as we're evaluating whether to make a purchase.

I rate vRealize Operations as a nine out of 10 today. There are still some areas to improve around the initial user experience. But, the product has improved significantly with the more recent releases.

It's valuable because it helps us look at our performance statistics for our environment.

Where the product could improve would be the UI. They just changed the UI on it in this last version, but they could always expand on that, make it a little bit more in depth.

Very stable product, no downtime.

It's very scalable and it will meet our needs going forward.

The tech support is good. I haven't actually had to call tech support on the product as of yet.

We were previously using SolarWinds and we switched to this because it's made by VMware and it works better with VMware than our SolarWinds solution did.

It's simple to deploy, it's an appliance. You just go into your vCenter and deploy it and it's up and going pretty much. You go in and you put in your information for your vCenters, it goes out and collects the data and you're off and going.

I rate it an eight out of 10, because there's always room for improvement, but overall I'm very happy with it.

vRealize Operations enables us to do a lot more looking at the data. Basically, it enables us to look at the information coming in from vCenter, vSphere. We fully integrate it in our end user computing side. So Horizon, plug it into our Horizon data.

For vRealize, in the state that we use it in, for our Horizon end points, there's probably a little bit more data that they could have available for Horizon than they do today. I think it's more vCenter focused. Their integration with Horizon probably could be a little bit better.

It's a stable solution. It's still growing. It's got room to grow, I would say. There are a lot of things they could do to make it better. I think they're pretty open to that feedback, and allowing us to expand it more.

It's highly scalable.

Tech support's really good. Anytime we've had any issues whatsoever, any of our engineers, or whoever we contact, is pretty available within a few hours of our posting a problem to support.

Setup's a little complex at first. But once you actually know what you're doing, and when you're setting up some of the other nodes - besides the primary one - the collectors and everything, it tends to go a little bit better.

From my standpoint, when selecting a vendor, we look at support, their customer service, what is their responsiveness to any of the problems we have. Scalability, "ease-ability" in the product. Is the solution fully integrated into what we need it to do?

I rate it a seven right now just because it's a little bit complex in its setup. But, I think, like I said, as they improve it, get a little bit better, then it'll make it easier to use.

We use vROPs primarily on our VEI side. It gives us a lot of insight into the session experience that I haven't found in another product. It matches PC over IP latency times, packet loss times; I just haven't been able to find that using another product anywhere.

I think it pretty much covers everything I need. I can monitor my storage performance with it. Obviously my host hardware, my virtual desktops. I know it can do virtual servers if we were licensed for that. We don't have NSX. I'm sure that there are add-ins for NSX for it.

It helps us verify when a customer complains about, or an end user complains about VDI performance. "Is there something going on in the session, network related between the endpoint and the virtual desktop?" Sometimes we are even able to find performance problems or identify network issues before an end user notices it and opens a ticket.

Monitoring our vSAN environment still seems to be touch and go. It doesn't always report correctly on that.

What would be helpful is more intuitive troubleshooting or more intuitive messages. Some of the messages that you see really don't make sense. When you start diving in to them, it gets better, but a lot of times there is still a lot of lack of clarity. For example, where do I go to try to figure out exactly what is causing this? Something a little more solid, maybe even link it to some KBs or that that might be related.

It's been a very stable product. The upgrades are simple, overall. I haven't had any problems that have come out of updates at all or upgrades to it. Very solid.

We are only using it on a VDI environment of about 550 desktops, but I know from reading the guides that it scales out really well.

I have had to contact tech support once or twice. I had a little trouble getting the deployment set up so it would exclude servers, because we aren't licensed to monitor servers with it. Sometimes, certain versions, when you add a feature, pack it in. Sometimes they don't work like you expect them to. But tech support has been great on that and they help get it figured out.

It was deployed when I got there, back in the vCOPS days, and I basically abandoned that installation and did a fresh vROps deployment because we were so far behind it was easier than trying to do the stepped upgrade.

Some of the earlier releases were a bit more complex to get deployed. Newer versions have been really easy. I think I did one other complete redeployment again because we left to get out of scope, and I had a lot fewer questions and a lot fewer issues the second time.

Overall, vROps is a very mature product. It is stable. It's got a lot of features in it and sometimes that's the downside. There is so much power to it it's hard to know how to use it completely.

If you are going to deploy vROps, make sure that you've got time to dedicate to learning it. The deployment is relatively easy. The learning how to leverage all the features of it afterwards can take some time. Leverage educational resources, whether it be through VMware or leveraging a partner if you need to. It is a really good product, it can just be a little overwhelming when you first get a hold of it.

vROps was there before me. When I got there, I was asked if I felt that there was value in keeping it and I said yes, absolutely.

The most important points in vendor selection are

• the vendor's reputation
• how good their products truly are
• how long they've been around
• the features supported
• the capabilities of their product
• how user friendly it is
• the comfort of the interface
• the overall stability of the product.

Single pane of glass for metrics. This helps us see if we have issues with network storage, compute.

It's enabled us to more quickly troubleshoot end user problems.

Being able to take and work off activity between it and other products.

Being an all-inclusive appliance, it's been very stable for us.

We haven't had to scale.

I haven't used it for vROps.

We've spent far too much time troubleshooting datacenter issues and once we implemented vROps we were able to save a lot of time.

I was involved and it was very straightforward.

No.

Looking for vendors, the most important thing to consider is their support.