VMware Aria Operations Reviews

For most data center operations teams, it is pretty hard to get a comprehensive view of what’s going on in their IT ecosystem. Virtualization and cloud service abstractions have made cross-platform relationships between different layers of the IT stack more complex. Heterogeneous, hybrid environments are the norm. IT pros have found visibility to be the #1 challenge facing operations teams. VMware Blue Medora management packs aggregate operations data from the leading server, storage,compute and database applications into vRealize Operations for rich analytics and helped to achieve full stack view of the environment.

Using VMware vRealize Operations with Blue Medora TVS helped to centralize data center operations monitoring platform. By adding the True Visibility Suite, its helped to monitor  applications, database, virtualization/cloud, compute, network and storage using one monitoring platform.

All the Blue Medora vROps management packs have features like:

· OOTB dashboards

· Collected metrics

· OOTB Reports

· Alerts and recommendations

· External relationships

· Capacity planning

• Reduced cross-team friction by eliminating MTTI hunts through, siloed infrastructure tools.

• True Visibility customers can see up to 50% reduction in time for root cause
  analysis.
• Cleared up alert storms with built-in policies that disable alerts for your dev environment and other less-critical resources.
• Increased tier I app availability up to 50% by pinpointing problems faster and more accurately with dependency-aware dashboards.
• Were able to drill down to native-tool detail to find noisy.

One missing component was the integration of Log Insight and vRealize Business within vROps. But, with the new version of vROps (v6.5 & v6.6), this requirement was also met with, as the other products in vRealize Suite are now fully-integrated.

More than five years.

As such, no stability issues were experienced from vROps during deployment, configuration, and the collection of metrics and data into the platform. 

The client decided to add an additional node to increase the capacity and resources within vROps analytics cluster so it could support the additional metrics collection process. You can scale vertically or horizontally.

I have received excellent support from VMware & Blue Medora support team.

Yes, Engineered by Blue Medora and validated by VMware, the True Visibility Suite included an extensive knowledge portal and includes 24/7/365 individualized technical support

It was implemented in-house

By using vROps plus Blue Medora TVS you can Maximize Performance, Minimize Investment
Reduce the IT tools, eliminate silos and boost IT productivity by up to 67%.

• Deploy in minutes without additional services or expertise.
• Maintain performance, reduce administration with agentless design.

The True Visibility Suite is available in three editions: Standard, Advanced and Enterprise. 
These packages align with the various infrastructure teams, and offer a convenient
way to pick the best package that applies, without being tethered to just one vendor or
device type.

There were a couple of options that we considered, like Microsoft SCOM and SolarWinds, but the level of monitoring and dashboard visibility wasn’t there.

• Conduct workshops and capture monitoring requirements at a high level; document and understand the customer's requirements. 
• Study the customer’s infrastructure, as it will be useful during the implementation stage.
• Align the customer's requirements, so that all the required systems are monitored in the vROps platform.
• Work out the network firewall rules that are required to configure vROps.
• Use the vROps sizing guidelines and sizing guide spreadsheet prior to vROps deployment.
• Deploy the remote collectors for bigger environments as it puts less load on the analytics cluster.
• Post deployment of vROps, you should create a full-stack relationship dashboard, as it helps to identify issues at various tiers in a typical 3-2-1 type environment.
• Make use of role-based user account management.
• Avoid taking snapshots or backups of vROps nodes during DT window.

Our primary use case is to make sure we're getting the best value out of our on-prem hardware in terms of matching against vendor specifications to actual operation and performance.

This solution has improved my organization because we have it mainly based on our production units. We'll have about 400 guests running through it, across around 40 nodes and it just helps us to lower balance, see where the pinch points are and really keep us 24/7.

The most valuable feature is the insight into how our infrastructure is actually working and the kind of performance that when users say there is an issue, it gives some insight into finding out what's going wrong with it. It's because we have it mainly based on our production units.

I absolutely think this solution is intuitive and user-friendly. My team spun it up, we've got it through our ELA agreement and it was up and working in a matter of hours.

I would like to see them get a holistic view of the organization, not just focusing on the server and the state that it's running on but to widen that out from the end user all the way through. It's a key critical part but actually, it needs to bring outside of that, then to the networking elements and the inter-dependencies that are in hospital solutions.

