VMware Aria Operations Reviews

I use the solution in my company for the virtualization purpose. Basically, the server virtualization is the main purpose. Other purposes are for the cloud part, which is the private cloud. My company has a local telco customer in Pakistan who works on public cloud infrastructure, and they also have VMware Cloud Director product deployed in their environment.

The most valuable feature of the solution revolves around vRealize Operations, which is a good tool. The product is highly reliable, and it is easy to deploy and manage.

There are some challenges with the tool right now after Broadcom's acquisition.

The major challenges associated with the product stem from the fact that after Broadcom's acquisition of VMware, all partners are no longer VMware partners. One has to reapply for Broadcom's partnership, which is a very time-consuming process. Broadcom seems to be confused since it does not have the exact partner strategies that a product needs to have in place. Broadcom does not provide a good pricing mechanism, and it also has some other issues in areas like distribution. Previously, VMware used to use Aptec, an Ingram Micro company. Broadcom has some issues with Aptec, so currently, it does not have a deal with Aptec, and everything is messed up. Broadcom does not have a proper distribution mechanism, so we have delays in getting codes and all that. After so many reminders, once we get the codes, things are still very time-consuming, and the prices are still not good. My colleagues who work with VMware products were opening support cases on VMware's portal, which has now become Broadcom's portal, which does not have enough information like VMware's portal. Although Broadcom has been trying to integrate all of it with its own portal while also attempting the existing VMware portal with the Broadcom portal, the migration does not seem to be successful. Broadcom has missed out on a lot of data, which means that previous service tickets that were generated under VMware won't have any records. You cannot use a learning mechanism from existing information, which makes it a time-consuming process. We have to go back to the existing information from VMware to figure out what the solution is for a problem. With the acquisition of Vmware by Broadcom, we have to do all things from scratch, and all such things are very painful, and customers, partners, and our company feel troubled. Everyone is trying to see how to get rid of the vendor. We are just trying to find an alternate product.

The pricing mechanism is not available here. There are some distribution issues, and there is not enough information on the portal. The migration process from VMware to Broadcom actually messes up a lot of data.

I believe that the scalability area of the product has scope for improvement, and I say this based on the feedback received from my team.

I have been using VMware Aria Operations for ten years or more. My company has a partnership with VMware. My company is a customer of VMware.

Stability-wise, I rate the solution a ten out of ten.

I don't think that the product has any mechanism in the area of analytics.

I rate the tool a ten out of ten.

I rate the technical support a ten out of ten.

Positive

The product's initial setup phase was easy.

The time required to deploy the product is something that varies from one customer's environment to another customer's environment or site. I can say that the product is not a single table that can cure everything.

The solution is easy to maintain.

For a small environment, only one person is required to maintain the product. If the size of the cluster is big, then a few people are required to maintain the product.

I have experienced an ROI from the use of the solution, but the prices are still not much economical.

If one is low price and ten is high price, I rate the product price a ten.

I don't think that the product has any mechanism in the area of analytics.

I rate the tool a ten out of ten.

The most common use case for vROps is to monitor infrastructure. Infrastructure includes, for example, your virtual machines. 

If a customer has an on-premises data center, they tend to integrate their adapters with vROps. This means that if there are any issues, alerts, or anything else that goes wrong with the system, vROps will pick it up. 

It will then use an inbuilt algorithm, depending on the events and alert system that you have configured, to trigger an email. This can help you to avoid a lot of problems in the future. 

For example, if there are a few appliances that are being monitored by vROps and their root directory or any other issues are getting beyond thresholds, say 80%, it will automatically trigger an email. If you have any ticketing system integrated with vROps, it will then trigger a severity one or severity two ticket to the respective team so that they are aware that there is something that might go wrong if it is not looked at on time. 

So, it is basically helping customers to avoid those situations where they might get into any issues or trouble. So, it is monitoring your system. 

Another stuff, so it is like if you want to have any visual representation of the data, of the performances, or of the data that has gone through in the last hour, last week, you can create a lot of dashboards on that, which is a visual presentation of the data. 

