VMware Aria Operations Reviews

The most valuable features of the solution are the effectiveness of hardware availability and flexibility.

The deployment of the solution can be improved by making it less complex.

The licensing cost is high and needs to be reduced.

I have been using the solution for 20 years.

VMware Aria Operations is a great product that is very stable.

The solution is scalable and we currently have 800 people using VMware Aria Operations.

I previously used other solutions and switched to VMware Aria Operations because of its functionality.

The initial setup of this solution is complex and takes a couple of weeks to deploy in our environment. We require six administrators for the deployment and maintenance.

The implementation was completed through a vendor.

The solution requires an annual license which is very expensive.

Before choosing VMware Aria Operations I evaluated other solutions. 

I give the solution an eight out of ten.

I would recommend the solution to others.

We use this solution solely for reporting purposes.

We appreciate that this solution gives accurate reporting.

We would like the default views on the reports for this solution to be improved; at present we have to customize the view before use.

We would also like the option for this solution to be cloud operated.

We have been using this solution for just over one year.

We have found this to be a stable solution.

To our knowledge, this is a scalable product.

The initial setup of this solution was easy.

I would rate this solution a seven out of ten.

We use it for data center virtualization and management.

I like the fact that the performance is good and that it makes it easy to consolidate all your servers.

If the cost of the license could be cheaper, it would be good.

We have been dealing with this solution for about three years now.

VMware vRealize Operations (vROps) is stable.

It is a scalable solution. We have two clients who are using the product.

The technical support is very good. They get it sorted within the SLA.

The initial setup is straightforward. It took about two weeks to deploy it.

We had a team of one or two engineers for the implementation process.

Our customers who have used it have definitely seen an ROI. Instead of using so many physical servers to achieve the same thing, they've reduced it to five physical servers, and they are able to do much more with those five servers.

The licensing model is annual. Compared to the price of other products, VMware vRealize Operations (vROps) is a bit on the high side. If it could be cheaper, it would be good.

I would absolutely recommend the product and would give it an eight out of ten.

The most valuable features of VMware vRealize Operations (vROps) are capacity and performance management.

VMware vRealize Operations (vROps) can improve the Layer 3 hypervisor VM infrastructure because we do not manage other applications. We need a package, which is too expensive. We would like to manage native VMware applications, VMware native components, hypervisor, and storage, such as vSAN.

I have been using VMware vRealize Operations (vROps) for approximately two years.

The stability of VMware vRealize Operations (vROps) could improve. It can help us to build a dashboard report on a job, but it seems very slow to produce or deliver the dashboards. We are tunning it to make it go fast.

The support provided by VMware vRealize Operations (vROps) is average.

The initial setup of VMware vRealize Operations (vROps) was very minimal.

We are experts and we install VMware vRealize Operations (vROps) on a host, and we import an appliance, such as OVA, and we deploy it.

We have a team of four people that does the maintenance and support of the solution.

I would advise others that VMware vRealize Operations (vROps) is a good tool to manage VMware application components, for sending storage on RPMs. For example, if we have a basic hypervisor or storage based on VMware files, such as VMFS. It is a great tool for that.

I rate VMware vRealize Operations (vROps) a nine out of ten.

There is a newer version available which will have better features.

I was previously working remotely and using vRealize Operations in a virtual environment. Now I'm working in person, so we use vROps to monitor our critical systems. We didn't use all of the product's features. We mainly use vROps for monitoring and automation. In addition to my team, the 20-person management team also monitors this environment, so it's about 30 people in total.

Mainly we are working on the vSphere monitoring, orchestration, and automation.

We are trying to consolidate our data centers, so the monitoring could always be improved. VMware could improve the way VROps forwards critical alerts to Microsoft Teams. I can't give feedback about anything else because we are not using all the features. 

We haven't had any issues with vROps. 

I think vROps is scalable and suitable for our environment.

VMware technical support is good. 

I also work with ControlUp when our customers need a specific metric. We only use ControlUp for that single feature. 

The initial setup isn't complex.

I rate VMware VROps nine out of 10. It's an excellent product for monitoring a VMware virtual environment.

We can monitor all of our relevant hosts that are stored from the same single pane of glass. We use it for daily routine operations.

The scalability options are quite good with VMware vRealize Operations (vROps), and all of the features are useful and relevant to us.

If this tool can integrate with other products, for example, those that monitor the network devices or any other storage devices, it will be very beneficial.