This solution is a hundred percent reliable. I suppose it's only as reliable as our own infrastructure that it sits on but it is absolutely stable. We've had no outages from spinning this up and it's monitoring our upstate daily.

Scalability is a little bit unknown as we move into the cloud technologies because this is all about on-prem. From what I am seeing around the show today it's the next generation if it's got a place to help us with our infrastructure. 

Their technical support is absolutely fantastic. They are either a click away or a phone call away and are really responsive.

We were using the technology and it was just burning up too much physical resource, so having this gives that reassurance factor that we can size things appropriately. Investing was a very straightforward process.

The initial setup was extremely straightforward; download the product, install the product, put a key on it, add the host to it. Absolutely very straightforward.

We are not particularly measuring ROI but in terms of the level of investment that we've made into our infrastructure, we've probably got an extra 12 to 18 months worth out of what we purchased three years ago.

We didn't look into other options. We very much get to where VMware house is part of our strategy, it was just a natural fit into our infrastructure.

I would rate this solution a seven or an eight. We are starting to see the benefits and we are starting to use its recommendations and starting to tweak it down. We still need somebody to look at this data, analyze it, and make decisions. Once some of the automation orchestration goes in, then it will move up again up to a nine or something like that.

We use vROps to manage our on-site private cloud as well as our public cloud out in OVH. It allows us to perform trending and analysis on all of our workloads to make sure that they're running as efficiently as possible.

It has saved us quite a bit of money by making those workloads run more efficiently and it has allowed us to recover a lot of wasted resources.

The most valuable feature is the ability to right-size a workload, based on historical data for that workload.

It also allows us to "sanity-check" the entire infrastructure by getting monthly reports on how everything is performing and where we can make improvements. That's all done automatically, without any administrator involvement.

One issue that I had last year, they've already added. They've put some chargeback functionality into it, which they didn't have before. That was very useful for us.

It's a very complex product. It has gotten better over the years, but they still have some work to do. It still requires a lot of time, and some training, to get accustomed to it.

Moving forward, I would like to see some tighter integration with the vSphere Web Client, just so that I don't have to open multiple windows and jump back and forth. We're currently running vSphere 6.7 and there is a lot tighter integration between vROps and vSphere, but it can always be better.

I have no problems with the stability. It's always been pretty solid.

I haven't really had any need to scale beyond what we've always had. The last two versions of it, we've gone with the integrated, high-availability built into the product, and that was a welcome change for us. It's even better now not having to have any kind of load-balancer in front of it, so it's very nice.

I did add a couple of remote nodes. I think when we first started using it, that wasn't even possible, so it was nice having that capability. That did help us scale. If our company were to grow, probably through acquisition, which we seem to do a lot, it would be very easy for us to scale the solution.

For this product, we have not used technical support in a long time. Probably some four years ago was the last time we used it, which speaks to the stability. We haven't had any problems recently.

When I started with my current company, seven years ago, they were using another solution and it was terrible. It didn't give us any of the planning, the change management, any of that stuff that was built into the vROps. To be honest, vROps didn't even exist back then so they pretty much did what they had to do. 

When vROps was offered, it still took us a while to get familiar enough with it to adopt it and, ever since then, we've been happy with what we've been given. 

In terms of actually selecting a vendor, my opinion on what is important has just changed. Our storage vendor is just getting bought out after a period of uncertainty, so I would have to say longevity, first of all; stability. We need to know that they're going to be around tomorrow. Also, somebody that continuously innovates. I did a press release almost 10 years ago for VMware and one of the statements that I made then still holds true. I said, "VMware gives me things that I didn't know I needed, and now I can't live without." I still think that that's the way to judge whether or not they're still giving me what I think they should.

They're constantly giving me things, features that maybe somebody else is asking for. A lot of times, they are things I had never considered before and then I look at them and I say "I have to have that". If I don't look at your product and say, "I have to have that," then I probably won't buy your product because I hate going to ask for money.

The setup is pretty straightforward now. It used to be much more involved and a not very intuitive deployment at all, but now it's really nice.

There are other providers out there that will give a similar experience to vROps, but we're comfortable with it. We were being pressured to look at these other things because one of our acquisitions used one of them. They wanted us to come to an agreement on what was best and we didn't like what they were using, so we stuck with vROps. Now they're with vROps, and lucky for them.