So, it helps you in a long way to monitor and understand your environment.

One of the things that is really valuable is its ability to help you implement security measures into your organization's standards. It helps you to have full control over more than 90% of the hardware and network infrastructure where you are installing vROps, so that you can have granular control over the infrastructure, which is pretty important these days. 

It's deployed mostly on-premises, but you can deploy it on the cloud as well. So, as most customers today are going for hybrid cloud deployment, they need a tool like vROps to give them a standardized, centralized view to monitor their infrastructure across both on-premises and cloud environments. It provides a single pane of glass to see what is going on across the entire infrastructure. 

vROps is a VMware tool, and most of the applications that our customers are running are virtual machines. So, when you have an infrastructure that mostly uses ESXi hypervisors, vROps really help you to have better control over your infrastructure and what is going on. This can help customers to run their day-to-day operations more smoothly. 

Moreover, in the older days, we used to perform health checks and other stuff manually. vROps automates a lot of these tasks, which lowers the burden on the operations team so that they don't have to worry about keeping an eye on each and every sort of thing. Even in the off business hours, when no one is there to take care of any stuff, vROps is still monitoring all of the data, appliances, and everything else. This helps them out in a big way.

The first area of improvement is cost. VMware licensing is always a bit costly. It has never been an open-source tool or something like that. So there are costs associated with that. 

Another thing is that you somehow need to have high-end people to perform the integrations with vROps as well. It's not as easy as it seems to deploy and integrate it with the different systems you want to monitor. 

It is user-friendly, but everything needs some specific skill sets. For example, if you go for even vRealize Automation, it comes as a bundle. So vROps is just one part of vRealize Automation suite. So, we need to know the product before we can start deploying it or start using it. We need to have people who have experience with specific tools before we can use them in our day-to-day operations.

So, for me, based on my experience, costing is one thing, and then there are the integration challenges that our company faces. And along with that, it does take up a bit of resources as well. It is resource-intensive.

I have not been using it directly because I work as an architect. Whenever there is a project for customers using vRealize Operations in their environment, we are the ones who have been designing the infrastructure with respect to vROps. 

So it has been around 12 months or more that I've been associated with projects where I have been helping customers deploy vROps and how to make proper use of this tool.

The stability of vROps depends on the environment that you are using it in. vROps comes as a suite, and when you're using it with other VMware products, such as vRealize Automation (vRA), vRealize Network Insight (VRNI), and VMware Cloud Foundation modules, it is already compatible with those products and is generally pretty stable. 

For example, when you are using it for virtualized workloads or VMware Virtual Desktop, it's very stable.

It is a scalable solution. You can scale it up depending on your configuration setup. 

There are different options for scaling, such as multi-node setups and collector setups. If you need to collect more information from different tools, you can simply add a collector to your environment. 

vROps is a good choice in terms of scalability. Even when you scale it up, it's not a big hassle to put more load into the system.

As an architect, we mostly design vROps implementations. The day-to-day operations are typically the ones that reach out to the support team. So, the support is mainly for people who are managed in the customer environment. 

We provide guidance on which integrations or adapters to use, and how to get the endpoint systems integrated with vROps. But when it comes to support, it's a matter of cost. VMware offers different levels of support, and the enterprise level of support is quite expensive.

If you're looking for a higher level of support, then it comes with a cost.

When I started working with vROps three years ago, the company mostly used vROps. When I joined, I started with the vRealize Suite. And they have different types of monitors. For example, there are different tools for different monitoring purposes. Like, for security, they'll have different tools for log monitoring.

We use vRealize Operations. We use vRealize Automation (vRA). We use VMware Cloud Foundation. That's vCS. And then, we have been using vRealize Network Insight. Then, we have been using Cisco Insight or Cisco FlashStack. These are the few software that I've been working on in the last twelve months. So, different teams will have different tools which are being used.

The initial setup is quite easy and straightforward.  The majority of the time, implementing vROps is not time-consuming. 

However, if you are migrating from one vROps version to another, you may need to take care of a few things, such as downloading the new configuration and other necessary changes. But overall,  vROps implementation is pretty simple.