I have more than eight years of experience with this solution.

I am absolutely satisfied with the stability of the solution.

With regard to scalability, when you deploy it you are given different categories. You can deploy it in a tiny environment or a small, large, or enterprise level environment. You have the option to deploy it in different levels so that it fits the database accordingly.

We have a system team of around four to five employees who use this solution.

The technical support from VMware is very good. We have been using this product for more than five years now, and their support is very good. We are pretty satisfied with it.

The initial setup is easy, and it can be deployed by a single person. It's not a very difficult tool. It's a pre-configured appliance provided by VMware, and you just deploy it in your existing VMware cluster and assign the license. You can have it deployed in your environment in two to three hours or four hours at the most.

To maintain the solution, you will need two people at most.

It is a very good investment because in the long run, it's all about the uptime. As far as we are concerned, it has given us that 100% of the time. We are very satisfied with the product.

The license is a one time cost, and you pay for support on a yearly basis. It is a bit expensive, but if you consider the product support and its reliability, it's justifiable.

It is a very comprehensive tool, and it gives you detailed information. I would rate it at eight on a scale from one to ten.

It was helpful in identifying the CPU, memory, and space utilization, which was very much important for us. We needed alerts when the utilization increased a lot, and we were able to inform the customers that we have a particular problem that could be the root cause of the problems that they might face later. They were then able to take some preventative measures in advance, which reduced a lot of problems.

It was very useful for regular monitoring, disk utilization information, and root cause analysis. It was also helpful in identifying why a specific issue is happening or why an error is occurring. 

It enabled us to be more proactive in anticipating and solving problems. We could know beforehand about the machines that might be at risk for high utilization. 

Alerts and monitoring were most valuable. It was also pretty user-friendly and interactive. I was able to generate good reports in PDF and HTML formats, which was really helpful.

The visibility that it provided for our infrastructure was pretty good. The snapshots were also useful.

vROps did a lot of monitoring, but in one case, we had to use Log Insight instead of vROps because vROps was not able to install the agent to enable us to have multi-monitoring. I don't exactly remember the case, but it involved monitoring all applications.

It wasn't exactly proactive. It was supposed to, but there were a lot of delays. It could also be because of our infrastructure and the way our network was set up. If vROps could be more proactive, that would be nice. It is nice to have the information beforehand, but when there is downtime, it takes a lot of time for us to be able to see an issue in real-time, which becomes a bit challenging. If there is a way to improve the data collection for the whole vCenter that would be nice because data collection takes a lot of time.

I used VMware for around five years, from 2015 till January 2021. Except for vCloud Director, I've used most VMware products such as vSphere client, Log Insight, and vRealize Automation.

It was pretty stable. I didn't find many errors while deploying the application and after the deployment.

Our environment didn't scale much, so I cannot comment on its scalability.

We had four vCenters. One was in Santa Clara, US. One was in Beijing, China. One was in Manheim, Europe, and one was in Singapore. We also had test centers, and we integrated vROps for testing there. We had one in King of Prussia and one in Switzerland. So, majorly, we had four vCenters for the production environment, and these vCenters worked with around 4,000 virtual machines.

I have not used VMware's support for vROps.

This was the first tool that we tried to deploy for monitoring.

I was involved in the initial setup of vROps. It was pretty straightforward. Most of the VMware products are pretty straightforward to install.

In terms of the implementation strategy, we have always followed the documentation provided by VMware.

We tried to evaluate many solutions, such as Prometheus, Dynatrace, Nagios, and PRTG. It was best for us to go with vROps because it is a VMware product, and it integrates best with VMware vCenter.

I would recommend vROps for an Enterprise environment. Based on my experience, it is a great tool to work with. Rather than having a big vCenter and then installing vROps, it is good to have it when you're starting with a vCenter. That's because data collection takes time, and it would become an overhead for vROps. In such a case, you might need a load balancer and multiple vROps. So, I would recommend having a vROps when you start building a vCenter. It will really help in scaling up the environment, and you'll also know if you'll need to replicate vROps or not.

We didn't use it for workload placement because we didn't have the load balancer for that. It didn't help much in decreasing the overall downtime, and it also didn't affect our operations when it comes to overall downtime due to performance issues.

I would rate vROps an eight out of 10.

We operate a test lab and we do virtual and physical testing for various clients.

We frequently build out a test sweep that looks like the client's environment and then runs the tests on that. We particularly do it with upgrades and things of that nature. 