You'd want the ease of use to be the primary draw to the product. Somebody who is evaluating vROps - when I didn't know anything about it and I was looking at it for the first time - it is very daunting. It's very complex and very confusing and especially, back then, there wasn't really any good training. I would tell a colleague not to try to do it alone. It's worth the effort, but you need to get help, either from your TAM or from somebody else, a colleague of yours who uses the product. Get some guidance because it's a very difficult product to get into and master on your own.

As good as it is, it's not perfect so I would have to rate it a nine out of 10. I would love to see something that I could turn over to a junior administrator who hasn't had my level of involvement with the product and say, "Here you go," and have it be, from a certain perspective, clear enough and intuitive enough for him to at least start getting some information out of it.

Like I said, it's a very complex product and you can get a lot of stuff out of it and I like that, for myself, but it's hard getting other people involved with it when it takes so long to figure out what's going on. I think that the engineers who created it are on the same page as me. As soon as it opens up, I see a wealth of information. But it's very daunting to somebody who is new to the product.

The solution helps to monitor our infrastructure. 

VMware Aria Operations is the leading industrial solution for monitoring VMware infrastructure stacks. It has evolved to provide more insights into customer capacity planning and has become more data-driven. The level of monitoring and the granularity it offers are unmatched by any other product in the infrastructure management market.

Even though I have worked with Microsoft, I would say this is the best tool available. The predictive analytics feature is very useful because it helps customers manage their capacity better by predicting usage and providing guidelines. This feature helps prevent overutilization and potential failures. I have a very positive opinion of it and am optimistic about its continued growth.

Every product has room for improvement, no matter how good it is. For VMware Aria Operations, I think the main area for improvement is its integration with other cloud vendors, like AWS, Azure, and Google Cloud. The integration process is quite complex and often requires VMware personnel's involvement, which isn't always a great experience. So, integration with hyper scalers would be a key improvement.

I have been working with the product for two years and have ten years of experience with the VMware solution stack. 

I would rate the solution's stability an eight out of ten. 

On a scale of one to ten, I would rate VMware Aria Operations' scalability around seven to eight. It handles thousands of users well, especially in mid-scale enterprises, but there can be some performance impacts when scaled to very large enterprises.

I would have rated support higher before the Broadcom acquisition. However, after the acquisition, I felt that support had fallen below par. When Broadcom acquired VMware, they brought a different vision focused on consolidating VMware products and prioritizing on-premises customers. This shift led to a decrease in support. 

Neutral

The tool's integration with other hyperscalers is difficult and not seamless. The solution can be deployed both on-premises and in the cloud. The deployment time varies; if everything is in place and you have good support from VMware, it might take two to three days to set up.

I rate the solution's pricing a seven out of ten. 

I would recommend VMware Aria Operations to others, especially for those working in infrastructure monitoring with VMware environments. It's a top tool for this purpose. Overall, I would rate VMware Aria Operations an eight out of ten.

We use the solution to monitor the capacity and performance of virtual machines.

The solution's best feature is capacity and performance monitoring. Using it, we can generate reports for each virtual machine.

They should make the report-generating feature user-friendly and customizable. Also, they should add automation features to store or delete the files in the database.

We have been using the solution for six years.

It is a stable solution, and I rate its stability as an eight.

We have two or three solution users in our organization. I rate its scalability as a six or seven.

The solution's customer support team responds quickly. Although, it depends on the severity of the issue.

I rate the solution's initial setup process as a six. It takes a week to deploy it.

The solution is costly. Its overall cost is around $900,000. Thus, we have only purchased its license for operations. We paid around $800,000 for four years.

I advise others to buy the solution only if they have a large environment and multiple clusters. It is not a beneficial investment for small businesses. I rate the solution as a seven.

We monitor workloads with vROps. For example, if a new customer wants our services, we need to know the impact if you put their workloads in our platform, i.e., if this new workload will have any impact on the product or platform. We need to know the increase in percentage relative to CPU, memory, and disk. So, it is important to know how a new project or workload can impact the product or platform.

It can decrease the downtime of a client who recently has experienced performance issues by 10% to 15%. This tool can help you decrease those kinds of circumstances. Downtime is also about the design of the solution and how you put workloads in your infrastructure. If you put in more VMs than your infrastructure can support, you will have a big problem with all your clients. That is the reason that it is very important to check the performance every day of the ESXi host and vCenter from maintenance mode. If you periodically check if you have had a security issue, then you can resolve it as soon as possible from a security perspective.