So, besides the license overall, you have to pay for the type of support you want. With the license, there is a support cost as well.

Typically, people don't just purchase vROps individually. It's usually part of a larger suite, like the vRealize Suite, which is expensive. So, the suite includes vROps along with other software. 

If a company purchases vCloud Foundation (vCF) or vRealize Suite, vROps comes with it. vCF and the vRealize Suite have been acquired or purchased by large customers who have the financial resources to support the licensing costs. 

For example, I've seen many banking sectors using vROps when they purchase vCS. Recently, I worked on a design for a major European bank, and they were using the entire suite. 

So, no one really goes for the individual product because its value is significantly higher when it's part of the suite. So, there are many customers who use it, but the number of people who use it within a team depends on the company. For example, service-based companies that support multiple customers may have different needs based on the number of customers they support. They may train or onboard more resources to use vROps, depending on their requirements.

The main reason my company goes with VCS is that they already have a current VMware setup. When people go with the VCS suite itself, suppose you have a VMware virtualized network and VMware workloads running on one platform. 

For the network, you may be using different switches, and for storage, you may be using different SANs. So, with this approach, you have to pay different vendors because you're not relying on the same vendor for everything. 

And whenever something goes wrong, you have to open different tickets, which can be costly and time-consuming. So, people go for VCS mostly because they are getting everything in one single setup.

VMware has your networking, your virtualization, vSAN storage, vRealize Automation for automating workloads, vROps for monitoring, and VRNI for monitoring specific networks. So, it comes as a bundle, and it's pretty easy for companies to know that if they buy everything from the same vendor, it streamlines their processes. 

It also leads to operational efficiency because they are dealing with one vendor. And then, when you have two different products bundled in a suite from the same vendor, compatibility is never an issue. That's one of the main things. Because if you have different vendors and products, there is always uncertainty about whether upgrading one product will be compatible with another product from a different vendor. 

And if we look at what VMware has done recently, every year they have validated design guides. So, through that, we'll have everything within that guide, which one is compatible with which, which doesn't work with which, and if there are any limitations with any releases. So, we get everything in one suite. 

So, that's the reason most people go with them because they can foresee their future development in terms of hardware, in terms of their workload, or in terms of their business.

First of all, I would always suggest you go for vROps initially and always go for a temporary trial license. That way, you can check your VMware or any workload stuff you have, how your trial license works, and how it works with your production environment. If you have any workloads that you're going to manage through vROps, always go for a trial license first. Don't straight away go with the production license.

Also, always try to use different workloads, different metrics, and different configurations. This is because it also depends on the specific data center you have and the different products you're using. Ensure you are trying to integrate or get the alert generated for most of the products you are trying to integrate with vROps. A POC (Proof of Concept) kind of thing is always required before you go for the production license.

During the trial period, you can see how your dashboard looks, how the alert system is working, if it's not working, and if it's really meeting your security considerations as well. So, these are the things before you fully decide to go for the production license. Always take a trial license integrated with your current setup, which you have appliances and tests on, before you even decide to go ahead with it.

Overall, I would rate the solution an eight out of ten. The reason is that there are many new advancements coming into the market that are AI-enabled. VMware really needs to do more when it comes to preventing alerts. For example, many security tools use algorithms to detect alerts and give you a whole scenario of the reports that show how you can prevent this action from repeating again. These are a few things they absolutely need to work on more.

Also, security has been a boom for companies in the last few years, and considering how important security is, there have been a lot of tools that do the rating. So, it is more integration-friendly if the current tool can be used for any integrations in any environment, which is something VMware is not yet that efficient at. But I would still give it an eight because most of the workloads currently being used are virtualized ones, VMware workloads. For them, it's perfect.

We use the application for capacity analysis and incident or threat analysis. We can fetch out reports and troubleshoot any incidents using it.

The application's capacity analysis feature gives complete insights into how many computing resources we may need soon. It helps us to procure the hardware accordingly.