vROps is used to do performance measurements. It's in conjunction with two other products. One of them is called vRealize Log Insight and the other one is called vRealize Network Insight. That gives us a reasonably good profile of the performance in one of the systems under test.

Our business is built around testing, measurement, and performance measurement and vROps is the primary tool. We use it in a VMware environment and we do tests in other environments. But in the VMware environment, vROps and the associated products, Log Insight and Network Insight are the primary tools that we use. It's a basic tool. It's very important for our organization. 

vROps provides proactive monitoring up to a point. There are limitations on its visibility. We often use it in conjunction with an operating system-specific monitoring tool. vROps provides not bad visibility into operating systems such as Windows and Linux, but if you want to track down problems in those, you're probably looking for something that runs inside the operating system. vROps is very important for the availability of the test lab.

Surprisingly enough, VMs take much fewer resources than most people think. vROps has enabled us to run 30% to 50% higher in terms of density. A lot of the work that we do is testing workloads, so the process is basically setting up a workload, guessing what the infrastructure's support that workload is, driving a test workload into it, and then manipulating the infrastructure until it begins to break or slow down. vROps provides the monitoring that tells us when those breaks occur, primarily at the hypervisor level.

vROps has enabled us to replace multiple tools. The performance measurement suite from VMware is three basic tools, vROps, Log Insight, and Network Insight. We use that cluster of tools in preference to things like Splunk and various other tools that are out there. It's a core tool for what we do. It is our measurement instrumentation tool, so it's critical to what we do.

In engagements with clients, we will often use vRealize for operational monitoring and that sort of thing. But our facility is primarily a test lab, so we use it for profiling and performance measurement.

For people who know it, vROps is quite user-friendly. It takes a little while to come to grips with it because it has a reasonably complex interface. The newer ones have gotten better in terms of being able to declutter the interface, but even so, there's a lot on the page, particularly in a reasonably sized infrastructure.

We've only just started experimenting with Tanzu to learn how to use monitoring and management. I have worked with Tanzu with a client who's in the process of post-deployment work. But I haven't used vROps specifically with Tanzu.

vROps enabled us to be more proactive in anticipating and solving problems. This has decreased our mean time to resolution by 40% to 60%. 

It's not a huge concern of ours but vROps' workload placement increased VM density.

We integrated vROps with vRealize Log Insight. It provides alerts, correlates metrics, and checks logs across all of the components of our infrastructure. When you're doing this, you get a slew of performance information that comes up in real-time on the vROps console and interface. Much of it comes through logs and Log Insight processes that are in the background and then push back the results from the log processing up to the vROps dashboard. It identifies issues that are showing up in the logs. The integration is very useful to the testing process.

vROps and Log Insight provide us the instrumentation that allows us to identify problems and issues and look at possible solutions.

Deployment is still a little bit of a nuisance but you only do that once. 

If I put on the hat of a client, I would say cost needs improvement. For clients with reasonable-sized infrastructure farms, you're looking at licensing at either per socket or per VM, and if you have an installation of any size, you're doing it per socket, and the per-socket licensing is a little heavy. Per VM license, if they have large numbers of VM, it is just not practical.

I have been using vROps for six years.

We found it to be very stable. 

Keeping in mind that we're a pretty small operation, scalability is not an issue for us. In larger data centers, my experience has been that it scales very well.

In terms of users, there's one person who works probably 50% of his time and 40% of his time as an administrator. We have people who run tests who are test managers of specialists and measurement specialists in testing and so on. Because we're not a production data center, it's not an army of people sitting in the other room, running this. It tends to be a small number of people that move around to various different roles. 

Half of an employee's time is needed for maintenance. 

Because we're a testing unit, the workload that we have in terms of testing will expand with the business. Generally, we run it on around three or four platforms at any given time.

We'll expand usage as our business expands, as we have more requirements, but we don't have a plan that says two months from now, we're going to add some more.

We didn't contact technical support for vROps. When we contacted support for other solutions, they generally provided reasonably good support. They tend to stick with the problem until it gets sorted out, and usually, they're good at identifying what information they need and how to get it to them. Working with them is reasonably good.

We've done the setup a number of times, so from our standpoint, it was pretty straightforward. But for someone just starting out, you really have to spend a lot of time with the documentation and understand the various configuration parameters and how they affect the operation of it. The setup is reasonably complex for a client.