vROps is selling because we have a lot of customers who need to know their usage of VMs, e.g., is the sizing of our VM good or should I decrease it? Or, in reverse, I need to increase the size of the VMs. All this is about the performance and what VMs resources you can liberate from the platform.

It is a very good tool for day-to-day troubleshooting. For example, if you have CPU-ready VMs, you can build a report of VMs who recently had an issue. It is useful for making decisions and troubleshooting issues. I think it is the most powerful option on the market.

You can schedule reports on the platform that are very useful day-to-day. 

For project management and new clients, the What-If Analysis is very good. You can use it for workloads. When you are adding new workloads to your platform, it helps you avoid impacting your production.

There is another useful tool for undersizing or downsizing VMs, which has more resources than they can handle. 

We have a dashboard for the latency of the datastore on the storage side. For new architectures, we have a vSAN dashboard for latency based on the usage of vSAN, because you need to regularly see the used space.

The newer versions (5, 6, and 7) are more user-friendly. There are tabs upfront where you can see if you need a dashboard, for example. You also have a building option, if you want to build in the infrastructure and how. It is very customizable from that point of view.

It is a very good tool for efficiency. From an ESXi host perspective, you can see the CPU rate on a dashboard. For example, if the relationship is 5:1, then it is a good standard. If you exceed this, you can get into problems with VM performance. If you have a host with a VM inside of a host using the CPU, you can balance that manually. It can also help you move the VMs into clusters. 

The older versions are not user-friendly.

If you have an operations center, you can put a big monitor with its dashboards so you can see what is going on in your platforms. However, there is no real-time. It takes about five minutes to refresh info. It is a good option if you need to see the entire landscape of the solution, e.g., the CPU, memory, and disks. For example, if you have plugins for VxRail, and there is a problem, will you be notified?

They could mix in parts of VMware Skyline into vROps to make it more efficient.

In a previous version, you could click on a cluster to see a lot of information about efficiency, e.g., when you will run out of memory, CPU usage, and RAM in percentages. In newer versions, you see this information in megahertz and kilobytes, not percentage. I don't like this change so much. If you need to present information to your boss or Director of IT, the information would be better with a percentage. Now, you have only a big number and don't know the percentage of use that you are getting from the VMs. I don't know why they changed it, but I liked the percentage version more than getting the numbers for megahertz of memory. Also, kilobytes of memory is a very large number. For a simple view, gigabytes or terabytes is better.

With the What-If Analysis, if you put some information in, and then add another workload, it is not possible to view the two workloads in the What-If Analysis. For example, if you have a customer who wants to up your sizing by 30% more, and then you have another customer tool which needs sizing, how can you leverage resources? If you add these two customers, then your sizing might be 70%, but you only have 30% of your resources free.

I would like to see more information about public cloud plugins with Amazon, Google Cloud, and Azure. This is really important in the future. Companies are moving to public clouds to maintain their workloads since they don't have downtime, which makes for very stable platforms.

In the future, they could add a central administrator for vROps. For example, if you have a large environment from multiple countries, then you need to look at the landscape for performance and forecasting.

I have been using it since 2017.

Version 6.7 is more stable than the previous version. There is no real problem with the purchase of upgrades. So, it is a very stable platform if you get good sizing of the tool. If the VMs do not have the appropriate memory and CPU, then you can probably get performance issues. So, this is important for the tool. From the disk size, it is better to choose the thicker VMDK to maintain a good performance if you had a lot of vCenters.

It is a scalable solution. If you need more vCenters or information, you can simply add VMs onto the cluster. From the vROps cluster, you can get more resources from the VMs. You only need to deploy a new VM for the cluster of vROps, and this automatically moves the workloads. If you put an IP, then the server will recognize this new node from the cluster and the job automatically. So, it has very good scalability.

There are a lot of plugins. For example, I use the vCloud Director plugin for private cloud. We also have VxRail. VMware and Dell EMC work very well together. From the VxRail side, there are plugins that can help show you more information for your platform.

Their support team is very good. They will explain things to you. You are very involved with the problem. I think the Latin America team works out of Costa Rica.

We had some problems with the views in version 6.5. It would show me 110% usage, which doesn't make sense. We opened a case with VMware. I worked with their development team in Bulgaria. We resolved the problem. 