The UI interface of the application has been stagnant for a long time. It could be improved to provide a good experience for the users.

We have been using the application for ten years.

After the implementation, I never had any issues with the platform's stability.

It is a scalable platform. It has become more user-friendly and supports a broader environment than previous versions. In my earlier experience, I had installed 4000 to 6000 virtual machines and those many hosts.

Along with the product, I am using Log Insight from VMware. Also, I have used SRM in the past.

I have been using different versions of the tool for a long time. Thus, the initial setup process was relatively easy and error-free. It is deployed both on-premise and on the cloud. It took a couple of hours to configure all the prerequisites.

It is a cloud-friendly application. Compared to other platforms, it is more stable, scalable, and easy to configure and deploy.

I rate it a nine out of ten, leaving one mark for more improvements or enhancements.

We were using VMware vRealize Operations (vROps) for analyzing virtual machines and using it by host. We didn't use the solution for costing or optimization around costing. We used it predominantly for troubleshooting.

What I like most about VMware vRealize Operations (vROps) is how it integrates into the vCenter. You'll get a similar hierarchical view of your host, your VMs, your resource pools, etc. I also like the granularity, particularly the fact that you could go pretty deep into the metrics and data retention as well. You could go far back several months to try and plot performance trends, eventually leading up to an issue or post-incident management.

I also like the plugins in VMware vRealize Operations (vROps). I find the plugins good, especially because you could plug those into Dell. For example, there was a way to visualize how your Dell infrastructure is performing. You could build dashboards, even custom dashboards for your operational teams. You could take a look at what was going on and also look into people doing incident management, troubleshooting, etc. You could customize your experience with VMware vRealize Operations (vROps), and I found that good as well.

I also like the UI of VMware vRealize Operations (vROps) because it's nice and very, very fresh.

In terms of what could be improved or added to VMware vRealize Operations (vROps), from my experience, it needs more work in the ITSM space because my company never used it as an IT service management tool.

I've used VMware vRealize Operations (vROps) for about three years, and I've used it for the past twelve months.

VMware vRealize Operations (vROps) is a stable solution. My company didn't have any issues with it in terms of outages, or severity in terms of the issue. From time to time, the solution would act up, but that was down to underlying issues on from my company's side, not from the VMware side. Overall, it's a stable product.

In terms of scaling VMware vRealize Operations (vROps), it's challenging, especially with all of the data you're putting into the solution, so you do need a lot of infrastructure to sustain a pretty big VMware estate, especially if you're looking at the tens of thousands of virtual machines sending data.

Scalability could still be improved in some ways, or you need to think about how to reduce the amount of data that gets sent to VMware vRealize Operations (vROps) that you don't necessarily need or use.

The technical support for VMware vRealize Operations (vROps), or VMware in general, has been good from my experience. Usually the response time is good. The team gets back to you within a reasonable time frame. The technical support team always asks for logs before carrying out an investigation. Sometimes, you want to expedite solutions to your issues or to get somebody on an issue fairly quickly, but you still have to collect logs, zip those up, and then send those to VMware, and that can take time.

I can't remember exactly, but there was a way to send in logs ahead of time to a VMware engineer through VMware Skyline, so the engineer wouldn't need to collect logs as a pre-requisite before starting the investigations. Other than the log expectation, VMware has good support overall.

The setup for VMware vRealize Operations (vROps) was easy. After getting used to it, setting it up was easy enough. It also became easy to navigate and use. How the solution was set up was that it was connected to the vCenter, then the adapters were set up, then you get the data to synchronize across that, and that's okay.

In terms of the pricing for VMware vRealize Operations (vROps), I can't remember exactly how much it costs, but it was included in the VMware vSphere enterprise plus licensing package my company paid for.

I've mostly used VMware vRealize Operations (vROps).

My rating for VMware vRealize Operations (vROps) is seven out of ten.