Overall, the quality of VMware's documentation tends to be fairly dreadful. And so, you do a lot of searching around and bouncing back and forth. One of the biggest improvements they could make would be to actually use illustrations in the document so that there is a straightforward way to understand what the documentation is trying to tell you. It's very verbose. Trying to relate what's in the documentation to what's in front of you doesn't always go well. Documentation doesn't seem to move as quickly as the interfaces.

We're certainly not a large data center by any sense of the word. We have about 20 hosts. If we were to do it starting from scratch and moving up, the setup would take about two weeks.

It takes two to three hours per host but there's a lot of carry-on between the time you spend working on the hosts. There's preparation and various other things. Overall, it takes around one to two hours per host.

When we started, we installed vROps, linked it to vCenter, picked a group of hosts, and set up monitoring on that group of hosts and on the VMs in that group of hosts. We worked out all of the kinks from the configuration and setup. Then from there, we just rolled it out to the rest of the hosts and set it up so that at the beginning of a test, we can deploy what we need for a given host. It's not just vROps, but it's also the support things that need to be in place for us to quickly turn around a testing environment.

Most clients see a good return on investment in reduced staff time, they get early warnings about problems that are coming along, reduced time to diagnose and come up with solutions to problems. In my mind, looking at our clients, the people who use it in production operations, there is a return on investment. It depends on the size of the organization and that sort of thing, but typically, I would say you get a 1.5:1 return on investment and perhaps a bit more. It's very client-specific. This is associated specifically with the testing work we do with VMware installations. We do work with other installations that use Microsoft and various other things, vROps is interesting, but not really that useful. There are better tools for those other environments.

There are no additional costs to standard licensing. There's time, material, staff cost, but they are not out of line or unusual.

To really use vROps effectively, you have to have three of VMware's tools. vROps, Log Insight and Network Insight. I'm not sure that would apply to every customer, but certainly would for the kind of work that we do. In a sense, the additional costs are those additional products.

When it comes to efficient workload placement, vROps works with vCenter for workload placement, and vCenter carries most of the burden for that, so I'm not sure that's something that vROps itself does.

If you're running an evaluation or testing on VMware environments, vROps is really the only tool that makes sense.

My advice would be to find a specialist. 

vROps will point you to where to look for the problem. When you actually dig into doing diagnosis and so on, you really need a good log processing facility to be able to dig through the logs and identify where the problems have arisen. vROps will notify you of a problem and will point you to where the location is. But to get down and identify the problems, you really need the log processing part.

Against other products, I'd rate vROps a nine out of ten. 

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 vROps as a monitoring solution because it is good at that. It is designed to monitor VMware data centers. 

I am using AWS and Azure. I prefer AWS, but it depends on the budget of the company as well. Having customers in the cloud is cheaper than on-premises, but it is completely different.

Many of the features in this solution have helped out and improved my customer's organizations, such as creating, monitoring, splitting, modifying, playing with the VLRs and alarm definitions, notifications, performance analysis, cost analysis, and cost-calculations report comparisons.

Improves performance for the CPU. Helps us develop a future plan.

The VMware data center has helped us be more proactive in anticipating and solving problems by splitting the production servers. I can combine it with other solutions, like Horizons Cloud. This helps in general.

vRealize Log Insight has affected our overall troubleshooting by allowing us to have a single point to check everything. For example, when I was using Dell EMC RecoveryPoint for virtual machines, which is protection software, they had a single dashboard inside the vCenter in order to check the overall information on the dashboard, such as storage. Previously, I would need to connect to vCenter to check every single log or if there was an alert. With this solution, I do not need to connect to the dashboard or vCenter. By using the UI of vRealize, I can connect independently from my home computer with no need to access vCenter. I have a single dashboard where I can check everything I need, such as alerts, emails, any critical situation, or Log Insight, all from one single place.

The most favorable features of the solution are it has a good design, is easy to use, and can be used for a large variety of solutions. You are able to combine it with many tools and solutions, such as LDAP, Active Directory, and automation solutions.

The UI is user-friendly and easy to use. For example, with a colleague that has just started in the IT field, I can easily explain how to use this solution. It is very intuitive. It has graphics and a lot of details. When comparing it to other vendor monitoring tools. It is much simpler to manage, configure, automate, and do reporting.

It is useful for performance monitoring, alert monitoring, and capacity planning. In the latest version, you have the ability to calculate how much you are spending on your infrastructure for every single machine or the final price of one of your virtual machines. Additionally, you can look at the information between on-premises and AWS, then compare the differences.