I had a problem with a vROps plugin because we upgraded our vCloud Director. The plugin didn't recognize the upgrade. At that moment, we are doing a workaround for this while they apply a new update from this plugin to resolve this problem.

We had a demo for Tanzu from VMware for vCloud Director. We needed to show a customer how vCloud Director works with Tanzu and the Kubernetes solution. From that demo, we built a solution with VMware that links with vCloud Director as a platform.

VMware Skyline detects a problem in your platform. It has the ability to create a ticket to VMware directly, then you will receive a call from VMware, "Oh, you had this problem." It also monitors security issues.

The initial setup for the demo is very easy. You have 60 days to use the trial version and see what the tool has to offer to you. You only download the URL, then configure some parameters, IP, and sizing. Also, in the wizard, you have an option where you can see VMs with more CPU, memory, and disk. 

The deployment was first a demo version, which was standalone with one VM. Then, we needed to add more vCenters to vROps, so we needed to add more VMs. Finally, we had three VMs to maintain the database of vROps.

We started with a demo version to see what the tool has to offer our organization in regards to the VM's efficiency and health. This is very common for our company. They ask you, "What if you put more workload in our infrastructure? How will this impact a new workload in our environment?"

You have two options to deploy VMs. 

1. You have thin space. If you use VMs, then there is space to increase. However, if you decide to choose VMs with thin space, probably for an SQL database, there is no other good option from a performance perspective.
2. You have thick space. For example, you have a disk of 100 GB, and you say, "All" in the first deployment.

The billing is complicated because every country has a different option. Here in Chile, we don't pay for this kind of service with the Chilean pesos. We use another currency. In the future, I think vROps needs to work with governments for a native solution.

It is useful for determining whether to make decisions. Also, for our troubleshooting issues, it is the most powerful option in the market.

vROps provides a good native solution if you are using multiple VMware tools.

The design and what you sell to customers will impact your infrastructure.

There is a new version, but I haven't used it yet.

I would rate this solution as an eight out of 10.

Our primary use case for the product is to to look at all of our infrastructure and provide stats to our performance team for most of our applications. We integrate with vSphere and have a fairly large vSan, which we rely on vRealize Operations to keep on top of to let us know if there are disk failures, alerts, or system health issues. This is pretty much the day-to-day triaging problems of vRealize Operations. 

It has been performing very well. We've been a vRealize shop for about five years. There were early kinks in the some of the virtual appliances as we rolled them out, but for the last year and a half, it has been rock solid.

It has enhanced our ability to troubleshoot and effectively manage our solutions to understand what clusters are having issues and diagnose those programs right away, so we can be proactive. We are now proactive, which we weren't before. We achieve this through vRealize.

We're catching problems earlier. The troubleshooting which goes into it is proactive. One thing I did recently was right-size all my clusters. I did that through vCOPS within a couple hours. I was able to move workloads around to different clusters and optimize my whole environment, which was across about 300 ESX hosts. So, it's very powerful.

We pay attention to disk snapshots which are in the overhead on SAN data stores that we have. They have the ability to collapse different virtual machines to different data stores and do a lot of cleanup. Without that visibility, we would probably have a lot more wasted space and more money that would have been out the door.

One of the things that we had to rollout in the last year and a half is compliance. The product has done a great job of ensuring all of our virtual infrastructure is compliant, and we have met all our regulatory compliance, which has been a huge help. 

There is rich dashboarding, which has the ability to customize dashboards. It has gotten better with the versions. I have assigned it to some co-ops who learned it within a few weeks and have dashboarding almost right away. It's very intuitive platform. 

Working with vendors more to suck more pieces in via the infrastructure and do that for zero cost, if we could. While not always based on VMware, if we want to add something in like Microsoft SCOM data, we have to go out and buy it, or certain widgets we have to buy. The more pieces we can receive for free and have everything cooked into vCOPS to give us a single pane of glass (for zero or minimal cost), this would benefit us.

We don't have any downtime for our vRealize app. It's definitely helped out with the stability of our platforms. 

It's very flexible and scalable. Adding things in has become a lot easier along with utilizing some of the capacity analysis features. If I have a project to add in resourcing, I can go to vCOPS, and do an analysis. I can put it through its workflow, then it tells me what to add and it's usually pretty accurate.

From time and time again, there's little tweaks you got to make to the vRealize platform. The technical support has been excellent. 