My advice to others who want to start using VMware vRealize Operations (vROps) is to use its full capability. It doesn't just do analytics and cost optimizations. It can do a whole lot more. You should use it in depth and try to integrate it into other IT processes. For example, my company only used a third of the full capability of VMware vRealize Operations (vROps) over the time I was on the team. I would recommend it to anyone, specifically to explore what it can do and then work out how it can benefit you. People should also pay attention to scale as well, because the bigger your estate, the more instances you will need to sustain that scale. Just pay attention to upgrading VMware vRealize Operations (vROps) as well because that's also a journey to upgrade instances, in particular maintenance and lifecycle management.

My previous company had a partnership with VMware. It had an enterprise license agreement, which means it was getting different services and different products from VMware.

This solution is mainly used for the orchestration of servers and for obtaining reports such as utilization reports or load reports.

In decision making, it is very useful to have a nice dashboard. We have also integrated with QlikView, which is an analytic tool.

vRealize has a very nice dashboard.

It integrates well with other products such as those from Oracle.

It would be good to have more detailed reports and more details on the dashboard.

I've been using it for five years.

It is a very stable product.

It is scalable as well. Our system administrators and data center administrators use this product.

VMware provides 24/7 online support, and I would give them a ten out of ten.

Positive

The initial setup is very easy because VMware provides 24/7 online support to us. Everything is much easier for us, because of their support.

The deployment took about one to two days. You would need one or two people, such as IT managers, for deployment and maintenance.

We used a third party team for the deployment.

We have licenses on a three year basis. Licensing costs are much higher, but given the stability of the solution, it is a reasonable price.

It's a stable product and is recognized worldwide. It is much more expensive than other products, but it is stable. Therefore, I would rate it at eight on a scale from one to ten.

We use this product for monitoring, to verify what is and isn't broken within the cloud environment.

The monitoring and verification functionalities were the most useful features.

I was pleasantly surprised that vROps has a plugin for Kubernetes, so it works quite well with that, which was useful for one of our customers.   

The solution also works very well with VMware, but not so well with Hyper-V, and compatibility with KVM was very poor. It also didn't have certain abilities that we liked, like being able to run in a bare-metal environment. 

Monitoring is useful but if the solution can't automate or function without my input, it's a waste of my time. That's where I found out there are some issues with this product, there are elements that are not as intuitive as they could or should be. 
My problem is that I think it stays static too long, it doesn't continue to look at the changes.
I would like to see better remediation, automation, and better connection with specific security pieces. I'm not talking about firewalls. Firewalls are beginning to lose favor in a lot of the environments that I deal with. I need products that give me a zero-trust architecture, and this solution still doesn't provide that. 

We have been using the solution for a little over six years. 

We didn't really have any issues with the stability once we got used to the way changes are rolled out. We had to add security, as the security of the solution isn't sufficient for our needs. 

I think it scales fairly well. We were able to run it around the world which helped tremendously.

The quality of the customer support varied. Sometimes we would get junior staff and our own team knew more about the solution than them. Then we would get escalated and connected with someone who really knew what they were talking about, and they were very good.

The initial setup has gotten a lot better over time. The last one we did, we were able to talk to Google, Azure, and AWS altogether.
Cloud foundation software helped a lot during setup with remediation, prevention, and troubleshooting. It had not always been that way.

I would say vROps gives us 30% faster throughput, faster return on investment or better return on investment, so I consider it a good investment. It's at least 30% if not more, so I'm positive about that.

I would give the solution a three out of five, with one being cheap and five being expensive. There are some elements of the pricing that are good, and some areas where I feel like I'm being charged for something the product can't provide yet.

I would rate this solution a seven out of ten.

If you're going to go full VMware, then the compatibility is there. If you're going to have multiple, different versions of systems, then you could run into some issues. There are other products out there depending on the size of your environment.
We were at the top. We were originally using AWS, which I still don't like because they charge you for everything. I used the multi-cloud and that caused some issues. We carry out a lot of testing, so we look at how well the solution performs with Google, Azure, and AWS. It seems to work better in AWS than most other providers, the problem was that I was trying to make it work with so many different versions.