There is proactive monitoring available. You need to adjust the appropriate settings, accordingly.

The solution can improve by offering more flexible integration with other platforms or products, such as Hyper-V or Azure. Not everyone uses VMware. It would be beneficial to have a more open-source concept for integration, creating more visibility across multiple clouds.

Sometimes, from a normal user's perspective, I feel like I want to get to the main dashboard faster because there are a lot of options to get to the final step. To get to our main dashboard on Windows machines, you need to click about 10 times and change a lot of options. It would be better if they could organize it to be only three to five steps.

I have been using VMware vRealize Operations (vROps) for approximately five years. I apply and implement it in different businesses and companies as a consultant.

I use vROps daily as a user and administrator. I also explain the solution to colleagues.

It is very stable without downtime. They have improved the solution over previous versions. 

I do the daily tasks, like monitoring. Since I am using the version, I haven't had to apply any upgrades, do any migrations to new appliances, or apply remote collectors.

You can scale up by combining all your vCenters and add collectors. It is very flexible.

In the small companies that I work with, there are about 50 users who are using it for monitoring critical solutions, like finance programs, SQL Servers, IIS, NGINX, Data Domain, and Avamar. 

In general, VMware has good technical support. They have top guys.

I have contacted VMware about Dell EMC issues, but they only focus on vROps support.

There is a strong user community with blogs, which is very important. The community is really extensive. A lot of people help you. We share information there.

I have used other solutions previously and it was impossible to get the dashboard from Dell EMC appliances. We found this solution does it perfectly.

I was previously using other tools combined with Windows, such as RVTools. Now, I only use one solution that has an all-inclusive virtual appliance. vROps is always improving, e.g., the UI, and a benefit to our operations. In general, it is a great product.

I have integrated vROps with vRealize Log Insight and vRealize automation. After integrating vRealize, we tried to split and combine the logs from the login sites for more alerts and information to organize the whole infrastructure and have automation. We used many different types of scripts trying to orchestrate them all together into one solution, replacing, for example, Elasticsearch and some other scripts.

The initial setup of the solution is easy. 

The deployment takes less than 20 minutes.

It is easy to deploy the settings. It is not complex at all. You can start all over and organize everything differently.

First, I choose on-premises because I want to feel in first person how difficult or easy the installation or deployment is from other data centers. Also, I combine it with Active Directory as well as VMware Workspace. Even if it is a PoC, I do the installation to production.

I also work with third-parties and providers.

vROps has helped decrease downtime by approximately 35% by giving me a warning when the VMs are down.

We are receiving approximately 75% workload placement efficiency. vROps is good in this case.

By using the cloud solution, it helps save on costs. We did not have to allocate money or resources for what is typically associated with on-premise solutions, such as installations, upgrades, maintenance, and network hardware.

The virtual appliance is not power-intensive. It does not use a lot of CPU, RAM, etc.

It gets better with every version.

The licensing is not clear at the moment if the on-premises pricing is the same as on the cloud. I am checking on the pricing. However, you can save a lot of money with the cloud solution because you need to spend time installing, upgrading, and connecting with the on-premises solution. Also, you don't need to spend time scheduling the maintenance and maintaining the solution when using the cloud version.

I recommend it to colleagues and companies, but people have complained that it is expensive. I think the pricing is fair.

I tested SolarWinds, ManageEngine, and HPE. I was looking for a product to help with monitoring of some special appliances from Dell EMC. I tested different products, and this solution was the only one that helped my customers and me to get the final solution that I was looking for. It is really difficult, practically impossible, to get a monitoring system for these types of Dell EMC physical appliances: Avamar, Data Domain, and RecoverPoint. I tried different products, like Zabbix, Nagios, and PRTG. Whereas, vROps is perfect for this type of job.

Dell EMC doesn't have any idea how to monitor. They offer coding, scripting, APIs, and connecting to vCenter. They don't offer a knowledge base or advice for monitoring problems. I discovered vROps for monitoring their problems.

While open sources are free, you have to spend a lot of time training and explaining to people how to use them.  

I am reading and checking for different solutions all the time.

My advice is to test the product.

I am monitoring VxRail from vROps.

Our average time for resolution depends on the issue. For example, if I receive a notification, and there is a large latency or the hard disk is filling up too fast, it will depend on the end administrator who is monitoring it.

I rate VMware vROps vRealize Operations an eight out of 10.