I haven't had any problems. Usually within an hour or so, we have diagnosed the problem and have a solution that we either need to implement or implement right away. 

I was involved in the initial setup a long time ago. 

Now, the lifecycle product has provided some things which are very easy to roll out within the vRealize suite. It is just check things out and roll it out, then it sort of monitors the application. This has greatly enhanced our ability to roll out vCOPS quickly and augment it too.

The ability to not have to buy as much hardware. I can look across all my clusters and spread the resourcing out. I can see where I have some low and high points, then not have to go out and buy a whole bunch of blades which I don't need. It has helped us in our capacity analysis and purchasing. 

We looked at Turbonomic. It was expensive because of their ability to learn your environment. We already owned a piece of the vROPs suite, the compliance manager, so we sort of fell into the suite. We thought we can go out and buy Turbonomic, which will cost us so much money or we get the enterprise product because we already have the compliance manager piece, which is what we did, and never looked back. 

It's an excellent solution compared to others. When I first looked at a Turbonomic was a few years ago, they had a few more features than what vCOPS was doing at the time. I gave that feedback and all those features are now in the product. Therefore, there's not much of a comparison today.

• Dig into your requirements.
• Put a list together.
• Then, start taking a look at vCOPS, because it's a great product. It most likely will fit your requirements. 

I would highly recommend the product to anybody who is out there. It has saved us a lot of money.

I would give it a nine out of ten. It's an excellent product, but there's always room for improvement. I never give anything a ten.

Most important criteria when selecting a vendor: We usually put together a list of requirements about what we are looking for within the product. One was the extensibility; the ability to kind of have a single pane of glass. This has been one thing which benefited us with vCOPS, as we can snap in almost any other vendor's hardware, whether it be UCS, Dell, or Cisco switches. This was a big requirement for us.

Optimization and reclamation.

It's been very successful. Before, we didn't know, as an organization, where some of the VMs or platforms were. Now, it's unified our organization to troubleshoot.

So far, since we upgraded the product, over the course of a quarter, I've reclaimed in our team, over 2,500 CPUs. That's a significant amount of CPUs, and we're still continuing. And using the DRS automation field and other features, we're seeing a lot of success as far as load-balancing, and we can also forecast some of the trends that we have in our organizations with the product.

Regarding the time to troubleshoot issues, on average, a NOC user or operations could spend at least 15 minutes just finding that VM or the issue. The solution is saving an average user, like myself as a consumer, about 40 percent. We have the issue, we have the problem. Before, we were spending an additional 40 percent just trying to find where the issue was.

As far as cost savings go, we're seeing significant growth as an organization, and we're also seeing the cost savings in the reclamation. Right now, we're being challenged regarding our growth, and we have to find capacity, and using the product sufficed a lot to not (have to) purchase other new products.

Gives a glass pane for our organization, it makes it very simple to give operations a simplified go-to product to find a VM, for example.

It's absolutely very intuitive. For example, we have a big environment. A simple case, for example, is, we get a request when there's an issue with a virtual machine, or the organization is (asking), "Where does that machine live? Does it live in which data center?" Now, they just plug it in on the search field and it gives them all the simple information: data center, the host, location.

One way the solution could be improved, in my opinion: management packs, more native management packs with API.

Compared to other versions, this version has by far, in my opinion, exceeded expectations.

Scalability is very simple and very efficient, as a product.

Technical support is always better every year, and so far it's actually all the new features that VMware has for technical support. One of the features is that it's very simple to just plug in your issue and you get a response. But I notice that the response time is more efficient than in previous years.

When I started at the organization, we had other, existing competitors, and we also had vROps, but it wasn't fully scaled-out for our organization. But I saw the value just based on my experience.

vROps was definitely on the top list, then we had VMTurbo (Turbonomic) and there's another product called Runecast. We have higher-tier products like Scalar but it's not really an operation type.

Pick something very simple and very intuitive and very efficient for operations. As an engineer, just basically simplify. It's a simplified product and vROps is the product that I would highly suggest and recommend.

In terms of how the product itself has improved, the first one I've seen is the UI, the dashboard, and the intuitiveness of the product, how it works with the web browser, it's very efficient and fast. That's one of the improvements I've seen.

Right now, I strongly feel the product is a solid eight. I haven't got the exposure to the vROps products, I would give it a ten, but the way I feel right now once I feel that it's a solid ten I'll give it.