We use this product for monitoring, resource management, and troubleshooting of our virtualized environments. We have been using Heavy Hitter VM dashboards for oversized and undersized VMs. We use vROps to find the contention in the CPU, RAM, and storage. We evaluate the IOPS and throughput of our storage connectivity with our storage back-end. We receive some alerts about some misconfigurations. Mostly, we are using vROps for two main purposes: monitoring and resource management.

In my current organization, we have two nodes; a master node and an HA node. So, we have two nodes of vROps working in vCenter.

We had an incident where a service owner reported to us that there was a slowness. The services on that VM were not running smoothly and clients were having problems. We moved to vROps and used it to understand the contention and congestion in the CPU, RAM, and storage usage. In the end, based on the metrics that were provided by vROps and the datastore at the VM level, we understood that there was a latency in the usage. Based on the recommendations that vROps gave us at that time, we moved our VM into a much faster datastore and were able to solve that problem.

We have been using vROps for the DRS of our clusters. We send metrics that allow analysis provided by vROps to vCenter to better manage and schedule the DRS operations. So, it has really helped us in that particular field.

It has helped us to better manage our resources. Especially right now as we are in the nick of resources, it has really helped us to find oversized VMs and better manage the resources.

I love the resource management and ability to find oversized and undersized VMs. 

The dashboards are really good. They give you a glimpse of what is really going on in your virtualized environment. The ability to create customized dashboards based on your needs is also great. 

The Troubleshooting Workbench, which is for deeper troubleshooting and understanding of your virtualized environment, is really good. We have been using it to monitor vSAN.

The forecast feature of vROps is really good. By understanding the forecast, we can possibly mitigate some challenges and the threat of running out of resources, then having downtime or a disaster. 

VMware has added more default dashboards, which are really good, intuitive, and informational.

We have been able to find the density in multiple layers, e.g., the storage layer and the computational layer. The resource management of finding those bottlenecks as well as oversized and undersized VMs has helped us with managing resources better and improving the overall performance of our data center.

The problem with vROps is that I personally didn't find a lot of knowledge base resources on the Internet. This is a very comprehensive and complicated product. In order to be able to use it, I expected them to have more resources and documents on the VMware website. Or, as an example, they have books available for other products, like vCenter and vSphere. We don't have that level of information available for vROps. It would be great to have a better, deeper, and more comprehensive knowledge base for vROps or even have some resources for learning.

vROps has a hypervisor level of monitoring going on in our data center. We are using other products, like SolarWinds, to have a service and OS-level of monitoring. Because we are using two solutions simultaneously for different levels of monitoring, it would be really nice in the future to have a service monitoring or OS-level of monitoring in vROps, e.g., adding the support online for monitoring services, like Linux services, Linux Databases, and Linux servers as well as Microsoft Exchange Server, Microsoft Active Directory, or other Microsoft services, since we use them a lot. It would definitely help us in the future if vROps implemented this feature.

We have integrated vRealize Log Insight with vROps. We received logs from vRealize for the VMs and ESXi hosts inside the dashboard of vROps, and it was good. However, there was a problem with that. It worked at first for two or three months. Then, I think there was a problem with the certificate of vRealize Log Insight. We haven't had a lot of time to troubleshoot this problem.

I have been using vROps for a year.

There is a team of multiple people at my company working with vROps.

In the nine months that we have been using it at my current company, we haven't faced any sort of problems in regard to crashes, the integrity of the data, or dashboards not showing. We don't have any problems like that. It is really stable.

We don't have any plans to scale this out. If there is a new feature or service implemented in vROps for future versions that VMware will publish, we might jump onto that. Right now, we don't have any plans to extend and increase the scalability of our vROps solution.

We have a team of five people who work with vROps. We have almost 1,500 VMs as well as 70 to 80 physical/ESXi servers. 

A user would have read-only access.

A colleague and I do the maintenance for vROps, e.g., troubleshooting, customizing it, or building a dashboard.

We have not used the technical support because we haven't faced complicated or problematic kinds of issues. We have been using the online documentation, which has helped us a lot.

My current company was using Veeam ONE. After implementing vROps, the company decided not to use Veeam ONE anymore because vROps was more extensive and comprehensive when it comes to monitoring.

The initial setup was straightforward at my previous company. We downloaded the OVF, then implemented the integration with vCenter and other products, such as vRealize Log Insight, and that was really straightforward. 

I personally didn't face any problems. The tricky part is there are two ways of implementing vROps. The first way is using vCenter. There is a part of vCenter where you can specify, "I want to implement this in vROps." If you go that way, it will be a little different than implementing the OVF yourself, then going through the wizard and using the VMware documentation.

Once, when I had a problem with vCenter, I went to vCenter, and I said, "Okay, I want to implement vROps." The problem was that vCenter and vROps were not integrating. The usernames and passwords were not synced, so I couldn't log into vROps. However, that was the only problem. Later on, I switched to implementing the OVF directly. In that way, the problem was solved. Generally, the implementation was straightforward and the VMware documentation, for this part, was good.

It took an hour or two to implement one node and integrate it with vCenter. It was just a simple implementation for vROps without customizations. 

Our implementation strategy: We wanted to test this feature. At first, we wanted to make sure that we needed this product. We then went into a testing and researching phase. We implemented it because we found it really useful. Then, we began customizing it, making sure that the dashboards and everything else worked best for us.

I did the implementation at my previous company. I personally went through the implementation step, then I used VMware and other resources on the Internet to implement the service.

I have worked with this product at two companies. At the first one, I used to implement it, then I moved to another company. In that company, we had vROps implemented and installed. We are using it for monitoring and resource management purposes. In the first company, I implemented it, and in the second company, I have just been a user.

We have definitely seen ROI by removing unnecessary servers and VMs. By having vROps as an assistant when it comes to monitoring and managing resources, it has helped us a lot with cost savings and managing expenses.

On multiple occasions, we were having slow performance, performance issues, or resource management issues. vROps has really helped us to understand the problems or issues much faster. It has improved our performance for finding these type of problems and mitigating them by about 50%,

The solution's capacity allocation and management has helped us save on hardware costs by 25% to 50%. We have also saved on power and other data centers by 15% to 20%.

By using vROps, we have found resources and VMs that were not damaged and in use. We have been able to reclaim those resources. When it comes to licensing, it has helped us save about 15%.

If you have a large-scale enterprise environment with hundreds of servers and thousands of VMs, it will definitely help you a lot when managing your resources.

I have been told that the company tried SolarWinds Virtualization Manager. While they tried SolarWinds, the winner was vROps in the end because the level of integration, comprehensiveness, and extensive data provided by vROps was much better than SolarWinds and Veeam ONE.

At first, vROps might be really intimidating due to the amount of information that you get. from vROps. You might say, "Okay, this is so huge, big, and complicated." However, after using vROps for a couple of weeks, you will understand the value of this product much better. I think a lot of people might jump into the UI, then its level of complication and complexity, they would say, "SolarWinds or Veeam ONE is a better solution because it is really simple." I would say to them, "Challenge yourself with it. Involve and engage yourself to work with the UI. After a couple of weeks, you will understand that vROps is definitely the best choice when it comes to monitoring VMware solutions."

If you have an enterprise-level environment or work in a large-scale data center, I would definitely recommend using vROps. It helps a lot with resource management as well as understanding the congestion and bottlenecks of virtualized environments. It is the number one solution for monitoring virtualized environments, especially if you are using VMware.

Generally, it is a very comprehensive, good product.

The user-friendliness of the UI is really good. It is better every year. I haven't used a previous version of vROps. I have only used version 8. I saw some screenshots of the UI before, and this version is much better. 

With the integration with vRealize Log Insight, we were able to view logs in one dashboard. So, we were not going back and forth to vRealize Log Insight. It improved the performance and efficiency of personnel, like myself, to better troubleshoot problems.

Right now, we don't have any performance issues, especially with the help of vROps. We have more of a lack of resources for future projects.

In the future, we might use the vendor’s Tanzu solution along with vROps for Kubernetes monitoring or management.

I would give vROps a nine out of 10.

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.