VMware Aria Operations Reviews

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.

I am working for a public cloud provider and am supporting their infrastructure. The company's cloud is deployed on VMware products. Essentially, it is VMware virtualization infrastructure and they are selling public cloud space.

Customers use the service to have access to a public cloud that is local, in their country. If, for example, they don't want to use AWS or Azure, then they can opt to use this service. In return, they have full control of their data and infrastructure.

We use several products in the VMware suite including ESXi, vCloud Director, NSX, vRealize Operations Manager, vRealize Operation Log Insight, vRealize For Business, and vSAN. The company runs 80% of VMware products.

In terms of user-friendliness, it is very good. The features are good and the interface is easy to understand. All of the commonly used functions are easy to access.

This solution has helped improve our organization because we are a successful local cloud provider and the number of customers that have joined our cloud is increasing. Our customers know that we're running on VMware and we haven't faced any issues yet. Moreover, most of our customers' businesses are doing well. Overall, we have done well with VMware.

We do our daily proactive monitoring using vRealize Operations Manager. It provides us full insight in terms of what is happening in our operations, including the details contained in the logs. VMware vCenter also helps us with proactive monitoring.

Proactive monitoring has helped us to avoid downtime, especially because we follow the best practices described by VMware. When you follow best practices, you won't face many problems. The overall downtime depends more on your support and handling of the product, rather than the software. We are running on a cluster to help avoid downtime.

vROps has helped us to place workloads efficiently, although our users do not have very large workloads. We are running two environments and we are able to handle the users and workloads that we have. 

Using vROps has helped to increase our VM density within our clusters. VMware provides a solution where you can create a cluster, whether for storage or compute, and nodes within the cluster are monitored. If there is a node that goes down then it is automatically kicked out of the cluster. Before the host goes down, vRealize creates a replacement. It has three copies of each disk in different host nodes, and it will automatically trigger one of the copies. This makes sure that the system is fault-tolerant and the VMs won't have any problems. Also, if the Distributed Resource Scheduler (DRS) is turned on, the VMs will balance the resources and try to avoid downtime.

We have been able to replace other apps with vROps because it is, pretty much, doing everything. For example, we had another monitoring tool that was running on each of our nodes. Its job was to trigger alerts and display information. vROps replaced it and is even more powerful. If the network goes down between our office and one of our data centers then it is able to detect that. It will provide you ways to get a deeper understanding of the issues, and it will suggest resolutions. There are other products that vROps has replaced, including solutions for resource planning and load management.

All of our products are integrated with vRealize Log Insight. It integrates with the other components including vCenter and NSX and retrieves all of the logs. From there, logs are stored in the system and when you have problems, you can deep dive and perform a log analysis. You just have to know the keywords you are looking for, which components, and the hostname, or the host IP address. It will report all of the information in the log that is related to it.

Troubleshooting works well with vRealize Log Insight, provided that all of the component drivers are updated and the service packs are all installed and running. When we configure the integration, we have to verify where the logs are coming from. As long as it is set up correctly, troubleshooting will not be a problem.

There are four main components that we use. The first is the hypervisor, EXSi. It is the most important part because this is the virtualization medium. Without it, you cannot set up or deploy your virtualization environment.

The next component is NSX, which allows network virtualizations to provide your tenants with the ability to manage their own network.

We have vSAN for storage virtualization, to create clusters.

We also have a tenant portal, vCloud Director, for self-management, including payment. Tenants are able to control and manage their virtual data center by themselves without the involvement of the service provider.

We have faced one problem when integrating with vRealize Log Insight, where the logs are not collected because the component drivers are not updated. Rather than give us the updated logs, the old ones are retrieved. The integration with vRealize should be more seamless.

One area that needs to be improved is vCloud Director, as it has very weird behavior sometimes. All of the other components are stable and you can predict their behavior. However, with vCloud Director, you can't always predict what it's going to do. For example, there are times when we thought that it was collecting information about the network, compute, and storage resources from vCenter, as well as information about the nodes, but it doesn't always work as expected.

The last time we had a problem with vCloud Director, we were unable to get the snapshot of the VM. From the backend, everything appeared to be running fine. This is an instance when we had to contact VMware support in our time zone, and they were able to help us.

You can find information about some of the problems with vCloud Director in the Knowledge Base articles that include various workarounds. VMware advises that when you face these kinds of problems, contact them to raise a ticket and they will come and fix it. The component is very sensitive.

In the past, when we have raised priority one tickets and they have sent us level one engineers. This wasted time because the L1 was only able to perform the troubleshooting steps that we had already completed.

I have been using VMware for two years.

The agility of the software components is fine and there are no complaints so far from us, so far. In general, the stability is good.

The problem that we faced recently was that we were running out of time for support. We were still running on ESXi 6.5, and support was ending at the beginning of this year. We had to upgrade our infrastructure and we had our hands tied. We could not move forward until the upgrade was complete, so it was a marathon of activity. This included adding two different sites and it required that all of our regular activities were interrupted. Ultimately, however, it worked and everything is now good.

Sometimes, there are issues with stability that arise from the hardware. We are located in Kuala Lumpur and our data center is based in Bangkok, Thailand. Although it has been okay, we have encountered a few power interruptions. We are using HP machines, which are good, but there have been troubles with some of the SSDs. When that happens, because I install the operating systems using a USB, sometimes the drive is misplaced. These are the types of issues that we face more often.

In the case of any downtime with a node, the data center operator is there to quickly overcome and resolve the issue. Once we realize that a node is down, a replacement is automatically started and communicates with the other hosts. This allows us to avoid interruptions in the operation and in the business. Once things are repaired, and the original node is put back into the cluster, everything goes back to normal.

So far, the product has been good and we haven't faced much in terms of complications. Our environment is new and we don't have millions of users, yet. We are still growing. I'm not sure if we'll face multiple problems when we reach one million users or even 500,000 users, but so far, everything is okay. We've managed to handle the workloads, and we've managed to satisfy our customers.

We have more than 100 customers using it and at this point, everything is running smoothly and the number of workloads is okay for our resources. As more customers come, we will increase our resources and expand our usage.

Overall, scalability is very good and it's one of the reasons that I like VMware products.

Our experience has been okay because we have received support for any problems that we have had. Also, we were able to get support from anywhere. It is not only available in our time zone, but we can get support from elsewhere if, for example, we need it overnight. Global support is available from anywhere in the world.

I can say that we have had a few bad experiences, but overall, you cannot take two out of 100 and say it's bad. On the contrary, overall it is good.

I don't know how it works in other time zones, but our time zone is supported by India. I have found that sometimes, you have to push them hard. For example, we have raised a P1 ticket and in response, they sent us an L1 engineer. When a ticket is priority one, it means that the situation is critical and the business is impacted. If you send a Level One engineer in a case like that, it will waste time because they will perform the troubleshooting steps that we have already completed. This has happened to us a couple of times.

VMware is the first solution that I used for virtualization.

VMware has introduced the Server Appliance, which allows you to deploy very quickly. We just need to import the appliance VM and deploy it. Traditionally, we had to create a Windows machine, and there were several things to configure, but they now have their own operating system called Photon OS. It shortens the length of time required for deployment.

The initial setup of vCloud Director is a bit complex. Sometimes when we have a problem with it, we can't fix it. VMware themselves suggest raising a ticket when an issue arises, and they will come in to fix it.

When we first implemented this product, we came up with a plan and submitted it to VMware. The VMware team reviewed it and advised us of the best practices. We developed a set of instructions that includes deployment and updating the solution and re-submitted it to them for review. It was finalized and we follow this plan whenever we deploy it. Whenever we encounter problems, we raise a priority one ticket and they come to help us with the problem.

The first time we deployed this solution, the local VMware team assisted us.

This service has been running for approximately four years and they are making a profit. Otherwise, they would discontinue it. They are planning to expand so there has been a return on investment, although I don't have the exact figures.

We did not evaluate other options before choosing VMware.

We offer a variety of services for our customers including Kubernetes monitoring and management. However, at this time, we do not have any customers who opt for it. What we provide depends on the customer's requirements. If they want to include VMware with their machines, we deploy the tenants. We promote all of the products, including that for Kubernetes monitoring and management, but nobody has yet requested Kubernetes. I expect that because we are promoting them, our users will understand the utility and plan to use them in the future.

VMware updates their product every one or two years, and I think that they are ahead of us in terms of what features are needed. Overall, I think that the product is very good. In the future, we'll have experience with the functionality of all of the new features that VMware is coming out with.

The biggest lesson that I have learned from using this product is that if you want to have a private cloud, VMware is the best option. It is the most stable and the best choice for a private cloud investment.

I am planning to open my own cloud in my country, which will help the local community because many government agencies will not use the public cloud. For this, I'm thinking that I will be using VMware.

I would rate this solution a ten out of ten.

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.

Our private data center has been built on VMware technology. We are using vSAN and we use vROps as a monitoring solution to monitor the full stack, from applications to hardware. That includes the servers and Cisco switches.

The solution is deployed on-premises in our private data center.

It enables us to monitor the full software-defined infrastructure from the app level to the hardware level. This is the main benefit for our organization.

When there is an issue at the disk level in vSAN, vROps gives us an alarm that the issue is happening on particular disks. Other solutions cannot give this type of alert for vCenter. Even vCenter cannot give that type of information. That's what makes this feature valuable for me.

The visibility it provides from apps to infrastructure is very good, compared to other monitoring solutions in the market. We have used other solutions, and we are still using them, but for monitoring your VMware infrastructure, vROps is very good.

vROps is user-friendly, but configuration is a little bit hard. It is also hard if you want to customize it for your data center, especially without VMware training. The user interface should be improved so that a new user can easily configure it for his own use.

I have been using VMware vRealize Operations for the last four years.

The stability is good enough to monitor private and hybrid clouds. Even though we are using very few of the features of vROps, it is very good. It is very useful for a cloud provider that is managing large-scale VMware technology for their cloud. It is good monitoring and operations software for them.

It is highly scalable.

We are already in the middle of a project to increase our infrastructure and we have included vROps in that project.

Customer support is good, but the main problem is that VMware support is very costly compared to other organizations' support. When you purchase a VMware product, such as vSphere or vROps, the license is perpetual, but you also have to purchase the support service for a number of years. The support service pricing is very high compared to the license, and compared to competitive vendors.

Before vROps, we were using SolarWinds NPM. The primary reason we switched was that we were looking for a solution that would give in-depth monitoring capabilities for VMware infrastructure.

The initial deployment of vROps was straightforward. We deployed ESXi, vCenter, and then vSAN. After that, we deployed vROps on-premises to monitor our VMware vSAN cluster. There was nothing special or complex about it.

It took four to five days to deploy vROps.

We have three people who are using and managing vROps and we are monitoring about 500 virtual machines with the solution.

We used a third-party integration partner that is certified by VMware. I felt that they were not well-trained on vROps.

The value we get from vROps is fine, but it would be better if the support cost were lower.

We did not look into other solutions because, at that time, we already had our VMware infrastructure. vROps is the best option for monitoring VMware infrastructure.

If your infrastructure is VMware-based, meaning you are using vSphere, vSAN, and vCenter, and if you are a large-scale cloud service provider, you should consider vROps as your monitoring and operations solution.

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.

I use it for monitoring and capacity planning.

I work with the solution's dashboards to monitor capacity. There are many functions in the tool and I have worked with a lot of different kinds of data from vROps. It's a great tool to work with.

With vROps, we have had the opportunity to increase our capacity. After vROps was installed on our infrastructure, we were able to view the impact that VM lag could cause in our environment and how we could modify such impact. It has helped us increase performance.

vROps has helped to decrease overall downtime. For example, when we planned capacity for new infrastructure, vROps was used to analyze the new projects that we needed to deploy. In some of those cases, there were many VMs to deploy and we didn't know what impact those VMs might have on the infrastructure, in terms of CPUs and memory. vROps helped us understand the particular impact of the new VMs. It reduced overall downtime by about 30 percent.

Using the solution for capacity allocation and management has also helped us to save on hardware costs, by about 20 percent.

Overall, it's a good platform and it's important to us for maintaining our environment. The challenge in maintaining our environment is made much easier with vROps. The tool provides us with the ability to respond to the causes of problems with VMs or the environment and this is power in our hands. For us, it's a powerful tool when it comes to IT infrastructure.

The monitoring features are great. I have gotten great value out of the data collected by the tool. The monitoring provides us with the ability to respond to the causes of problems with VMs or the environment.

The capacity planning is also very good because it gives me an opportunity to make a reasonable plan for increasing my infrastructure. It fills important functions for both monitoring and capacity planning.

The visibility it provides from apps to infrastructure and across multiple clouds is also great because it's a tool that aggregates a lot of data, both on-premises and in the cloud. It aggregates everything in one tool, which helps you to analyze the performance and the capacity of the infrastructure.

We have integrated vROps with vRealize Log Insight as well. We generally use vRealize Log Insight to identify, through the logs, what is happening with the VM or the infrastructure. The integration with vROps means we can look deep into the cause of a problem. The tools work very well together. vRealize Log Insight provides us with many tools and many ways to solve our problems.

I've been using VMware vRealize Operations for about five years. I have had the opportunity to work with vROps since version 6.57, and I have started working with version 8, which is the latest version. I have installed vROps for two companies.

It provides great stability, when you follow the recommendations.

As for scalability, if you follow the VMware documentation, you can have a great solution.

We have about 500 VMs in our production monitoring. Right now it is on-premises only. We intend to start using cloud, and vROps can be the tool to monitor the cloud environment.

We have had a good experience with the support for the vROps tool, although we haven't had to use support too much.

We did not have a previous solution.

The installation was straightforward. It followed VMware principles that result from working with vCenter and VMs. It's easy to implement.

At a maximum, it takes 20 to 30 minutes to set up, but the configuration can take one or two hours. Building deep reports can take even longer.

The tool is user-friendly, but you need to study to learn about the many features that the tool offers. It is not a tool that you can just start to work with when it comes to capacity planning. You need to study the documentation. But for monitoring, you can start using it right after installation because the data is easy to understand.

Overall, the value is worth the cost because it's a tool that connects with our VMware infrastructure very well. It's a solution that our provider, VMware, developed for VMware itself.

The cost is simply something we need to pay. We can't evaluate the price because we use a VMware environment, so it makes sense to use a VMware monitoring tool. 

We use vROps in our VMware environment, but we have Zabbix to monitor other environments. It's a challenge to consolidate all that into one tool. I don't know if that will be possible, even in some months or years.

I recommend following the vROps documentation and, in some cases, it may be necessary to use a VMware partner.

We mostly use vROps for troubleshooting and forecasting. We take some reports from previous months and years for capacity and future planning.

We mostly use it for infrastructure. I know there are many packages for different apps from other vendors, but we mostly use it for VMware infrastructure. It gives us a good look inside our infrastructure, mostly in terms of capacity and reporting.

We have benefited mostly from capacity planning. During some days of the month, we have huge traffic and workloads on our systems. So, we take the previous month's reports and see the month-to-month growth so we can plan next year's capacity planning.

We have integrations with other monitoring systems, so we mostly use vROps for troubleshooting.

We mostly create our own alarms and dashboards. We use the metrics in vROps with these dashboards. 

It is efficient and easy to manage. We can find what we need from the software's interface.

We did an integration with vROps and Log Insight. We use Log Insight mostly when troubleshooting and creating some alarms to send us notifications

Lately, the chargeback site has improved, but it could be simpler. You need to create your own dashboards. It should be simple to get a virtual machine and break down the compute and storage costs.

It is not real-time. It takes samples every five minutes. Therefore, we are not using it for real-time purposes.

I have been using it for more than five years.

The stability is pretty good. Besides upgrades, we don't have issues with it. There are some issues during upgrades, but I think that is normal. Sometimes, we have some errors during upgrades where we have to start over or fix some things.

Scalability is easy. You can create other vROps machines and add them to the system, making it run like a cluster. It is easy to add more depending on your requirements. 

We have a couple of thousand VMs in our environment. 

About 10 to 12 people in our team are mainly managing vROps demand. From time to time, it changes but other departments also use it. They don't have administration permissions on the system, but they can create their own views, dashboards, and alerts. So, many people are using it,

At my last company, we changed our monitoring system from another tool to vROps because we were not getting actions from it. Therefore, we decided to change it to vROps. Because vROps is a VMware solution, it was easier to integrate and use.

I have used two other monitoring systems. However, I didn't use them for a long time. One was very simple, doing basic monitoring, and the other was a Microsoft tool. They both have many pluses and minuses.

vROps is mainly for virtual infrastructure. The other solutions are for both physical and virtual LAN infrastructure. 

The initial setup was not that complex. It was easy to set up and integrate.

The initial setup was just a couple of virtual machines, so it was a very basic installation. It was very fast. However, the implementation of the infrastructure takes months because we need to see how the system works, then decide what to monitor and report. This takes at least a couple of months.

We talked with VMware to set up a straightforward installation of the vRealize suite: Log Insight and vROps.

vROps has helped to decrease overall downtime by about 10%. We have many other monitoring solutions. This solution is just a part of our underlying infrastructure.

Log Insight has had a good effect on our overall troubleshooting. We have a huge infrastructure and can't always individually monitor it. We also did some automation for alerts.

The value that we get from vROps is okay. It could be cheaper.

I would recommend doing a PoC before using it. You can get a trial license for 30 or 60 days, so you should test it in your environment before implementing it. You should have some hands-on practice because it may not fit with your environment.

The solution is a little bit complicated to use at the beginning. When you get how it works, it is simple. You can easily make or use dashboards, notifications, and alarms.

vROps capacity allocation and management has helped us save on hardware costs, unneeded licenses, power, or other data center costs. It is not the only solution or system that we use for these purposes, but it helps.

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

I am working for a company that provides a cloud computing solution in Bangladesh. We are like an AWS or Azure in Bangladesh. We have a huge infrastructure with different data centers and different availability zones. We need to monitor our customers' VMs and their workloads. Many of them are financial companies and big corporations. We use vROps as a visibility tool to do all this. We also use it for planning and for performance monitoring.

In our country, whenever people are using virtual machines or cloud computing, they want reports, every day or week or month, about how VM instances are working. They want to know about the CPU, memory, and data usage. That's especially true for FinTech companies. We generate those reports from vROps. It provides them with relevant information and helps them to better understand things.

The most challenging part of a data center is the monitoring. You have to see how things work, such as particular instances and workloads, what the ideal VMs are, et cetera. It's important to understand cost optimization and performance tuning. If you have that kind of visibility, when you have a large infrastructure with 10,000 or 20,000 VMs, a product like vROps is great for doing all these things in one place.

The solution has helped us to decrease overall downtime. We have segregated things. We have a master replica in a different segment, and it has helped us to do so. In two years, we have had one hour of downtime, in total. vROps helped achieve that.

It has also enabled us to be more proactive in anticipating and solving problems and that has helped to decrease our mean time to resolution by about one hour.

For efficient workload placement, it's great. It's a multi-purpose solution. If you have multi-purpose workloads in your infrastructure you must use this kind of product.

In terms of cost savings, it's about optimization. When you have lots of hardware in your data center you need to optimize it. If you have lots of workloads running, you need to optimize them. With this kind of solution, you optimize your data center. It has helped to optimize our operations by 15 to 20 percent.

In addition, the solution has replaced multiple monitoring tools. It combines a lot of tools. We are still using SolarWinds and Grafana, but our infrastructure is totally built on VMware, so we are planning to use vRealize Operations Manager with everything because it's a VMware product.

One of the most valuable features is the ability to compare between AWS/Azure and the local cloud. When customers deploy something on the local cloud, with the same configuration that would apply to AWS or Azure, we can calculate the estimated cost difference between the local cloud and the public cloud. We do this kind of analysis for optimization and it is one of the best features of vROps. It is an advanced feature that came out in version 7.5.

The most commonly-used functions are easy to access.

When it comes to the visibility the solution provides, from apps to infrastructure across multiple clouds, it is a great product. If you have a VMware infrastructure, or a multi-cloud infrastructure—including AWS or Azure or Hyper-V—you need visibility and dashboards to monitor everything. vRealize Operations Manager, for managed service providers, makes it easier to understand all the scenarios. It's a good product, providing visibility into everything in a single dashboard. It is an amazing product.

They need to improve the capacity and infrastructure planning side of things. Also, I would like to see them integrate more stuff, with more detailed monitoring and different cloud providers.

I've been using VMware vRealize Operations for two years. Initially, I was using version 7, then we upgraded to 7.5, and now it's 8.0.

Out of five, the stability of the solution is 4.5.

The scalability is 4.6 out of five.

Initially, the tech support was not that good, but now it is very good. They've improved.

We were only using vCenter and ESXi initially and then we started using vRealize Operations Manager.

The initial setup of vROps was pretty straightforward, but I have been working on VMware stuff for the last six or seven years. Deployment takes about 30 minutes.

In our data center, we have a NOC monitoring team and we have a system team. Those are the two departments that are using the solution. And it doesn't require much staff for deployment and maintenance.

The value we get from the solution is worth the cost because it enables us to optimize things.

If you have a big infrastructure, you should calculate the cost for those systems. But if you have a small workload, a small environment, don't go for vROps.

We are using Veeam and SolarWinds, but they are not that efficient.

My advice is to take a good look at vROps. When you have a big infrastructure with a large volume of instances, monitoring everything in a single dashboard is very difficult, but with this solution, it's pretty easy. It's like a Swiss Army knife. You can troubleshoot and monitor in a single place. It's pretty convenient.

Overall, this is a very good product. We are using lots of VMware technologies, including Log Insights, VMware ESXi, vCenter, and NSX. There were a lot of improvements with version 8. They integrated AWS, Azure, and Google Cloud. It is improving day by day. If some of your instances are situated in AWS and some are on Azure, and you have to monitor all the systems in a single place, that's where they're improving on things. Now, they are providing the cloud-provider stuff.

We are planning to deploy Kubernetes in our data centers, because Kubernetes is a very new technology, but in our country it is not that popular yet. We will look at integrating that kind of offering later.

Previously we integrated this solution with vRealize Log Insight as a trial. But later on, we stopped using vRealize Log Insight because we were using Splunk for analytics. vRealize Log Insight is a different product. When you have a lot of stuff in your data center and you need to archive and manipulate things, you need to use different tools. vRealize Log Insight is not useful for our use case.

My primary use case is infrastructure monitoring. This is a very in-depth monitoring tool and the use cases have been to monitor multiple hardware platforms like Dell and UCS. This includes network hardware as well as the storage solutions like Unity boxes. We've also monitored the entire SDDC stack by leveraging the different management packs.

vROps provides us with visibility from apps to infrastructure and across multiple clouds. It has immense monitoring capabilities when we talk about the vCenter, which includes clusters that host virtual machines and data stores. Not only that, but with vROps version 8, you have in-built management packs for AWS and Azure. This means that you can monitor these public clouds from the same solution and you do not have to purchase any other management packs.

With vROps emerging into the application field, we can now deploy the Telegraf agent and have the application monitoring done in vROps as well. From infrastructure to application monitoring, vROps has a wide range of visibility into the monitoring spectrum.

One of the most useful features that this product provides is proactive monitoring with the help of alert optimization. It detects anomalies and I know when something is about to go wrong in my inflow, or even that something could already be happening. The alerts are available by default and this helps with early detection. Other than the alerting, the capacity planning functionality is also a proactive measure that is very useful.

Proactive monitoring is something that takes time to stabilize because once you download vROps, it will take three months for the tool to stabilize and create a baseline. Once that is complete, it can perform proactive monitoring and will help to analyze the underlying issues.

It has absolutely helped us to reduce downtime. When we talk about the infrastructure and detecting problems, the notifications and alerts provided by vROps have allowed us to avoid application failures resulting from the infrastructure not working correctly. It is difficult to estimate how much time it saves because different customers have different environments and different timelines.

With respect to workload placement, it is a feature we use and it's incredibly useful. That said, there are a few things that can still be enhanced because certain customizations are missing. If we are referring only to VMware workload placement then the functionality works great. It works well on-premises but not for the public cloud.

Using vROps has led to improved data center efficiency, which has, in turn, reduced the cost of our infrastructure. Specifically, the VMs were on different ESXi hosts and now we've consolidated some and distributed others. The cost savings come from a reduction in hardware requirements as well as licenses.

We have integrated vROps with vRealize Log Insight and it's a great thing, firstly, because the integration is very easy. The best part is that you can easily create alerts within Log Insight, and then push them to vROps. Unfortunately, we do have a problem with getting the triggered object when we send alerts from Log Insight to vROps but other than that, the integration works seamlessly. The system is best utilized if whatever integrations you have with vROps are integrated into Log Insight as well. That is when it starts giving you value.

The integration with Log Insight has improved our troubleshooting capabilities. For example, there are certain events like a disk consolidation failure where there was an alert, but we weren't able to capture it with vROps because it isn't able to capture everything. However, we were able to find it using Log Insight, which then allowed us to capture the event that triggered the alert. This helped us to save the application that was running on the virtual machine.

Implementing vROps and the right sizing has really helped the customers to save a lot of resources with respect to CPU and memory. We were able to identify what resources and VMs were idle versus what was powered up and in use. The reports helped to highlight where it was oversized and we were able to downsize accordingly, ultimately saving money.

The most valuable features are capacity planning and predictive analysis. These are some of the most outstanding features that vROps has as a monitoring tool.

The ease of usability, interactive dashboards, and graphs are features that are different when we talk about the other monitoring tools. The dashboards and the interface are very easy to understand, very lively, and very dynamic.

This product is very user-friendly. It is also very easy to deploy and because it's a VMware product, we always have access to VMware support.

The workload placement can be improved. It can be more diversified because it does not provide many options with respect to segregating the workload.

The what-if analysis section is not very advanced and there is a lot of room for improvement. For example, it should include a wider spectrum when we talk about the data center cost assessments and the data center workload assessments. It should be able to consider a use case and predict what the capacity will be after a specified period of time.

I have been working with VMware vRealize Operations for more than five years.

This product is really stable when we talk about monitoring. The only condition is that it has to be sized well. If vROps is sized properly, it will give you a value with respect to monitoring. If it is not sized well, where it has too few nodes and the number of objects is really large, or the workload is not placed properly across all nodes, we might face issues. It happens because the workload is not correctly distributed. Importantly, we do have options for properly sizing everything.

Other than this single issue, it works fine.

Scaling is easy to do. For example, adding an extra node is easy and can be done in 30 to 40 minutes. All you need to do is add a data node and the vROps internal architecture will automatically replicate and share the data across nodes.

There are between 50 and 60 people on my team. The roles vary from engineers to consultants to architects, all of whom work on the product. We have implemented this product for more than 50 clients, some of which had huge environments. For example, we have worked to implement environments with more than 40,000 virtual machines.

Technical support is pretty good. Most of the time, I've been able to get solutions to my problems. There have been times when we had trouble that they were not able to find a solution for but other than that, the support is okay.

I have knowledge of other products that are similar but I'm biased toward vROps because that is the only one that I have been working on.

This solution is very easy to deploy.

It is deployed on-premises but with the latest version, they introduced vROps on the cloud as well. This means that they now have a SaaS offering in addition to the on-premises solution.

When deploying in a production environment, it will take between one and two hours to complete. The implementation plan depends on the SMEs that are working on the project and how stable your insight is. The timeline is very personal and it can really vary.

When we talk about deployment, there is no fixed plan when we talk about vROps. The reason is that it's a very customizable tool and the entire sizing depends upon the sizing chart that is provided by VMware. Essentially, whatever the requirements of customers are, we plan according to that, and then we follow the deployment rules or the deployment process that is given by VMware to deploy the tool.

Our clients have seen a return on investment by way of cost savings through both proper sizing and efficient workload placement. What they get from this solution is absolutely worth the cost. It's a monitoring tool, so return on investment doesn't happen on day one.

When you deploy the tool, it takes three months before you start monitoring the data. Then, you start getting into the metrics, and then after that, maybe after a year or so, you will start realizing how useful it is. This will be the case with all of the monitoring tools.

This is an enterprise-level product and everything is included in the VMware Suite license. 

My advice for anybody who is implementing this product is to size the environment very well. This is the first analysis that we do; we look at how big the environment is that we want to monitor and how many objects will be there, and compare this to the VMware sizing guide. You really have to analyze that and size your environment well because if it is done properly then it will give you a lot of value in monitoring.

Overall, this is a good monitoring tool and I think it's the best one for me. That said, there is always room for improvement.

I would rate this solution a nine out of ten.

This year, we introduced the vROps feature to our platform, as part of our infrastructure.

The main use is to provide us with visibility of our environment. It helps with proactively detecting and dealing with issues that may arise, such as problems with our hardware. It provides us with alerts when there are things that we need to perform. For example, it may say that I need to expand my disk space.

From my perspective, the visibility that it provides into our apps and infrastructure is fine. There are no concerns or issues because we only use VMware.

We are currently integrating it with different VMware products including vCenter and Cloud Director. 

This product contains features for proactive monitoring but we do not use it because we have our own monitoring solution. It can do things such as sending an email in response to an event.

The most valuable feature for me is the pre-implemented, existing dashboards. The fact that I don't need to create a dashboard myself is helpful. You have the option to create them but most of the dashboards and reports that we need have already been created.

I have not compared the vROps interface against other similar technology, but with respect to it being user-friendly, I haven't had any issues with it. The most commonly used functions are easy to access.

As somebody who works in operations, the capacity management features are very important. It's a very good product in that regard.

I would like to have more documentation, in the form of knowledge bases, that better explain the technology, related products, and what the capabilities are.

Having an installation guide that assists with installation and integration would be helpful.

I have been using VMware vRealize Operations for approximately six months. We are still in the beginning phase.

To this point, I haven't encountered any issues or had any alerts with this product. As we grow, maybe later it could happen, or we could experience instability in the product, but for now, it's okay.

Scalability-wise, it is good because you can create your own reports. There is no default report, but you can create your own templates or your own reports. You always have the choice of creating a new one or using an existing one.

The infrastructure team is the one that works directly with this solution. As part of that team, we provide VMware features and virtualization for our customers. There are five or six of us on the team.

We have not been in contact with technical support.

Prior to vROps, we did not use another similar solution. We implemented it in order to have as much visibility as possible for resource management. Previously, we only knew about the CPU consumption. Now, we can use the reports to better check the resources.

The initial setup is straightforward. It is just a matter of installing the appliance, setting the IPs, etc, and then performing the integrations between other VMware components. The configuration took approximately two hours.

I completed the deployment on my own.

We did not evaluate other similar solutions prior to implementing vROps.

As we are still in the beginning phase, we have not yet worked with all of the features. For example, I know that it can connect with vROps Log Insight, but we have not integrated it.

Given my experience, I'm not sure at this point whether this solution is applicable to other technologies such as AWS or Azure. However, if the support exists, it is very good because future environments and implementations will rely on multiple technologies. It will not be VMware alone, but rather, it will include AWS, Azure, and others. Support for all of these options is very nice. It appears that VMware has this vision because they already have support for the NSX and NSX-T network technology.

I expect that it will save us money in the future, but still being in the implementation phase, we have not yet had this experience.

My advice for anybody who is implementing this product is to plan for integration with your entire platform and VMware products, such as Cloud Director.

Overall, this is a good product that is easy to install and use, and integration with other products is smooth. Although we have not used all of the features, it does provide us with good visibility.

I would rate this solution an eight out of ten.

We use this product for troubleshooting and capacity planning.

Our troubleshooting steps include checking for performance issues, and that is the main concern. Apart from that, the capacity analysis features allow us to forecast capacity planning. We also use it for performance monitoring.

This product is what we use for all of our L1 and L2 tasks, such as increasing the amount of RAM or upgrading the CPU when configuring our VMs. Each and every task is clearly summarized.

If there is an event, such as a spike in disk activity, we are able to use vROps to clearly explain to the DB team what happened. We can look at a particular disk in the storage and determine what happened. Being able to properly explain it will help the DB team to check it on their end.

As a VMware engineer, the visibility of the infrastructure that it provides is something that I am really impressed with. When we are having performance issues, or problems with capacity, or the network, it clearly, easily, and in the quickest way, will show the cause of the problem and how to resolve it. Everything is crystal clear. vCenter is also useful for troubleshooting but I prefer vROps and think that it's the best option.

This product provides us with proactive monitoring. The dashboard gives us a clear picture of everything that is going on. From an operations perspective, we can view how many hosts there are, and whether anything is critical, all in a single view.

It allows us to monitor the entire environment. For example, we can see how many data centers we have and how many clusters are being hosted. The single dashboard shows us other details, as well, including the cumulative uptime for each cluster. Proactive monitoring really helps from a capacity-planning perspective. When we conduct a capacity analysis, we can forecast the future based on how things performed over the previous six months. It allows us to effectively predict capacity.

The capacity analysis will show us details like how many VMs were powered off over a period of time. Knowing this helps us to optimize and reclaim or release those resources.

vROps has helped us to decrease our overall downtime. This is in part because of the visibility with regards to what patches are needed. If any of the hosts need a critical update, we can view it from the dashboard and perform the patch proactively. The issue will be fixed on our schedule ahead of any problems.

With respect to workload placement, proactive monitoring and good integration make this system efficient. Based on the CPU and memory that is available, it will best decide how and where to place workloads. Efficiently also comes from the fact that we can log into vROps and view everything.

Another advantage is that because it covers L1 and L2 tasks completely, we do not have to give L1s or L2s access to vCenter. Instead, we can give them access to vROps. They can perform activities from there. For example, they can configure and generate reports, and forecast capacity based on them. From a VMware perspective, the troubleshooting is quite quick and easy to do.

The most valuable feature is that everything is integrated for monitoring, performance, and troubleshooting.

The interface is quite user-friendly. Regardless of what you are doing, everything is available on the dashboard. There is nothing that is too complicated.

We have integrated with other VMware products including vCenter, VRA, and Log Insight. Normally, we rely on vCenter for alerts, and based on those, we know what to monitor.

I have not used the Kubernetes integration but the feature is good.

Technical support is normally good but there is sometimes a delay in their response.

We have been using VMware vRealize Operations for approximately six years.

We are using version 8.1, which is both stable and efficient.

We provide support to our clients but for critical things that we are not able to resolve, or if they have an RCA, then we contact the VMware technical team. The support is good and I would rate them an eight out of ten.

That said, the support could use some improvement because sometimes, there is a delay before we get a response. If it is a P1 or P2 issue then it will be considered a high priority. Also, if the issue heavily impacts our business then they work quickly and well to resolve it.

They have different support teams to work on different issues. For example, vCenter was down and we didn't know why. After we checked the logs, we discovered that it was an issue related to storage. The network team was involved, as well as a VM team and a storage team. Bringing all of these teams together, they need a single point of contact to fix the issue. We would be grateful for this because when it comes to critical issues, this is L4 support, and we need to fix them.

We have it deployed on-premises but I have also deployed it in a hybrid cloud environment. I was not personally involved in the initial setup.

My advice for anybody who is implementing vROps is to first learn how to troubleshoot. If any issue should arise, the first point of contact is L1 and L2. From there, instead of going to vCenter and checking the logs, use vROps. It will allow you to easily find problems and monitor them.

As we are technical people, we need to develop a solution as soon as possible, instead of delaying. My preference is to log in to vROps and monitor everything. Once we locate exactly where the problem is, we can give a solution for it. Only if we do not find the cause here then we go to the logs.

I would rate this solution an eight out of ten.

We have a large, enterprise-level VMware virtual infrastructure. We use vROps for private cloud monitoring. We are using vROps for capacity management and audit monitoring. If there is any issue within the infrastructure, within the thresholds, vROps will capture them and trigger alerts. The triggered alerts are sent to our ticketing tool, using the REST API, and the ticket is created according to the priority. The respective first-level teams will handle those incidents.

The incidents we deal with are mainly in things like capacity management. Over a period of time, the virtual infra keeps growing. We measure when we are going to hit the entire capacity and we will always set thresholds 30 days ahead of hitting capacity. vROps will alert on that, and we can procure more hardware proactively and we can keep increasing the capacity well in advance.

VMware has released a feature called Continuous Availability (CA). We have HA within the data center and the CA is across the data centers. We use both services. For most of the infra we are using HA, meaning within a given data center, we have a master and master replica and multiple data. Based on the growth of our virtual infra, or if there is any new deployment, we'll keep increasing our data nodes. It can do analysis and give you beautiful reports. Those reports are very useful for management. What is the status of our memory and CPU? What was the utilization of infra like in the last 30 days? How many workloads were deployed? What are the future requirements? With a simple click we can generate the reports.

It certainly helps us to decrease overall downtime. While we have cluster-level resiliency on the vSphere end, vROps provides an alerting solution. On top of that, we can use workload balancing. vROps will sense that there are multiple clusters running, some that are more utilized and some that are under-utilized, and it will report that to us. If you use it to balance, it will automate that back to the virtual infra, and it will do all the migrations automatically. Workload balancing is a great feature from vROps. Without vROps, we had 80 to 85 percent uptime. With vROps, we improved that at least 10 percent and we are close to 98 or 99 percent uptime.

It has also increased VM density on particular clusters. Based on the memory assigned to the workload, the density on the cluster varies. If we have 50 VMs on a particular cluster, but the resource allocation is greater there, that cluster is heavily used. If we have a second cluster with 100 VMs, but each VM is assigned less memory and CPU, we cannot say that the density of the first cluster is only 50 and the second cluster is 100 VMs. It will calculate based on the demand and allocation model of capacity and resources to the workloads.

With vROps we have saved on hardware costs by at least 5 percent.

In addition, in general, if I want to see the logs for a particular object, I need to log in to vRealize Log Insight and search by framing a query. But because it is integrated with vROps, when I go to the cluster tree, if I click that object and click on the logs, it will automatically provide the output. It is very simple and I don't need to log in and frame the query.

The "what-if" analysis capability is important to us. We can create a report for possible failures. What if we lose one host or two hosts? And if we add two hosts, how does that affect our resources? Or if there is a new project and we need a certain amount of workloads deployed, how many hosts do we need? With the existing capacity, if we add that many workloads what will our remaining capacity be? We can do capacity analysis with this tool.

Policy tuning and the SDDC Management Pack for health monitoring are also important.

It gives us visibility into the virtual infrastructure, and even the physical infrastructure, and into the workloads running. We have visibility even at the level of the appliance services. We can monitor everything. We can also create dependency reports, so if a service is down, it will not impact things. It gives us those dependencies brilliantly.

When it comes to policies, they need to fine tune things to make it easier. It is a bit difficult setting up policies.

We have been using VMware vRealize Operations for six years. We started with version 6.x. We keep upgrading and now we are running on the latest version, 8.1.

With the HA feature it was a stable product, but with the new service, the Continuous Availability, we have seen some issues and we are not recommending that. We are re-deploying that infra to high-availability. CA is a great feature, but we see some issues with our infra, so we are using HA. As soon as we got that new CA feature we implemented it and we learned that it creates a lot of issues for our infrastructure, but it is working fine for other customers. VMware tried to help us and their solution was to move to the HA.

But stability-wise, it's good. It won't create any issues. If there is an issue, just a simple services restart will fix them. We've mostly seen that disk space consumption increases when we keep provisioning and expanding. But that works fine and the product's stability is very good.

We can scale up the infra without any downtime. There have been no issues. 

If there is any issue, they will pitch in and help, based on the severity. They're very helpful and very knowledgeable. We get good support from them. No issues. Their support has been brilliant.

We started applying vROps in parallel with the inception of our VMware infra.

The solution is very user friendly. In one step it is ready to deploy. We don't need to configure anything on the OS level. You just deploy it and power-on. We only need to configure in, vCenter, which infra we are monitoring. When we start to onboard, it's very simple to manage. Anybody can deploy and configure it. It is easy to deploy. There are a lot of publicly available articles that we can refer to. There was a great article on end-to-end setup.

Based on the virtual infrastructure size, we decide which appliance size is needed. Do we need to go for tiny, medium, large, or extra-large. The decision is based on our environment's capacity, how many objects we have within the virtual infra. We first deploy the master, then the master replica, and then the data nodes. We can run with one master node, but if we deploy master and replica and data nodes, it gives us more resilience. So even if we have a failure on the master, the master replica makes it a high-availability solution.

Deployment takes just 15 minutes, and we can have vROps up and running in 30 minutes.

There are five members on our team and everyone has knowledge of vROps. Everyone is certified. There is no segregation of roles. Everyone takes care of the entire product life cycle, whether it's upgrading, troubleshooting, or streamlining. We use it day in and day out. Our key job is tracking of vROps' health and alerts-monitoring, to make sure it's running fine. It's part of our daily work.

They forecast our pricing based on the objects we deploy, but I'm not involved much with that. The licensing part is a bit complicated.

We have not evaluated other solutions since this one is from VMware itself. We prefer to use the proprietary solution.

It provides proactive monitoring, but it is not a real-time monitoring. It is polling every five minutes. If there is an issue in the first minute, but polling happens at the fifth minute, there is a gap of four minutes. It will capture that failure and alert in the fifth minute. It is more reactive monitoring, in that sense. But at least we know there is an issue.

Overall, vROps is maturing, year by year. New versions have a lot of scope. We are not fully utilizing it, but if you understand the product features correctly, it will save you a lot of cost and reduce manual efforts. I would recommend it. If someone is looking for virtual monitoring, vROps is the best solution.

We wanted a tool for monitoring the entire virtualization infrastructure. In addition to infrastructure monitoring, a second use case was application monitoring. At the time we were looking, they had a tool called EPOps through which you could do application monitoring. We also heard about some other components, partner integrations for VMware, through which we could monitor the SAP landscape and storage performance.

There was a team of five or six members. Only one member implemented the vROps, but the visibility was provided to all five of the core infrastructure members. They have been able to use the tool effectively to monitor all the applications from an infrastructure point of view.

We also created an application-specific dashboard, from an infra point of view, which was released to end application teams, so that they can then monitor the performance of their applications: How is the CPU and memory? How is the software: working or not working? It is a one-of-a-kind solution where we have onboarded application teams and given them logins for their specific areas.

vROps also provides proactive monitoring, at some level. It's not practical to keep on logging in to the tool to look at it. So you can create alerts and it will alert you if memory utilization is going beyond 80 or CPU utilization is going above 90. It significantly improves the monitoring, because we are able to act on it beforehand, before the system goes down. It has decreased our downtime by 20 percent. We are more proactive in anticipating and solving problems, and it has also reduced our mean time to resolution for infrastructure by about 10 percent.

We also use it for capacity management, for buying new capacity. It has saved us on hardware costs because we're able to plan properly and we're able to buy the necessary hardware. It has saved us around 50 lakh in Indian rupees [about $70,000 at the time of this review]. And because we are not buying as much infrastructure, the licensing requirements and costs have also been reduced. And it has saved us about 5 to 10 lakh [about $7,000 to $14,000 at the time of this review] in power and other data center costs.

For VMware monitoring, it gives a good amount of data, which can be circled back with the IT hierarchy, or application owner, to have a discussion. 

VM rightsizing is another very good feature and capacity planning is something else that I like about it.

In addition, over time it has become more user-friendly. When we deployed, it was only three-years-old. Recently, it has matured enough to monitor cloud infra also, but we have not tried that yet. But it has matured over the time. The GUI has become more user-friendly and it is very lightweight now.

It shows end-to-end visibility for infrastructure: CPU, memory, and all the processes that are running on the server. It will provide you everything. It will provide you some information about applications, depending on the tool capability, but it is not an application performance monitoring solution.

We integrated vROps with vRealize Log Insight, but it was not helpful to me. It was not giving me any good data.

Another area where there is room for improvement is an area which I've not looked at: cloud management and how efficiently it can do it. 

Also, while it is able to do VMware management very effectively, if you have any other hypervisor solution, I don't know how effectively it would work. It should scale to other infrastructure also.

We have been using VMware vRealize Operations (vROps) for the last five to six years now.

The product is more or less stable. We may find a database-related issue once in a year because it uses the open source Cassandra DB, so sometimes that does not work the way it should. 

Also, high-availability within the product is not so good. They have tried to improve it over the time. We have created a two-node cluster where, if one cluster goes down, the other node will take over. Whenever we have tried, it was not that seamless, and we had to involve their support.

It is scalable. It is easy to scale. We also implemented it in a remote location, where we just had to install a remote connector. All you need is good connectivity.

In a given week we were using vROps three to four times. That frequency has been reduced and now we use it about twice a week. I look at it in my role as manager of IT infrastructure and data center. On my team there are three people and they also look at vROps from time to time. They create VMs. They are database, software, and backup administrators. Above me there is our leadership team that also looks at it on a case-by-case basis.

Technical support is very good, no doubt about it. If you raise a very high-priority case, you will get an immediate response. And most of the people are able to solve the problems. You don't have to roll the case over to the next available or superior agent.

We didn't have any tools before vROps, but it provides a single tool for virtualized infrastructure monitoring.

The initial setup was a complex process, and it is still a complex process. There are too many products: the UI, database, and you have to properly size it according to your requirements, otherwise it does not work well.

Our deployment was a one-year project.

We took a full suite of licenses for all the VMs which we had. And that time we had some 600 VMs. We took two types of licensing, advanced and enterprise, where we were trying to achieve our application monitoring in the enterprise licensing. The advanced was used to create dashboards and other kinds of reporting.

Besides this, we used one more product, VMware Compliance Manager, which they have now stopped. That is one area which they have now integrated into vROps, but we have not tried it so far.

We used VMware professional services. Our experience with them was okay. We thought we would implement way further, with VMware onboarding, but it took a year to complete the project.

We haven't really seen ROI. That was not the idea at the time. We wanted a monitoring platform. Return on investment on such a product is also fairly difficult to calculate.

Over time they have changed the pricing and the licensing model. Five or six years ago, when we took it, it was a very good option. Now, I think I have to reevaluate, to be honest.

We looked at SolarWinds and BMC. One of the primary reasons we went with vROps was that we had a large VMware infrastructure. Also, at that time, the dashboards were very good. Also, at some level, it was an agentless solution. In all the other cases you had to install an agent in the end VMs. But because vROps is tightly integrated with VMware, it monitors without agents. That was a factor. Cost was also a factor.

My advice would be to look at it holistically, meaning look at what you want to achieve in the final endgame. Also, evaluate a couple of products to get a feel for them and which product suits you. In addition, create roles within your company, because this needs dedicated attention when you implement it and attention to sustain it. There should also be alignment with an application team or leadership team when implementing this kind of solution.

I work for a Post Office service and we use this solution to monitor business core assets which help to deliver packages. There are many applications we need to monitor as part of our service and to see their availability. We also use it to analyze and to forecast. Finally, we use it for business reports for sharing the status of memory, CPU, and data storage. The solution is very big in terms of how many variables you can extract.

There are many clusters that are displayed, each solution and its specific application. For example, for our front-end website I can specifically monitor the resources, the memory, the storage it consumes. I can extract this information to create a report for a specific cluster.

Each group of employees has access to reports about specific clusters. You choose the information to add to the forecast from various KPIs. It helps the company understand capacity and to see the information it needs to see regarding the future.

In the country where we operate, we have something called a PDI, a development and innovation program or plan, for looking toward the future and delivering new applications. vROps gave me the information I needed to build a new PDI. It gave me excellent data for that.

Every four years, we have a plan to replace hardware. In our last replacement, vROps helped me to reduce the hardware we needed because we could optimize our solution. We have also saved on power and other data center costs. In that area it has saved us 30 percent.

It has also helped to decrease our overall downtime a lot, because I can see the distribution of memory and the CPUs. I can see if there are issues with storage or the network or CPU. It helps me to plan so that the system is more available.

We have integrated vROps with vRealize Log Insight. With this we can correlate logs between vROps and the ESXi. I have shared this dashboard with a group of people. They can see this information day by day and look for issues and problems in the production area. We can see the relationship between the tracing and the logs from the ESXi and the server, in the same dashboard. We can see what actions are needed to solve problems. That is a very important capability for our company.

For me, the most valuable feature of vROps is its reporting. We use the reports to send information to certain groups within our company to help forecast the use of resources.

It provides a focus on the VMs. At a glance, it shows the applications inside of each VM. The next step would be to use the plug-in, the APM.

The ITIL is very important for helping resolve capacity issues. It helps deliver a lot of information about issues faster.

I've been using vROps for six or seven years.

The solution is very stable. I don't have any problems keeping it running. The maintenance is easy and it's easy to upgrade.

When it comes to maintenance, usually there is a ticket, and the person within our company who is responsible will analyze it. It may be a new upgrade, a new feature, a patch. A person is assigned to it to decide if it's necessary to upgrade or apply the patch. Once it's approved we set aside time to take care of it, but it's generally not difficult.

The scalability is excellent, no problem. In the time we have used it, our environment has grown. We can add more servers, more data. Scaling it is easy.

We have two sites and together there are 276 servers. But thanks to the use of vROps, with each new purchase I buy fewer servers. When we started with it we had more than 300 servers. Now we purchase fewer of them.

For me, the technical support is the biggest problem. I've been working with them since 2016 and in the first years their response was faster than it is today. That is a problem. Also, I need to put together and send them a lot of information. And then I wait one day, two days. The support has been getting worse over the last few years. They need to improve it. Two days for them to respond is a big problem for me.

I realized we needed a solution to monitor our VMs. So six or seven years ago we decided to buy a solution to monitor, forecast, and give us unique dashboards with information on issues such as capacity, and to monitor applications, etc.

The setup is a simple process. In our company we have a system, BMC, which makes it possible to deliver information and to integrate BMC and vROps, using the SDT and VMware. This process, the integration between BMC and VMware took two years. 

We did the implementation ourselves with an internal team.

At the higher levels in my company, such as the CIO, they looked at what the solution delivers and they felt the ROI was faster with this solution.

When we last did a comparison of solutions, the pricing was equal or similar.

Because we are a government company there are compliance requirements. Any purchase has to go through a public process. We have to publish the information in the market. We looked at BMC and CA, and we looked at CA recently.

We tested and did a proof of concept for each of the solutions, not a big test but a simple process; enough to see how they operate. For me, the big difference was that vROps is a VMware solution and is integrated with other products such as vRealize Log Insight and vRealize Automation, and of course, vCenter. And the unique dashboard was also a great addition to our operations.

In the future I'd like to use the plug-in and the APM. In the future, using the APM, things will be better. Nowadays, applications have under-utilization of hardware.

I'm happy with the solution. There are many options for using it because of the features vROps has.

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.

I've been using this for managing our company's infrastructure. We have a cluster of somewhere around six nodes. 

We're using it in a hybrid mode. We have our on-premise data centers and we are operating on AWS as well. We have multiple legacy apps which require a certain type of monitoring to be enabled and we kept that enabled from the on-premise, but the advanced features for monitoring are being explored on AWS.

Primarily I have found it very useful from the compliance perspective and for control and agility. These are the three main things which are helping us to have a more proactive approach in managing the infrastructure.

We used to have COTS products for monitoring our ESXi hosts. We had a team that would check on alerts and then go on to our approach for remediating the problems. vROps has helped us to reduce the costs and increase the efficiency, because it has a lot of features that tell you where things are going wrong. We have been able to cut down on the cost of resources and we have a smaller team to manage the infrastructure now. The solution helped us to reach a level where we have low resources but high efficiency. Its gives you the most accurate alerts and remediation processes for closing problems.

We have a support operations center where we have a dashboard running 24/7 and that is where vROps manages things and tells us about the health of the infrastructure. If something is going wrong, if it picks up any anomalies, the team takes care of it, remediating based on the recommendation of vROps in the dashboard.

Since incorporating vRealize Operations over the last two years, I don't recollect there being a big concern in regards to downtime. We have not had any downtime happening in the last two years, since we put vROps in place. If we correlate it to the other models we were using earlier, we had certain incidents where we were not even aware of what was going on, on the ESX level. vROps has helped us to reduce our downtime by 90 percent. I'm taking the 10 percent off to account for planned maintenance, because sometimes we need to go offline for maintenance done for our entire infrastructure. But downtime has been reduced 90 or 95 percent since we incorporated vROps.

It has also increased our efficiency and decreased our mean time to resolution. Infrastructure agility has gone up and we're much more efficiently handling the infrastructure now, whether on-premise or Amazon. It provides the agility to do the deployments, but even then, deployment has to be initiated at a user level. Overall, it has increased our efficiency by 30 to 40 percent, in terms of deployment.

The solution has also played a very vital role in workload placements and we have been able to manage workloads and capacity planning, among other things, in a very efficient manner. We are 70 to 80 percent more efficient in regards to management and capacity planning. It gives you visibility into the infrastructure so that you never go beyond the sources that you have and it has helped increase our VM density by around 70 percent. In addition, performance has definitely increased by a similar rate of 70 to 75 percent compared to the previous product we used. There was a leap forward when we used vROps.

Regarding hardware costs, what we used to do before we had vRealize Operations was to buy things in chunks. If we needed storage or additional memory, we might procure 10 TB of storage at one go and then start using it, despite the fact that only 4 of the 10 TB was being used. That's how we would do hardware resource allocation: we would have to buy that item and put it into the system. But now, because of the visibility with vROps, we know how much storage we will require six months down the line. That means we do procurement in smaller chunks. We save hardware costs and, at the same time, resources are planned in such a way that we never run out of resources. Because we have six- or seven-node cluster, from the power perspective, we are not seeing that much in savings, but definitely due to the capacity planning and the visibility, we have seen a cost benefit.

There's a feature known as Smart Alerts in vRealize Operations, which I have found to be useful if there's anything going wrong in the infrastructure. What usually happens is that you get so many alerts that you become confused. Smart Alerts give you visibility into your infrastructure and also recommend how to fix the situation. That's a feature which I'm really a fan of.

Control, from the compliance perspective, is also helpful because we are a PCI DSS-certified company. It keeps us in compliance so that all of our servers and other things are not breaching any of the baseline protocols and baseline policies which we have laid down for the company. That's another thing which I like about the VMware vROps.

For the initial setup, there should be some sort of auto discovery of the environment. That should be enabled. It has the ability to discover a main node, but it could still be made easier, to reduce the initial configuration and setup time.

We have been using VMware vRealize Operations (vROps) for the last two years.

After incorporating it during the initial phase, there was a discovery period for the infrastructure and for vROps to adopt our set of configurations and advanced policies. Since then, it has been pretty stable. We haven't had any issues.

The scalability is fine. When we started using vROps, we only had a three-node cluster. Over the last two years, we have gone up to a six-node cluster. It is pretty scalable. The good part is that adding nodes to vRealize Ops is a pretty straightforward thing. It has given us the visibility to plan and to scale to the level we are at now.

We have over 3,000 people, out of an employee base of 10,000, using the apps that are running on the ESXi that is managed by vROps.

In terms of increasing our usage, as of now there are no plans because it widely depends on the expectations of the business. It's a global thing now because of COVID-19. We still don't know how we are going to grow this over time because the business is in a "back seat" right now. But I'm positive, down the line, of the possibility that we will go further with this.

We have had a couple of cases where we have reached out to VMware support and the tech support has always been awesome from all perspectives. Their problem-solving attitude has always helped. We have been using VMware for seven to eight years now and we have gradually grown but support has been awesome during that time.

In the past we used Paessler PRTG as well as other tools.

The initial setup is straightforward, not complex.

Initially, because we were not familiar with vRealize Operations, it took us a while to get it set up. Our infrastructure is dependent on multiple volumes, ESX clusters and the storage. It took us seven to 10 days to have a fully functional deployment of the solution. The initial setup took us less time, but setting out and defining the policies, the baseline and advanced policies, happened within 15 days of the deployment.

For deployment, we used a team of four onboard resources and we got in touch with local consultants who are VMware Certified partners for doing the deployment. The initial deployment was done by the certified partner and then a knowledge transfer to the resource team took place. After a month or two, our team was able to be 100 percent hands-on with it and started using it.

I rate VMware vRealize Operations very highly because it gives you multiple features such as compliance, agility, and staying hybrid, although if you want you can do it on-prem or on the cloud. I would recommend it regardless of the deployment, whether it's on-prem or AWS or hybrid.

It is user-friendly, but it definitely requires a little tweaking in the environment when you're doing the installation to set it per your requirements, your infrastructure, and per your expectations. What are you trying to monitor? Once you're done with setting up vROps for your cluster or nodes, then it's very easy to use. It will really help you out to get to the stage of automation for your infrastructure, so you don't need to depend on manual processes at all. 

We are not using Kubernetes or Tanzu as of now, but we are planning to incorporate it down the line, maybe in three to six months.

Overall, I would rate vROps as a nine out of 10. The one point I'm leaving out is because there is room for improvement, as I mentioned earlier.

For our clients, vROps is used for managing their environments, having a single pane of glass, so they can go in and have a view of what's actually going on in their environments. That's especially true when it comes to TCO perspectives. When it comes to the TCO, they get to realize how they can start trimming down VMs that are not working, or cutting down on the resources that those VMs are using. That helps them do better in their environment and to lower their operational costs at the end of the day.

We do have the big enterprises; we've got quite an extensive team that looks after clients. But my clients are SMB clients and are where we see a need for vRealize Operations.

For me and my clients there's a very big benefit from a monitoring perspective. It provides proactive monitoring and helps instantly. It gives you this one dashboard with an overview of everything that you're busy with, within the environment. You can get notifications, on time, to deal with a situation and it also gives you references to what you can do and what you can't do, or what is recommended by VMware. It has links for you to find the resolution to the problem. From that perspective, it's brilliant. I don't think anybody could ever ask for anything over and above that. It's very proactive.

vROps has also enabled us to replace tools. SolarWinds is one.

The capacity planning is one of the most valuable features. That is brilliant. A lot of clients, especially now due to COVID-19, are in a situation where they don't have a lot of money to spend. They're looking at what the best way is to start cutting costs, especially from an IT perspective. A lot of companies look at it from an IT perspective rather than anything else when it comes to business. That's key. 

Also, the integration with Blue Medora is brilliant, especially the way it can let you know if there is a problem in the environment, and various ways to fix the issue.

In addition, for me, it is seamless and easy to get to know. It's quite straightforward and it's a nice product. The user-friendliness is brilliant. At some point you need to just keep kicking and kicking until you get what you really want. But from a user perspective, it's quite straightforward in terms of being able to understand as to what is going on and how to get to specific pages. The first page gives you everything. It highlights everything: your risk, your health, and that kind of stuff, with the dashboard. It is quite easy to use, especially once you've kicked around a little. From there, I don't think you should even encounter an issue.

The integration with vRealize Log Insight is amazing for me. I don't think there's any other monitoring software that I'd choose or sell to a customer. That's especially true now from a vSAN perspective and getting the logging side integrated into the solution. The correspondence and the communication between the two products is great. I would always recommend going down that route.

I've used vROps for about a year.

I have used it a handful of times when it comes to client deployment. But there's time required to get my head in the game with it, because there is a lot when it comes to the product itself. We are going to be installing it in our lab as well, to get more clarity around how it works, especially when it comes to the integration with Blue Medora and those kinds of things.

On a scale of one to 10, I'd say I'm probably a four when it comes to vROps, but I hope that I'll actually get to 10, to be the best in it. It's a very brilliant product. I love it, the way it works, all the functionality. Everything about it is just amazing.

The stability is great. On a scale of one to 10 I would put it at 10.

The scalability is also great. I haven't played with it that extensively but, from my understanding and from what I know, you can scale as much as you need to. As long as you understand the dashboards and how to create them, you should be okay. From that perspective I think it rates quite well.

The initial setup is straightforward. You just download the OBA and—"Bob's your uncle." The installation guide is also very helpful. They give you a step-by-step guide for how to deploy it. If you read the document, you'll be okay from the beginning until the end. You shouldn't have a problem.

If it's just a basic deployment, and if you've already got the OBA, it should only take a good 30 minutes, and that would be a lot. I'm just covering my bases, in case there is anything that may not have been taken into consideration. But plus/minus 30 minutes should be enough to do a basic deployment.

Currently there are five of us in the company who are using the product or who are familiar with the product. From a maintenance perspective, the dashboard does most of the job. One person can have a look at it and there are the rest of the guys on the back-end for support. I don't think it needs 10,000 people looking after the product. The product is an automated, driven process. You just need to look at the dashboard and understand what it says and it should make the job a lot easier. You shouldn't need more than one or two people looking at the product every day.

Overall, the value you get from a vRealize is definitely worth the cost.

vROps is a bit expensive and that's a reason that small clients say, "No, I don't think we need this." From a pricing perspective, it is quite steep. But "expensive" is relative, depending on what you need. Others might say, "It is expensive, but I think we can use it to better our environment." It is quite an expensive product. But if you really require something, you'll do it anyway.

The main difference between vROps and the SolarWinds solution is the integration to the VMware stack in its entirety, and the opportunity to integrate it with different product sets, like Blue Medora. That makes it quite a different solution compared to SolarWinds which, as far as I know, doesn't have that type of integration. Maybe there is something new along those lines with SolarWinds and I just haven't looked at it, but I've never seen those types of integrations when it comes to SolarWinds.

When we speak to clients about it they often say, "I'll think about it." I think the best thing for them to do would be to actually use it, with the 60-day trial. They should play around with the tool and then come back and say, "This is what I can do in the product." That way, they would see what the product is about. I'd rather they experience something than somebody else telling them about it. Clients have access to VMware. They can download the solution from wherever they are and then start playing with it. They need to see what it can do and realize, "Wow, what an amazing tool." They need to see the benefits of the tool. It's the best monitoring tool. It is expensive, but expensive is relative. It's a matter of the client having a play with the tool and realizing what an amazing tool we have.

My clients are quite small so when they do use it, it's when I'm with them. They don't understand what the product does. For me it's a big thing, but for them, it's neither here nor there. They say, "We'll deal with it when we can. We'll look into it whenever we've got the time." It's never the situation where I've come back and my client is saying "Wow, that is brilliant!" They say it's brilliant when I do it but they don't go back and start utilizing the tool. So I don't really always get the feedback that I desire.

One of my colleagues is busy with a deployment at one of our clients and he's also doing the Blue Medora integration. I talk to him on a daily basis just to get an update, and he's amazed at what vRealize can do. From that perspective I think that we're quite happy with the product.

We are using vROps for its monitoring and alerting mechanisms, for the entire VMware environment. We use the analytics and recommendations.

It's a monitoring tool. It is very common, but in my last eight years of using it, what I have seen is that it gives detailed monitoring information for your entire VMware infrastructure. It gives recommendations in terms of resource utilization.

A major part of its functionality now is business cases. I can identify them now, meaning if we migrate to the public cloud, what the business case would be.

In addition, the proactive monitoring and recommendations always help you to avoid unwanted downtime. If I see that a machine is heavily loaded, I can apply the recommendation and balance the load across all the nodes. And if the machine is under-utilized or over-utilized, it will tell you whether to optimize or to increase the resources accordingly. It improves the operational experience as well as the performance.

It automatically places workload on the machines where there is any available capacity or more resources are available. You don't need to worry about that. vROps does it. The workload placement has definitely increased VM density. That is part of the VMware DR solution. It enables you to place things automatically on a machine with less load so that you can increase the density, depending upon the resource availability on the machine.

One of the best features is the monitoring. It gives you proactive recommendations, based on the information that you have. It recommends changes. For example, if an ESX service is heavily loaded, it will tell you to make some changes, such as storage optimizations. Every tool does monitoring, but this one gives you more proactive monitoring, with the recommendations and actions that are needed.

VMware products are user-friendly, there is no doubt. That goes for all their products. I use multiple VMware products and I don't see any difference among the products in that context. vROPs, specifically, is easy to handle, even if you don't know anything about VMware. If you have some experience in monitoring, the tool will definitely be easy to learn and to get hands-on with it.

Also, if you want to migrate to public cloud, it helps with the business case. The tool gives some rough estimates about migrating to the public cloud or to another cloud.

vROPs is integrated with vRealize Log Insight by default, but we don't use it in our company. But it allows you to keep the logs and go back and identify what the performance was like a month back. That can help with troubleshooting because if you know what things were like a month back, and an issue comes in, you can get into performance metrics for that month. All the log data will be available for troubleshooting and capacity management.

Three or four years back, regarding business case data, when looking at migrating to public cloud, we had to feed in the pricing of all the public clouds manually. I don't know whether that information is now available automatically, but that would help.

Similarly, if it could help with calculating on-prem costs, based on their experience, it would help customers determine whether to remain on-prem or move to the cloud.

I've been using VMware vRealize Operations for almost eight years.

The stability is good. They keep updating it with the new versions and new features. So many features have been added and so many different licensing models have come in. Variations are available for data center requirements and remote site requirements. But the product looks very stable.

I've never had a problem with the scalability of vROps. It can scale to any level. I've never reached the maximum of what it can do.

The setup of vROps and Log Insight is very easy. It's not intensive or very complex. I did it about four years back when we deployed it in my previous organization and it was very easy for a standard VMware environment.

The amount of time it takes depends on how big your VMware environment is. There's no benchmark value. If you have a small environment it shouldn't take more than one or two days. But in a bigger environment, the scanning of data takes time because it has to talk to vCenter, pull all the data, wait for all the data to come in, and see if there are any recommendations. But that should not take more than a week and you should be able to see everything, even in a much bigger environment.

To deploy, you need to have a VMware guy and it depends on where the data is being integrated to. If it's only a VMware environment, you need only one or two people, max.

If the deployment is being integrated with some enterprise tools or third-party vendors, you may need to work with their separate teams.

In terms of value, it depends on how you look at it. Is there really any other solution for VMware? I don't think so. If you bring in something else then you have to think about the support matrix, compatibility, and you multiple vendors involved. You go with VMware because of the easy integration and support. It's a big product and it costs, but the value depends on your point of view. If you look at it from a cost-perspective, it's costly. If you look at it from a compatibility/support perspective, it meets all your requirements.

Because we are a valued customer, we got a good discount from VMware on the pricing. What they offered and what we have gotten as a return on our investment are reasonable.

Every VMware product is a licensing challenge. It's always costly. It's based on processors. From a technical side, the product is very good. The challenging part is always the licensing.

They should have some kind of alternate pricing models. They have a simple model, CPU-based. They should do something to make it more reasonable there. And they have too many variations. I think there are three different models that depend on different form factors. They should make it easier. With three different versions—standard, advanced, and enterprise—it's confusing.

This tool gives us everything we need. I don't see any alternatives to it.

We don't use VMware's Tanzu solution along with this solution for Kubernetes monitoring and management, but we have had discussions with the VMware team about it. It is still in discussion.

Leaving the issue of cost aside, I would rate vROps at eight out of 10, in terms of the technical side, integration, and support.

It's typically used for our interactions with our software engineers, especially when we are configuring or assigning resources to them. It is the way we get the virtual machine to be right-sized. They usually ask for more resources than they need and with this tool I can manage the resources.

There was a system with a Docker cluster that was having really bad issues. A server would go down and the machine would move to another server, in this case a virtual machine, bringing down the whole cluster. Thanks to vROps I was able to closely check the resource usage to spread the load, so instead of having three servers we moved to a more stable solution using eight servers.

vROps has helped to decrease overall downtime by about 20 percent.

In addition, we work here with a five-year budget and we need to have a really good forecast to design solutions because those solutions must last for five years. It's not easy to increase the resources of a solution in the middle of this five-year cycle. So vROps helps a lot in seeing how the load is increasing over time. In that way, I can forecast for more than a two-year period and do so for five years, at least.

The most valuable feature is the ability to check the right-sizing of a machine because that way I can assign the real resources that are needed.

It's also user-friendly. One of the things that I really like are the ready-to-use dashboards. You can get them from a dashboard marketplace where dashboards are contributed by other people. You can use them in your facility without any problem, and some of them are really useful.

The solution also provides proactive monitoring. It's good to have a baseline of how the machine is normally working. After that you can check if it has gone beyond this baseline. If something goes away from this baseline, it usually means you have a problem and you need to fix it.

There is room for improvement when it comes to the integration with Active Directory. Sometimes I need to log in to the application using my Active Directory account, instead of using the regular admin for vRealize Operations. If I want to deploy this tool to more users, I need that.

I used vROps a lot about two years ago and I started with it again about two months ago. I'm the person who designed the whole VMware solution at ALMA Observatory and I support all of it and administer the VMware platform, among other things.

It's quite a stable solution. I have never had a problem with the solution. Every time I want to see something or check something, it's always there.

I have not needed to call VMware for technical support for this solution.

We did not have a previous solution. We only used the typical solution in vCenter for checking performance.

I wouldn't say that vROps replaced a lot of other tools but that's because there aren't too many products that are similar to vROps.

We were already customers for vROps, but at first we were not using a lot. Then we needed to do an upgrade and it was not an easy path to follow. But in terms of the setup and configuration, it was straightforward and much better than the old versions. The last version I used was v4 and, compared to that, it was completely easy.

The deployment, even though I was doing other stuff, took one or two days.

I don't think the solution saves us money, but with it I can better say how the money is spent.

We provide services to our scientists. I can say, "I will provide you with 20 virtual machines, 20 TB of disk, bandwidth, and I know it costs X. The biggest impact is the way I can see where the resources are that we are using. That makes it worth the cost.

The pricing is a little bit expensive.

Licensing is an issue because there are always changes, and by that I mean cost increases. And that's not only for vROps but for VMware, vSphere, and all the products that are involved.

I used Turbonomic a long time ago, but only as a test.

The implementation is easy. You just need to assign resources to install all the virtual machine requirements, but the process is straightforward. My biggest advice is to check the dashboard marketplace because you can find dashboards that are useful to you too. The dashboards are produced by the community. They are free, although some of them need container packs that you need to pay for, or you may need a licensee to use some of them.

We have been able to use vROps to optimize our environment and do right-sizing for most of our VMs. vROps has also been able to help us in regards to forecasting and adware procurement. Therefore, we can see our utilization in the next six months and how we have been trending.

The company is multinational. We are still running on-premise with a plan of moving to the public cloud. At the end of the day, it will probably be a hybrid environment.

When it comes to apps and infrastructure, it provides us with valuable insights. 

It has been helpful around capacity planning, which we traditionally did on a yearly basis. However, since last year, I started using vROps to reclaim and save more resources. It has been helpful along those lines.

In the next six months, vROps will hopefully give me an accurate forecast. Also, it will be able to look at my environment and prove some vendor requirements wrong. 

The dashboards are interesting. We have been able to use the dashboard to monitor the environment. There is also a newer feature where we can share dashboards with people. We don't necessarily have to give them access to vROps. That has been great.

The optimization and performance are helpful.

If I could integrate with vCenter with vROps, then I could execute more things by managing vSphere from within vROps. That would be great.

I have been using vROps for about a year. We got the license last year, but it could not be deployed until later in the year. 

It is a stable solution.

vROps has helped decrease downtime by 80 percent because it gives me a lot of visibility into my environment. With its performance optimization, we have been able to see things happening ahead of time. It also works concurrently with some other monitoring tools. For example, I am also using VMware Skyline, which has helped to drastically reduce downtime. 

I haven't had any downtime this year.

If I see the infrastructure grow enough, then I will scale up.

I am the only one using vROps within the organization.

The VMware technical support is helpful.

Before now, we did not really have a tool for capacity planning. This is the first tool that we have used. It has been great.

The initial setup was straightforward. The documentation is online, so I was able to deploy it before the training. The deployment took me three weeks. 

We don't have a test environment, so everything that I deploy has to go straight to production. However, when deploying vROps, I knew that it would not break service nor cost me downtime, so I decided to give it a shot.

I did the deployment. Going through the documentation, I was able to get different options, picking the one that suits my environment.

If you are not that familiar with the deployment and how to do it correctly, then you may need an expert's advice or intervention at some point in time. You should be able to find your way around 75 percent of vROps. Overall, the solution has been great for someone who is technical.

Make sure you get the right advice and documentation for the deployment. So, if a person or customer is unable to deploy on vROps, then they should get the right expert to assist them with the deployment. Because if you have the wrong deployment, then that might put you in a mess and you might not get the value from vROps. If you are going to implement the solution, do it the right way.

At the moment, I am the only person managing vROps.

It is worth its cost. With VMware, you always get your value for your money. 

vROps has saved us a lot because it has reduced our procurement costs. Usually, we would have a rise in procurement costs at the beginning of the first quarter. We haven't seen that going into 2021.

The solution has a huge cost. If we could just have one license covering everything that vROps can do, that would be great. I would prefer it this way.

We need a separate license for vRealize Log Insight, which has not been integrated. However, it's something I'm looking forward to using.

We did not look at any of their competitors.

We are still running vROps in parallel with some products that we are currently using. However, I am seeing the opportunity for it to take over from our other tools in the future.

From what I have read, it is a great tool that you can use across multiple clouds.

We are planning on implementing VMware's Tanzu solution along with vROps for Kubernetes monitoring/management in Q1 2020. I am currently familiarizing myself with it because I know it's something that I will be deploying pretty soon.

I would rate this solution as a nine out of 10. 

We provide solutions related to VMware, Docker, and Kubernetes for banking data centers. 

We use this product to monitor virtualization infrastructure and different resources that we use in our project. We implement vROps into data centers that are working together to develop vROps solutions with different interfaces. One of them is Dell EMC Adapter which is added to vROps to monitor and collect various logs related to Dell EMC storage. We also add another plugin to monitor HP.

We host around 1,200 to 1,300 virtual machines. Our data centers have more than 50 physical servers.

Before using vROps, we used SolarWinds and ManageEngine, as well as Cisco NCM, to monitor different resources in our infrastructure. But we established a new project for customers and unified all the monitoring solutions in just one platform, vROps. vROps helps us to predict many issues and problems that we may face in the future. It helps us to optimize many configurations because we have good visibility into resource usage.

Because we can predict many issues and problems, we can solve them and provide options for our customers to change configurations and optimize their environments. We are able to fix problems in advance. That helps us to decrease the amount of downtime in a given month. After using vROps, in the second year we were able to offer our customers a new SLA at 99.97 percent. That has proven to be a great benefit for our company.

It is very efficient. By using vROps we have fixed many problems. In terms of the efficiency in operations, monitoring team members are very satisfied because they have dashboards to monitor specific resources and details.

Once we started using vROps, we were able to change out servers and replace them with new versions because we could detect different problems related to the old resources we were using in our environment. With Cisco NCM, you can't detect these problems. Using vROps enables us to detect problems related to the hardware and the issues that arise from hardware error.

After one year of using vROps, we integrated it with vRealize Log Insight and vCenter. vROps and vRealize Log Insight are integrated very well. The integration helps us to gather a lot of event details sent by Log Insight to vROps. The integration between these two products helps us to go into the detail of events. It helps us to monitor problems and detect issues. Then, it provides recommendations to take action and solve problems directly.

One of the most attractive features in vROps is collecting information, logs, and events and, after that, providing proactive predictions about usage of resources. vROps also offers recommendations. For example, in the next two months we might face problems with CPU usage. vROps predicted and forecasted these issues in advance. That's a very useful feature.

In terms of user-friendliness, vROps provides a unified dashboard and you can easily create different dashboards to measure different resources. The UI is very friendly. Our team members are very satisfied with working vROps in comparison to different solutions like ManageEngine and SolarWinds. vROps is very unified and integrates with different solutions.

As a result of using vROps we have easily been able to reduce a lot of unused virtual machines in our infrastructure.

There is room for improvement in asset management and resource usage.

Around two years ago, we installed and configured a vROps project. I'm responsible, as a team leader and the VMware engineer, for different technologies on VMware, like vSphere, vROps, VMware vRealize Suite, as well as container infrastructure.

Because we need high-availability for our solutions and to ensure that our customers have monitoring solutions available, we established a cluster in vROps. vROp provides you a clustering installation for high-availability and sustainability. We had two data centers and we created two vROps that are synced together as Active-Active. If one version is down, the second one is active and provides monitoring.

Because of sanctions in my country, we don't have direct support. We use a partner. Although we can solve most of the issues within our team, we do use our partner for specific problems or issues that we can't solve.

If you study the guidelines, the setup process is very clear. We didn't have any specific problem installing and implementing vROps in our projects. If you have experience in the installation of vROps, there are no problems.

The deployment took about one month. We studied and reviewed the features and implemented a pilot environment in our company. In terms of the specific plan that we provide to customers, we implement vROps and start a one-month period where it is in a test environment. The day after that we move vROps into the production environment.

We make use of just one license for vROps and we don't need other licenses for things like SolarWinds and Cisco NCM.

I recommend implementing vROps by first setting up a pilot environment. You need to become a master in vROps to make the best use of its features. If you don't have any experience with a lot of the features provided by vROps, you can't easily use them, and you can't understand the difference between vROps and SolarWinds and other products.

So I would recommend studying it in detail. After that, you can make use of it, because vROps is a bit complex.

Our primary use case is for monitoring as a service for cloud clients, which generates early metrics that can be detected on time and corrected, the added value that this service has delivered a feature in the form of the cloud of the corporation. The administration is very intuitive, however, you must have high knowledge of management of virtualization components. Additionally, service components and licensing topics must be kept up-to-date by verifying the cost-benefit to deliver as a service aggregated that have this service we deliver as a feature in the form of the Cloud of the Corporation.

The tool helped the organization in all monitoring tasks when being delivered as a service for customers helps them to generate early alarm templates, being a cloud service provider is delivered as part of the IaaS to generate memory consumptions processing and storage additionally can be configured parameters such as networking and services that are configured on virtual machines. The counter you have is the license that must be configured in order to have all the games you have, cloud computing.

The tool has many benefits in the monitoring and template functions to integrate with various virtual machine operating systems in the cloud service. Integrations with operating systems are intuitive and easy to install. The most important value is the value it delivers in a cloud service to generate early alerts in cloud services. In short, this is the most granular value that this service delivers to customers, in the administration part you have facilities for the ease of documentation on the web

The database services in the tool as backup services are friendly and can be deployed in the release to production. However, in the new features, I would like to include more online documentation that can help service generate early alerts. A service provider must be generated and coupled to new technologies, as a service provider we have advanced and generated as the advancement of technology, with the help of Nutanix we have learned to identify several tools and compare them. l can help service administrators generate early alerts, for a service provider should be generated and coupled to new technologies. As a service provider we have advanced and generated with the advancement of technology, with the help of Nutanix we have learned to identify several tools and compare

I have been using vROps for five years.

Technical support is excellent.

We did evaluate other solutions. 

VMware vRealize Operations combines multiple VMware components to deliver integrated performance, capacity, and configuration management capabilities for VMware vSphere, physical and hybrid cloud environments.

I have used VMware vRealize Operations for automating the configuration of provisioning various workloads for our ICT Operations staff.

This has reduced the time required to provision the various workloads thereby improving our service delivery as ICT Operations.

This solution provides for easy monitoring of the ICT Infrastructure capacity.

There is Workload Optimization that has new host-based placement, fully automated mode, and a historical view of all the nodes.

The most valuables features are the collection of assets, security, and configuration data settings from each networked virtual environment in the system. This is very key to our decision making.

The introduction of cross-cloud migration is a plus as this improved efficiency for data center staff. 

Certificate Management should be simplified for non-technical staff members.

There is a need for revamping the reporting and improvement on Dashboard to include statistics, which can be used by Finance people on capacity management.

There is a need for improving integration with other hybrid virtual environments. 

The soultion is very stable.

The solution is very scalable. 

The technical support is superb.

We did not use another solution prior to this one.

The initial setup was moderately complex.

It is a mix, where we use our own trained staff with the help of local VMware Partners. The partners are well equipped and have high expertise. 

A lot can be realized in terms of efficiencies, including improved service delivery. 

There is a need for training so as to get qualified staff to set up the environment.

The initial costs are a bit on the higher side but the licensing is flexible. 

We evaluated third-party solutions such as RackNap.

We use this solution to see what we have inside of the virtual environment. We can see the compute nodes and what issues it has. We can also see the networking, data storage, all the recommendations, the issues, and the compilation as well.

This solution has helped to improve my organization because we use it for reporting when management wants to know what we have in the data center in our virtualization environment. We can just send the reports over the vRealize Operations and it will tell how much we consume in our environment. Also, it can alert us as to what resources we need to buy for the next financial year.

When you open the vRealize Operations, usually it will alert you what the misconfiguration is in your environment and that misconfiguration can cause failures in your environment. It alerts you with more than one type of alert like, blue, red, critical, just a warning, and with a daily solving for issues that prevent a lot of downtime. For example, it will alert you if you have thin provisioning and what's overcommitment in your storage. It will alert you that you are consuming most of the storage and that you will have a coming failure. This helps you to move forward before the downtime happens. 

For the cost saving, it has a feature that will tell if you can provide computer resources to a better machine that isn't being used so you can retrieve back those resources and provide it to another department. It will enable you to efficiently use the resources that you have, more than just wasting the resources of the department. You can retrieve it back, and you will get all of the suggestions from reports in the Operations manager. You will save a lot with it.

The most valuable feature is the feature that alerts you when you have any issues or when you may face any upcoming issues. It can alert you within the day or two days before. It can also help you if you want to scale your environment. It will give you a scalable plan to scale your storage or the compute nodes. You can give it the percentage you want to scale it and it will guide you to have the resources for that.

Usually, we use it for reporting when the management's asking us, without any technical output, they want to know what we have in the data center in our virtualization environment. We can just send the reports over the vRealize Operations, and it will tell how much we consume in our environment.

It is user-friendly. As it's a management product, you usually don't have downtime. It will not impact anything.

They can change the interface for the 6.7 vSphere that would make it more simple and more friendly. I think changing the interface of the operations manager would be good. It's friendly to use right now but it would simplify it more.

It's stable. We don't have any bugs or any issues with it.

VMware always gives us the best support. They are friendly to talk to and they understand the real impact of what's happening. They try to get into the issue as one of your team. They also fit into your working hours to solve your issues. 

We installed it with a partner, Epsilon ITs. It was a very simple installation. We did not request an advanced team. 

We measure ROI by seeing the graph of our investment in the data center for the computer resources, as well on the storage. We see the graph starting to lower because we start reusing the resources that we provide to the other departments. If we have a scale of 30% for every three years, it becomes twenty or fifteen.

I would give this solution a nine. One for the future improvement. 

I would recommend it, and especially if you have a huge environment, it will easily give you a complete view of what's inside and what configuration is in it. 

Our primary use case of this solution is to use it as an operations tool.

It hasn't improved our organization, we have monitoring in place already, too much overlapping monitoring because wasteful operationally.  Also, the learned behavior thing at first sounds like a great benefit, but when an alert is triggered just because a VMs behavior changes, like for example it uses more network than usual and crosses a threshold but isn't really taxing the underlying infrastructure, well it essentially creates a scenario where admins are logging in to address the alert, but its there really isn't anything wrong.  This stuff should be simple and not overly complicated, and in my opinion the product has become overly complicated over the years. 

Reporting is a fantastic tool. It's a great tool for generating reports on different things, and for historically looking at performance metrics to help solve performance problems in an application stack. There are some great uses for it, but I think that VMware needs to take a step back and simplify it a little bit more, without trying to bombard us with everything they can possibly think of. Some of the stuff isn't important, and it's not operationally useful.

I used to use the old version, and I liked the old version before it was rebranded. The interface was more intuitive, it was more familiar with traditional vSphere client type interfaces. When I deployed the most recent version, I logged in and I was shocked that I didn't know where to go to do what I wanted to do. The whole interface is an information overload, it just bombards me with messages, warnings, and alerts. When I follow through on the majority of these messages, I realize that I'm really just wasting time because they're not real problems.

There's a time to live metric that keeps flashing all the time saying things like "Your cluster is only going to have 45 days left before this resource is going to run out." It's not true. It simply doesn't happen. We could run our clusters with these warnings for another two years. I'm not happy with that. I don't want to be warned just because one VM deviates a little bit from what it would be doing on a normal basis. I'll only want to be alerted when that specific VM causes a genuine problem within the physical infrastructure, where it's going to create some sort of bottleneck of performance for a larger number of VMs collectively. There's x amount of bandwidth on a physical network interface card as the traffic flows over it. It's not really ever gonna be a bottleneck until that card itself becomes saturated. I don't want to see an alert about a VM that's running over a network card when the card itself isn't saturated. 

These are things that bother me about the product: information overload, too many warnings that are false alerts. After a while, when I see these things all the time I don't want to act on anything anymore. I don't want to log into the product because I know that when I log into it I'm going to see too much stuff that's just going to waste my time.

It is stable. 

We don't scale very quickly in our environment and we only have fixed licensing to a specific product. Even as we add new hosts and classes, we only use that particular product against the assets we are licensed to use it against. We acquired the VRealize operations bundle in a large purchase, as part of a solution for our SAP environment. It actually monitors all the hosts and VMs associated with our SAP infrastructure.

OK

We use foglight, and I have to admit vrealize is way better, but we really don't spend much time in either product.  We haven't switched we use both to manage different assets

The initial setup was very simple. We have a relatively small environment we were running it against and we didn't have to plug multiple components. We just employed everything all at one server VM stack.

in house

Cant' really say there is one, you buy it, you spend money on it, but it doesn't really allow for a return on your investment, it only burns more of your operation teams cycles just to learn it and use it, and respond to the alerts it creates.  Bottom line, if you size your infrastructure correctly you don't need this.  If you want to stack VMs on the host to its tipping point, good luck no matter what you monitor with.   

The pricing and licensing structure of this solution weren't so bad. Although the larger scales become more expensive because it's a per-socket model and that's the way VMware prices its stuff out. This particular product could benefit from a different model like a per-VM count rather than a per-socket count. We bought it as part of a bundle and we got a good deal on it. 

We have another solution from Dell EMC called Foglight, and it's way worse. vRealize is ten times better than that product. Although they both leave us with too much nonsense to bother with.

I would rate this solution a six.

We use vRealize Operations to monitor and do capacity planning for our clients. We integrate into our architecture's environments. Mission-critical on IBM clouds was announced and so we use vROps quite extensively in all of this architecture.

This solution is intuitive and user-friendly. They improved a lot with the latest release to vRealize Operations, like the dashboards, for example, and the way it works. Now it feels much more user-friendly than it was before.

vRealize Operations offers a clustering feature so you can have a cluster for multiple appliances. It is a master in replica. For example, in case your master goes offline your replica will take over so you will not lose your data, dashboard, reports, and everything you have set up.

vRealize Operations is a really cool tool. It can give you a real and deep overview of your infrastructure, capacity, mutualization, forecasting future, and what you need to plan for. It also has monitoring alerts. It's a pretty good tool, I personally really like it.

This product, of course, has room for improvement. A feature that I would like to see is one that allows you to deploy clusters within multiple geo-locations. At this point, this is not supported and I think it would be really nice to have clusters across two data centers in scenarios when you have storage vSAN.

It's really scalable. You can scale all of the vROps if you have NSX in your infrastructure and you want to deploy something as agents in your segmentation, you can deploy this agent and then you can still get the specific network segment.

Their technical support is great. Of course, they can be better but they're great.

The initial setup can be straightforward depending on what you want to achieve. Overall the deployment of the vROps cluster is pretty straightforward. You set DNS records, set the IP address, then just click deploy and go through the wizard.

I would rate this solution somewhere between a seven and eight. Not a ten because there's always room for improvement.

We initially rolled vROps out for environment health and for the ability to look at the abilities to stabilize the environment. We've actually been able to take advantage of it also with resource reclamation which was a big selling point for leadership. 

The sandbox is a good example of how this product has improved my organization. We had our development team asking for more resources. With vROps, we were able to go in and show them specifically that they weren't consuming these resources. We needed to be able to take these back but during peak times the resources can be given back automatically by the system, in a proactive manner without causing any kind of downtime or any kind of an issue with loss of work.

The resource reclamation is the most valuable feature. We've had issues with our sandbox environment, and reclaiming these resources. Since, it's become a major selling factor in expanding the environment and expanding the client base for vROps.

I have found this solution to be intuitive and user-friendly. Every version that has come out has been better than the last. I am extremely happy with the product.

So far, we've managed to build what we were missing, and that's what one of the nice features with our product. The flexibility with it that was missing in previous versions, is now the ability to go in and define the base variables of our environment so that we can tweak it as we need to, take back what we need to, and give what we need to. 

With our environment right now, stability is the one sticking point. There hasn't been a great deal of handholding in between the different versions, so we've run into problems with there being what I would call "more than just the average change between versions" and it's caused a loss of data for us in the past. 

This solution is most definitely scalable. We've already gone back to the drawing board and specifically designed it from the ground up to be scalable with the size of our environment moving forward.

Technical support has also been a pain point for us. We've had mixed support issues in the past with vROps on stability issues with downtime. Overall, it's gotten better but there still could be some improvement on the GSS side with that.

Having too many monitoring tools is a typical IT problem and the advantage with this solution was that this was giving us the ability not only to check the health of the environment and give operations team a heads up dashboard in order to see the health of the environment, but also have the options for resource reclamation which was a major selling point.

One of the issues that we've had in between the versions is that the set up for it has gotten a little bit more difficult. It doesn't always tell you right away that you'll need to do something different with this version versus a past version which has become an issue. It's now something that we're aware of. From what I've been hearing today, the new setup should be relatively simple in comparison.

We implemented this completely from the ground up, all the way back to one of the older versions. We've used it for the last several years, going through and learning each new version of the product. 

We've had a demonstrable increase in value directly related to the actions of the product.

We also looked at VMTurbo and there were a few other ones for resource reclamation but as soon as we found out that vROps in the newer versions was able to be a little bit more robust, it was the clear selling point.

I would rate this solution an eight. 

Our primary use case of this solution is that it helps us to monitor and troubleshoot our VMware environment.

This product has improved my organization because it has helped us with monitoring and troubleshooting our VMware environment.

The most valuable features would be that it helps you drill down the problems to the bottleneck of where it is which saves us time. We have to give time back to business and we cannot spend hours trying to figure out what happened.

I definitely find this solution to be intuitive and user-friendly. It's integrated with vCenter, so I think it is a good product.

This solution solves our problems. But every time I think it's perfect I come here and they add something new. 

It is stable.

We are from Portugal, so we are small environments, mostly SMB companies, but yes I think it will adapt to any kind of infrastructure.

Technical support is good, once you pass the first level. They know the product like no one else, so they always solve everything. 

We had some monitoring tools, PRTG and some of the stuff from SolarWinds, but it is integrated with everything from VMware. Everything is virtual so, I think it is the way to go.

The initial setup was very easy. We do not have a huge environment, we have eight ESX hosts, so it was pretty straightforward. It was easy to do.

Normally we have a partner or a VMware reseller that helps us implement the solutions.

We have seen ROI because the time we take to solve problems has decreased a lot, so that is the way we give back to the company in the investment.

We have tested some other solutions and they are not as integrated and as easy to manage. I would advise someone looking into this solution that one vendor is always a better option than three or four.

I would rate this solution a nine because normally I wouldn't give a ten. We do not have any problems with the product. It solves our problems. We now know if something is on the console and if there really is a problem. Before this, we had a lot of false positives. It digs into the problems and then at the end it just drops it. 

We use vROps primarily for maximizing efficiency across the boards. We also use it for monitoring servers, seeing where we can gain back some efficiencies, and where we're wasting resources.

This solution has improved my organization by claiming back resources that have been wasted on applications or on servers that just didn't need them. Having a tool that shows that information on a pretty regular basis has been very helpful.

Definitely has reduced time to troubleshoot. You can get a lot of information out of it very quickly, whereas traditionally, you'd be going on servers and pulling out logs and doing it the long way around. Whereas here it is sort of a single pane, where you can access things quite quickly.

The most valuable features would be the forecasting and the ability to see where waste is.

I very much find this solution to be intuitive and user-friendly. It's like all VMware products. Once you know one of them, you can navigate around most of them.

I know that they talk a lot about AI and a sort of forecasting ahead of time. It's a good application, but it has to wait for a certain period of time to actually do an analysis. If it would give you that ahead of time, or even forecasting, it would be really improved.

Has been extremely stable. We've had no outages or any issues with it across the board, since it's gone in on day one.

In terms of scalability, it's grown along with ourselves. We're a constantly expanding company, and it's scaled to fit every time. I haven't had to go back and re-architect it at any stage.

Their technical support is extremely technical. I'd give them a nine out of ten when it comes to technical capabilities. We're constantly upscaling all the time and have to go back and retrain on certain areas. That is a great advantage.

We use a third party reseller, called Triangle Technologies. We have used them for a lot of our hardware as well. They worked hand in hand to bring VMware in.

I would rate this solution a solid nine because there's always room for improvement. I would highly suggest using the product. Its benefits vastly outweigh the price that it costs, the time it takes to implement, and what it can do for your SaS is unbelievable.

We use vROps to monitor and manage our environment. We sell VMware as a cloud to private cloud and to big companies who don't choose to install VMware on their site.

The most valuable feature is the ability to monitor our compute and that it tells us when we must buy new storage or a new host. It finds out what the issue is with big VMs.

It is user-friendly. All VMware products are. 

Stability is good. I don't have any problems with this product and upgrades are very easy because it's just click two buttons and next, next, next, finish.

We can choose the license which is stable and scale out when our company's bigger than vROps.

When you are at your lowest, support is pretty bad. They ask you dumb questions but when you come to second and upper service desk, it is much easier and much better to talk to and resolve the issue.

We weren't previously using another solution. We use Zabbix for monitoring our environment. Zabbix gave us some monitoring issues, but vROps gives us something more, something predictable.

The initial setup was easy to set up. I didn't have any problems with this product.

I would recommend this product from VMware. If you need some analytical tools, I would recommend this product.

I would rate this solution a seven. I don't give tens because something could always be better. 

We are branching into NSX. This solution was purchased with NSX to give us more insight into our environment. We're looking to do a lot more microsegmentation and figure out what the workflows are or what the data flow is between applications and between hardware so that we can minimize bottlenecks, get a better idea of performance issues, and be able to really lock down what we're doing for security. We're also looking to make sure that our microsegmentation is set up correctly and that we don't have data leakage in places that we don't want.

The most valuable feature would be the ability to plug into the data feeds that we have and pull information from physical hardware as well as the virtual layer. The best feature is the visualization of what's going on, so we can take a very quick look and see if there are any issues that stand out.

In terms of being intuitive and user-friendly, this solution is getting better. When we first installed it they had upgraded a few times, and just the overall layout is better and easier to manage. It's easy to learn, so once you get in there and start looking around, it is fairly intuitive to figure out what you want to do.

As they're able to add in more vendors for hardware to be able to pull information from different firewalls, switches, or other vendors, I would like to see where we can get more of a complete view of what's going on in the network. That would make this solution better.

It's a virtual appliance and it's been rock solid since we installed it. We've had no issues with stability.

We don't have a huge network and a huge environment, so I don't see us having to grow it too much in the future. If we do, I don't think it will be a problem.

Technical support has been good so far. All of our VMware support has been really good and it's easy to get our questions answered. We have a technical account manager as well through VMware which helps. If we need first line support for things and additional help, he will get answers for us faster. It's been great.

We weren't previously using another solution. Other than just general NetFlow products, nothing really shows the visualization of the network flow like what we're seeing with Network Insight.

The initial setup was fairly straightforward. There were instructions for it that were easy to follow. There's video tutorials and things like that online, so it was fairly easy to set up. We didn't need any support to get it installed.

We haven't really seen ROI yet. We haven't been using it that long and we're still building out our NSX environment. The visualization of what we're doing and what it provides is a good place to go and see so we don't have to use multiple tools. It consolidates multiple things into one so that makes my staff and the network team's job easier.

I have seen the demos and what it can provide is fantastic. It more than makes it worth it to use the product. I would rate it between a nine to ten.

Our primary use case of this solution is that it enables us to show value to our customer. We show them how they can get the most out of their state. It also shows us our investment and what we can do better to enhance our environment to get the most out of it.

This solution has improved my organization because we work with several other companies and we've seen them automate more of their workloads, get better visibility of their workloads, and get further insights into how their databases are operating. 

It has reduced the time it takes to troubleshoot issues. We have customers trying to pinpoint and isolate issues using vROps. The information it provides helps them to pinpoint the issue a lot faster and resolve anything a lot quicker as well. They have a lot less downtime. 

The most valuable feature would be that it can show us how to get the most out of our infrastructure, how we can scale, and what will happen in the future, over the next twelve months. 

This solution is intuitive and user-friendly. It's pretty easy, just plug and play.

The integration points can use improvement. We currently use a lot of third-party management packs to get insights for SQL, HP, or Dell EMC. If we could have more integration built in as a standard feature that would make it slightly better. 

It's very stable. I haven't seen any downtime. Usually, it's deployed using a redundant pair. It works really well. 

In terms of scalability, I haven't yet hit the max instances and I don't think I ever will. 

The initial setup was pretty easy. It's like setting up any other VM. It's a few clicks and you're ready to go. 

This solution offers a sixty-day free trial so I would advise someone considering this solution to give it a go. At the end of the day, you won't lose anything, you get to play with the product. Make sure to get your technical guy in early to help support you.  

I would rate this solution a solid nine because there's always room for improvement. It's a very good product, very easy to use and it has great integration points with other VMware products. 

We use vROps to gather all of the information about the infrastructure. We have a huge infrastructure which means that we need a central location where we can find anything and any kind of data. We also massively use it for reporting. 

This solution has improved my organization because it's much easier to keep track of installed software versions. 

The most valuable feature would be the reporting function and the central location for everything. We need reporting for all of the components.

This solution is intuitive and user-friendly. It has evolved pretty well. It wasn't that simple in the beginning but now it's getting better.

The speed of the user interface and the upgrade process of the components are features that I would like to see included in the next release. 

This solution is stable. It has improved a lot. 

We use one of the largest installations of vROps and it is scalable. 

VMware provides good support. We are a GSS customer which means that we have global support with a dedicated engineer from VMware's side so we have no issues with support. 

We use a large installation of this solution with multiple nodes and so the setup was pretty complex. 

We haven't seen ROI yet. It might come later.  

I would rate this solution a seven because it's not the best it can be yet. It has room for improvement but it has definitely evolved to become above average. 

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.

Our primary use case of this solution is for collecting performance metrics and also for troubleshooting some performance issues. 

The most valuable feature is how our metrics interact with each other. You can find what objects are needed and get all of the information about an object: How it works with the storage, CPUs, memory, and you can get an easy way to find the solution during troubleshooting.

It is intuitive and user-friendly starting from the latest versions, especially with version 6.5. Previously, we had some issues with the stability with such obligations but now it's useful and stable. 

Our internal infrastructure was changed and now it's an absolutely different interface. It has absolutely different uses and dashboards. Sometimes it's difficult to find some features like they were in previous versions but it's coming with the times so for now, I don't think it's a big problem.

I think about how our infrastructure will grow and how we will manage with the application. It can grow at any time, there's a huge amount of new options and new hosts, but the console and the server stay the same. 

We mostly use this solution for troubleshooting because just getting information from vCenter is not enough. In vCenter you have information about the current state so a lot of the metrics are not collected but if you need to collect more metrics, you have to expand the level of collection. We would like to get a separate solution.

We tried to use Veeam ONE one for monitoring but it's a bit difficult. It's a different project and has different ways to manage it. Previous versions of vRealize did not have the same features as Veeam ONE. Now, it does have the same features and much more. 

I would of course recommend this solution to someone considering it. The new versions are simple, useful, and expandable.

I would rate this solution an eight. I wouldn't give it a ten, but I know that vRealize Operations provides API. You can get anything you need from API, not only from the dashboards.

Our primary use case of this solution is for monitoring our VMware infrastructure, vCloud Director, and NSX Manager. 

vRealize has products created especially for virtualized infrastructure by VMware. Its main features are great.

I don't find this solution to be intuitive and user-friendly. It's a large and difficult product to learn. We need to search for more information.

I would like to see them add customizable dashboards and customized views. 

I find this solution to be stable. 

It's very scalable. It's fast and fast is easy.

The initial setup was complex. 

I would rate this solution a nine. 

We use vROps for our many VMware infrastructures. It is mainly for IT operations because we're processing a lot of information. vROps is good for us for reporting and for monitoring hosts and VMs.

The most valuable feature would be the reporting because if the frame or something is not syncing or we have an issue it will report it to us and give us a warning.

I wouldn't say that this solution is user-friendly. You need to know a lot of tricks to know how to use it. It's quite buggy and quite slow when it comes to loading.

They should improve on the speed, first of all, because it is slow to load and then you can't use it at all and you need to keep refreshing the browser. They can also improve the GUI, like the placement, some buttons here and there. In short, they should make it simple.

Stability isn't bad. Not perfect but not bad. 

Their technical support is good. I am happy with them at the moment. 

Overall, the initial setup was straightforward. There are many ways to do this life cycle. We have many different views.

I would rate this solution an eight. It serves its purpose but it has room for improvement. For example, vCenter has Flash version and HTML5. HTML5 is really, really good. It's fast and good. If they can make it simple like this it would be perfect. 

The company I work for is Sureskills. We're a consultancy based company. We have multiple customers that we sell a lot of virtual products to. We don't just deal with that. We deal with a lot of Microsoft, Stack, and Dell EMC products as well, but we do an awful lot of VMware based products. 

Our primary use case is two-fold. From one perspective it gives the local on-site IT people some ability to see what's happening with their virtual state and let them know if there's any issues or problems that may be starting to come to the surface. Secondly, from our perspective, because we provide support to these companies, it allows us to quickly see from a number of different reasons why there would be issues from this. It's useful from both sides.

The most valuable features would be that it gives us a breakdown on the ESX host and then the virtual machines themselves. Also, with some of the add-ons that they provide with vROps you can start to see if there are any issues with things like Exchange Infrastructure or SQL add-ons, etc. It's useful to get from the hardware perspective to the virtual machine down to the actual application that's running on those VMs themselves.

I do find this solution to be intuitive and user-friendly. You could set vROps up in an hour and start to get some statistics from it. It's a very simple tool to use.

I would like to see improvement from the application layer. They have add-ons for SQL and Exchange. It would be nice to see some additional application support being developed further down the line.

We haven't seen any downtime. From our perspective, we haven't seen any issues with vROps in itself. It's simple to install. It's very easy to operate, so from our perspective, we would see it as a natural add-on to anything in terms of the virtual infrastructure.

Even if you're a small to medium size business and you have 50 virtual machines or if you're a large company with several thousand virtual machines, the solution works across the board for all.

Their technical support is outstanding. We would deal with VMware on a fairly regular basis for our customers, and possibly because a lot of the support is based in Ireland, we would have a fairly good relationship with them and they're very good at getting back to us very quickly.

The initial setup was very straightforward. From the web interface, you can literally just go straight into actually installing vROps with very little previous knowledge required to get it up and running.

I'm not sure about return on investment per se, but certainly in terms of being able to troubleshoot and identify issues quickly and in a timely manner which further down the line may have caused an issue with the production infrastructure. It's intuitive from that perspective, that it allows us to deal with issues before they become a problem and that could cause an issue down the road which would potentially impact on costs for our customer.

They compare reasonably well to alternative solutions. There are several products that are out there that would manage a virtual infrastructure for customers, but we perceive it to be the best of the existing range of products in that area.

I would rate this solution a nine out of ten. 

Our primary use case of this solution is to monitor the server and desktop environment. We've never had a performance issue.

It has helped our organization because we can keep the metrics within our ratios. In this way, if something jumps out we can be on it right away. It has also helped to reduce troubleshooting time. 

The alerting feature would be the most valuable feature for us. It gathers more metrics. In the latest versions, there are metrics that are being exactly captured with vCenter which are a bit better. Aside for that it provides a historical analysis of metrics over time. 

We did not find this solution to be intuitive and user-friendly compared to other options. We actually ended up paying for something else to use in conjunction with vRealize. 

I would like the ability to edit more stuff in the standard version. The way it is now really limits the usability, especially because the dashboards don't fit everybody. Aside for that, creating reports and views needs to be more intuitive. Right now it's too hard without having had a lot of training. 

It's pretty stable, we've never had any issues with it. 

Their technical support is okay, it could be better. 

The main points that we look at are the costs and ease-of-use. Ease-of-use is the main thing for us because if we can't get the data we need it's not going to be helpful to us. 

We looked at Foglight, vRealize, and Veeam. The main reason we chose vRealize is because it's included in our license. 

I would rate this solution a five. There's a lot of stuff that we'd like to do that we can't. 

I would advise someone considering this solution to take classes and get a lot of information because this solution may look simple but it's a lot harder than it seems.

Our primary use case of this solution is to gather analytics. We don't use it very often but it's working and collecting data. 

It has helped my organization by running analytics on use cases, performance, and by running clusters. It has also helped reduce the time it takes to troubleshoot issues for the VDIs. 

I find this solution to be intuitive and user-friendly, for the most part. It's the type of thing where if you don't use it, you lose it.

I have found this solution to be stable. We have never had any downtime. 

I've never had an issue with scalability. 

We've had to use their technical support and we've found them to be great. 

I would rate this solution a seven. We don't use it enough for me to give it a ten. There's a lot of value to it but we don't fully exercise it. It's a great product depending on what everyone's needs are. 

Our primary use case of this solution is for the performance monitoring. It's been performing well.

It has helped our organization a great deal in terms of being able to identify and troubleshoot problems. The time it takes to troubleshoot has been reduced. It has also helped with its capacity planning features.

Various metrics that we have for all the particular performance features, like CPU monitoring, memory, storage and so forth are the most valuable features for us. 

I also find this solution to be intuitive and user-friendly. Their feature set is very good. 

I would like to see them add a little bit more functionality and the ability to create more dashboards.

Stability is good. We haven't had any major issues with it. 

Scalability is pretty good. The fact that we can actually use it to expand on other aspects of it by adding additional packs is really good. 

We have rarely needed to use their technical support. They're pretty good. 

I was involved with one out of two of the setups we did. It wasn't very complex. We had a little bit of trouble in the beginning but nothing was significant enough that prevented us from moving forward. 

When selecting a vendor reliability and ease of setup is something that is very important to us and are the reasons why we proceeded with this solution.

I would rate this solution as an eight and a half. I would tell a colleague who is considering this solution that it's worth investing in. 

The analytics and operations management are our primary use cases of this solution. It's been performing well. 

The ability to analyze optimizations, the performance, and balance have all helped my organization. 

It provides my team the awareness to see what's going on with the nodes and the clusters. It will then either rebalance them or allow the automation to rebalance them for us.

The alerts and awareness would be the most valuable features for us. 

I have found this solution to be user-friendly and intuitive. I also like the integration point and that it's a single pane of glass.

It's very stable. 

Scalability is good. I've used it in previous versions and I'm looking forward to using it in the current version, 6.7. I think it's phenomenal. I look forward to the product growing even further. I understand version 7.0 is coming out soon.

I haven't had to use technical support for this version but I have had to use them in the past with other versions. There have been some challenges with them. It's hard to get through to the right person and resolving issues in previous versions was hard. 

The initial setup was straightforward. 

Our primary use case is to monitor the performance of the virtual machines as opposed to monitoring the performance of the OS. We'll monitor OS and stop at the OS, whereas vROps will pick up what's going on underneath. If the datastore is having a problem, it will bubble up to the VM and show us that.

It has allowed me to give the developers insight into what's actually happening underneath the covers. They used to only be able to see their app and now, they can see underneath. We've also given them access to see into the OS and we've given them a full stack view of how their application is performing.

It has helped to reduce the time it takes to troubleshoot issues and has improves quality of service to our users. 

The most valuable feature for us is the one that allows us to take over the DRS within vCenter and does it more intelligently. 

We have found it to be intuitive and user-friendly. 

I would like to go back in history on the performance data and blank out some of that performance data so that it isn't used in calculations. For instance, if an application goes wild and uses up all the resources, I don't want that to be understood as that VM needs more resources.

Stability is fine. The only issue I've had with it was an issue that I myself caused. 

We're not big enough to warrant scalability. 

Their technical support is good. They found the problem quickly. Support gets back to us quickly. When you raise a support call they don't get back to you with a candy email, they actually get back to you and help. 

The initial setup was very easy. 

We looked into a competitor but it was way too expensive. The fact that vROps came as part and parcel of the vRA enterprise gave us a huge win on the cost. 

I would rate this solution an eight. 

Our primary use case of this solution is to monitor our systems and capacity planning. It has been performing great. It's a little bit of a beast to run sometimes, a lot of knobs and dials, but it runs well.

The biggest benefit to us is that it shows us where our pain points are; where we need more storage, where we need more network or bandwidth, where we need more CPU or more memory. We know where our problems are before they happen.

It has helped reduce the time it takes to troubleshoot issues and has improved the quality of service to our users. 

The most valuable feature would be the capacity planning. I can see where we're at as far as usage on our data stores, our CPU and memory. It lets us know where we need to grow. 

We haven't found it to be intuitive or user-friendly. We're on version 6.0, it's gotten better since but there's a lot of things we have to do under the hood to make it work how we want it to work. It doesn't work out of the box very well until it's been fine-tuned.

I would like to see a better interface, something that's more intuitive, one dashboard that shows everything I want to see on. The dashboards that come with it are focused on certain things that aren't the big picture. I'd like a dashboard that does everything faster and also a faster web interface.

It's very stable. It's a beast to get configured but once it's been configured it's easy to use. We don't have any downtime from the product itself. The initial configuration is quite painful. 

It scales very well. It's designed for huge operations, so when it's used for a small company, it's not quite suited for their needs. It takes a lot of time to figure out and to make it work for your needs which is why it's precarious.

Their technical support has been very good to work with. They help us get to where we need to go pretty fast. They're very knowledgeable. 

We bought some tools from vCenter. We had to go through all the logs yourself, all the metrics ourselves. It tied into our UCS system that we had attached to our UCS, Hitachi system, and vCenter system. We could all the stuff in one pane of glass, which is nice, but it was one of those things that we had to do a lot under the covers to make things work for us.

The criteria that we look for when we evaluate a solution are functionality, price, and feature set. 

The initial setup was complex. There's no wizard to install it. We have to read a lot of documents then there's a whole other guideline to install the next part. There are a lot of steps. The documentation was great but there's a lot of pages, around three to four hundred pages of documentation. 

I did most of the installation myself but called support when I needed help. 

We have seen ROI with this solution but it's hard to monitor. 

We looked at ManageEngine and SolarWinds. We chose vROps because we're a large company and they gave us a good price cut. Also because the feature set looked good from the demos. 

I would rate this solution a seven because it's complex. The new versions are a lot better.

If you're considering vROps I would tell you do first do your homework. Make sure that you're ready and that it's going to fit your needs. Make sure there are full-time employees to manage it because it's not something that you just set up and go. It's got to have someone to babysit it and maintain it. Somebody needs to take care of the many different dashboards and functionalities. 

Our primary use case is to automate redundant tasks. We're limited to two guys, so automation is beneficial. We'd eventually like an implementation of ServiceNow later down the road.

The most valuable features for us would be the automation of the redundant tasks. The implementation of ServiceNow is huge for us as we are essentially a cloud provider to the campus. It'll allow us to automate a lot of tasks that constituents need done.

I have found it to be intuitive and user-friendly. From what I've used it, it's been easy.

ServiceNow implementation is rough. 

Stability so far has been good.

Scalability is one of the reasons we really like this solution. It's very good and it scales great. 

I rated this solution an eight because it's intuitive and easy to use. The features that it'll bring us are tremendous. It's going to be like having extra people on hand. Automation is a powerful tool that we're looking to use that'll make everything a lot easier. 

Our primary use case is for the developers to test code. Our customer care uses it to troubleshoot customers' issues. We also have a training business unit and they use it to deploy classes for customers to train. We've been using it for four years and it has been performing well. It does the functions that we need it to. We do have some issues from time to time. We're looking for more maturity out of the product but it's getting better with every release.

It has increased the speed of VM deployment. A normal server request would come in, it could take anywhere from three to four days to deploy and now within 15 minutes they can click and have something up and running. IT support for developers is nice as well because they are able to manage the environment themselves.

The self-service feature is one of the most valuable features for us. It gives the end-users the ability to deploy their own machines and so the administrators are hands off at that point.

We have found it to be intuitive and user-friendly. It requires minimal training to get them up and running to start deploying and accessing machines. 

I would like to see them update the format of the catalog in a different way. There's no option in a lot of the contents for the virtual machine blueprints to change the view.

Stability does go down from time to time. We have had some issues with the appliances sometimes and we have to do reboots in the middle of the day which affects the ability for them to deploy. Now, there's no downtime for existing stuff that already deployed, but it does keep them from deploying at that time.

Scalability is nice. We have it deployed in a highly available environment and scalability is nice because we just add another ESX host and we are able to increase the capacity there.

Their technical support is helpful. Sometimes they can take a little while to get back to us. 

We were using a lab manager before that and that was decommissioned so this was the next solution for what we needed. We needed to have a self-service environment for our developers, customer care, the ability to deploy machines, destroy machines, complete the entire VM life cycle and it does.

The initial setup was very complex. We've been using it for a while now and realized that it's pretty logical. Upgrades are pretty straightforward. We had a lot of problems originally deploying it, between some certificate issues, but we had an engagement with VMware so they were able to help us get a poof of concept environment set up as well which was helpful.

The deployment can be complex so I would advise someone looking into this solution to engage professional services to set up a proof of concept environment and to evaluate it. 

I rated this solution an eight because we've had issues with the stability and the appliances. Other than that, it's a solid product. It does exactly what we need it to do and we're happy with it. 

We primarily use this solution to look at our workloads and determine where there's an additional need for space or capacity needed as well as how to optimize it. We've been using it for a few months. 

It has improved the way my company functions in the way that it quickly identifies problems and addresses them. We're still relatively new to it so we haven't used it to the right size. It addresses problems that we see and then we're going to eventually get to the point where reducing capacity where needed will help.

Troubleshooting is one of the most valuable features for us. It identifies problems that other monitoring solutions give us, offers insight into the problem and then digs into it and finds out what the actual problems are and addresses them.

We have found this solution to be intuitive and user-friendly. The dashboards on the home page are easy to navigate. Once we log in, it's easy to find what we're looking for and to see immediate problems.

Stability is good, we haven't had any issues with it. 

The solution is intuitive so I haven't had the need to use their technical support.

I rated this solution a nine because I haven't had any issues with it and it has been intuitive and easy to use. I don't know it well enough to give it a ten.

If you're considering this solution, I would advise you to consider it and to look at your environment to see how it can assist with troubleshooting. 

Our primary use case is to have everything on one dashboard in which we can look after our operations and get alerts.

It is easy to see when something has gone wrong. We just have to go in and fix it. The reduced time it takes to spot and fix an issue has improved my organization. It also saves the amount of resources that we use to fix an incident

We have found the integration with VMware to be one of the most valuable features. It's also easy to use. The interface is really clear and when there is an issue the color turns red.

I'm quite happy with the path that it's going on, so at the moment, I can't really recommend anything that this solution can improve on.  I'm pleased with where it's going and the new features that are coming.

I'm really happy with the stability. I haven't seen any issues with it at all. 

We're really happy with the scalability. We've deployed it and it's looking after several VMware instances and it hasn't had any issues. It gives us all of the information that we need. 

We haven't had to use their technical support. 

One of our managers presented vRealize and we really liked it. It has better features than other alternatives. 

The initial setup was straightforward. We used an integrator and they did everything for us,  there were no issues. It was just a case of going in, looking around, learning it, and just getting a little bit of initial help for a few days. It's been fine since.

We also use SolarWinds, AppDynamics, Nimsoft, plus vRealize as well. We're trying to make the company all go for one thing, but it's been a bit of a struggle. We'll be pushing it.

I would rate this solution an eight. It's a good solution and I like it. I haven't explored it enough to be able to say that it's a perfect ten. 

I would advise someone looking into this or a similar solution to consider vROps. Have a look, try it out, and try some demos. I think it's a really good product. 

Our primary use case is to see what's going on with the complete infrastructure and to be able to see if there are any issues. Although it's not in real-time, we still use it effectively. We can see what the state of our environment is.

It has improved our organization by saving us time that it takes to look things up. We have everything on one dashboard.

It has helped reduce the time it takes to troubleshoot. We're using the vRealize Operation Manager, and when there's an alarm we can have a look, drill down, and see exactly what the issue is. They will usually have a suggestion from a knowledge-based article that will suggest how we should handle the issue. It saves quite a lot of time. Rather than having to go and have a look on Google or somewhere, we can find a solution in the Operations Manager. 

I like that we can see what amount of the CPU has been used and what's been handed out. We can see how we can bring the virtual machines in line with what actually has been used which has saved us cost.

It is user-friendly although there's always room for improvement. In the beginning, it was about figuring out where you can find what, but once you know it, it becomes easier to navigate. 

Stability is good. I haven't had to restart it at any point. 

It's scalable. We can add a new host and they immediately become available. 

Their technical support is excellent. 

We chose this solution because we are using VMware, and the rest of the suite, so it was just a logical decision to go with Operations Manager.

The initial setup was a bit complex but not really complex. If you take the time to look through the documentation you can figure it out. 

We deployed in-house. We just had to look at the documentation. We tried it in our test environment, found that it was doing what we expected it to do and we deployed it in production.

Our ROI is that I can spend less time looking at issues, it's all there in the dashboard. I can see them immediately, I don't need to go into vCenter and go through all the different data stores. I can just have a look at the dashboard, see if there are issues, see where the issues are, and save time.

I would rate this solution a ten. I was looking for a solution that would help me do my work and this does exactly that. 

I would tell someone looking into this solution to go for it. 

Our primary use case of this solution is for the capacity planning and also for the monitoring.  It has helped us get a clear view of the infrastructure. We spoke to people from VMware and realized this was the right solution for us. 

It has helped our organization because now we have been able to reclaim about 40 percent of our infrastructure resources.

It has also helped us reduce the time it takes to troubleshoot issues. It helps us pinpoint the locations of the program which allows us to reduce the time it takes to figure out a solution. 

The dashboard is a valuable feature for us as well as the personalized reports. Our management doesn't really care about the incident, rather they care about the reporting so it's a good tool for us.

At first, it was not so user-friendly because there was so much information that we were lost. Now, we can use it very powerfully. After we played with it for a few months it became easier to use.

Stability is very good. 

It's very scalable. It has many capabilities. We only use around 30 or 40 percent of the tools, we still have to evolve with it. 

Their technical support is good. We haven't had too much use for them. 

We are public services, so we talk to all the companies that want to work with us. Sometimes we can have more than ten companies that we work with so we just talk to them and we consider different factors like budget and from there come up with the right solution. 

The initial setup is not complex because we had a team help us and they helped with the beginning of the installation. Around one hour after we could already start seeing what we could do with it.

We implemented in-house. 

I would rate this solution an eight because we don't know how to maximize all of the features. Once we do, maybe it'll go up to a nine.

I would advise someone looking into this or a similar solution to first analyze your infrastructure. Take a look at what you need and then directly focus on your objective. This way you can maximize the solution.

The primary use case of this solution is to monitor the user experience of our VI in finance and troubleshooting.

It helps us make occasional reports and with that information, we can react proactively. It has also helped us reduce the time it takes to troubleshoot issues. 

We like that we get reporting on our sizing reports. 

I would like to see them develop real-time capacity meters.

We did not find this solution to be intuitive or user-friendly. It's complex and overwhelming. It takes time to learn how to work it, which metric is in real time, and what information it's giving per day.

We found the stability to be good.

Scalability is good. 

We've had to use technical support and we've found it to be fine. We have a team in our company so we can ask all of our questions to our technical account manager. 

We knew it was time to switch to a different solution because the engineers were complaining. We knew we could not see everything on the platform. 

The initial setup was straightforward. In our company, we have a service provider and iOS platform, and they built the application.

We integrated in-house. 

We get fewer complaints. 

I would tell somebody looking into vROps or a similar solution to get someone with in-depth knowledge to help you with finding your use case. It's very important to set your expectations, know what your KPIs are. This will help you better navigate the solution.

I rated this solution a seven because it's complex and not intuitive. It has a long learning process. It can be frustrating trying to get the correct information from it. 

Our primary use case is to manage our huge VMware infrastructure based on the public and private cloud and dedicated infrastructure. We use it to see if the VM is a good or bad size and to see if we can reduce the cost. We also use it to adjust the memory, and CPU, and to increase the network storage.

The most valuable feature is the ability it has to adjust the efficiency inside the infrastructure.

We do and we don't find this solution to be user-friendly. It's intuitive because in a manner of a few minutes you can see the value. It's complex to manage because there are a lot of options and metrics. It's complex when you want to do something very specific.

I would like to see them implement multi-tenancy on the product itself and the option to manage it in one team. At the moment some of the objects are only available to one user and I'd like for it to be available to the whole team. 

It's quite stable. We've had one or two issues due to storage space used by the solution because there is no specific agent for monitoring the solution from the outbox.

Scalability is quite nice.

We've never had to request support for this solution. 

We didn't use a solution previously to this one. I think it's the best solution on the market in terms of capacity monitoring. I didn't find a similar solution with the same amount of capacities. This solution was the only one that was on the shortlist because the tool is not concurrent to monitoring tools.

The setup was straightforward and easy.

We deployed ourselves and we also provide service to our customers with this tool.

I would rate this solution a nine because I think that the tool is very powerful and we are very happy with the product. I couldn't imagine finding a similar product that would have the same abilities as this one. 

If you're looking into this or a similar solution I would advise you to do VMware's training on it because it's the best training I have had with VMware. I always refer back to the information I got from the training.

We use this solution to determine what systems are being utilized and whether there are issues with VMs.

It has improved our organization because it allows us to be proactive in regards to catching systems prior to them becoming a critical state.

It has helped improve the quality of service to users. It's made sure that we don't have servers that are over-subscribed with storage that starts to end up being at the minimalist points. 

It helps us to determine, over the course of time, whether we need to supply more hardware, memory, or storage.

For the most part, we have found it to be user-friendly. It has gotten better over time since the first version of vROps that I used. The interface has really improved since then. 

I haven't had any problems with stability. It has been fine. 

We haven't done a lot in scalability since it's been implemented. 

We haven't had to use their technical support. 

We had an option of using this solution or not and our group chose to move forward with it. 

After a few earlier iterations, I think the latest version was very easy to deploy. I didn't have to problems with the setup at all, it was very easy. 

Not having any downtime is always a return on investment.

We use a multiple-monitoring solution but vROps is more tailored towards the environment that we use. We use both solutions hand in hand. The monitoring solutions that we currently use notify us of any issues and whatnot. We use vROps to tell us what the VMs or servers are doing over time. 

I would tell somebody looking into vROps or a similar solution that it's a good product. I haven't had any problems with it. I want to continue using this product moving forward and I would definitely recommend it to a colleague.

I rated this solution a nine because we haven't had any problems with it. It has provided me with the information that I've needed to make sure that our environment stays stable and it provides our users with the needed applications.

We are using it to monitor our whole infrastructure, integrating SAP, and using the Madura plugin. We love it.

Using a single pane of glass, we can view what is causing the issue.

Before we used the tool, when we had performance issues, a lot of people looked into their pieces and finger-pointing happened. Now, one person can look at the full overview of their infrastructure, and say, "Here's the problem. Have a look here."

We have all the information that we need in one place and don't have to search for our monitoring tools everywhere.

The solution is intuitive. You don't need a week of training. If there is an issue, you can intuitively find it. 

We would like to have monitoring for containers.

It is stable. The solution works.

We have thousands of RAMs and thousands of hosts on it. 

We started small, and now, we are a big company. It scaled.

I have not used the technical support because the solution is stable.

We did not have a previous solution.

We used the company, Fleet, for the deployment. They were professional and the solution works perfectly now.

We did an enterprise license agreement with our VMware partner and put this in our bundle. We tried it and loved it, so we use it now.

Try it. Or, you can start small and use it.

It makes our life so much easier.

We use it for monitoring of the VMware environment. 

It has performed well. Though, I haven't found time to dig deep into it.

Because of the recommendations in the product for configuration changes, bad legacy setups become visible using the tool, which is great.

You receive both the overview and the details.

It's user friendly, but a bit complex, so you need to spend time with it.

As far as I have seen, it is very stable.

We have a small size setup.

I have no experience with the technical support.

We received the product as part of a license upgrade and decided to use it at that time.

The initial setup was very straightforward. We spent a few days setting it up, then it was up and running. We haven't done many changes since then.

We did a basic setup with a large European reseller of VMware. They were great, as it was a quick turn on solution for us.

We have another monitoring tool which we use for physical servers and virtual as well, but vRealize Operations Manager gives us more detail. It's best of breed when it come to monitoring.

Don't underestimate the time for getting it in place and in tune for your business. Even though it's pretty much turnkey, ensure you have enough time to focus on getting it tuned for your environment.

It is a good product, but our company has a lot of tuning to do with the product.

We use it to monitor our system and optimize performance.

It visualizes stuff better, so we can pinpoint or see problems. However, I feel as though there is a lot of potential in the product that we haven't utilized.

The most valuable features are the trending and analytics.

When you deploy it as a single node, it's more stable than if you have multiple nodes. We've had some issues with this.

Scalability is good, but I haven't tested it that much.

I have tried the technical support.

It is pretty straightforward.

I would recommend NSX. From my experience, the solution is pretty good.

We use it for making VMware assessments.

I am a system integrator, so it's not implemented in my organization. I implement it in other customers' organizations.

I can install it in 30 minutes to an hour. In about two hours, I have data to give to my customers. In about a week, I have reports to give to the administration, so we can decide which products that they can farm.

• It is easy to install the product, so we can make it available to our customers. 
• It provides good insights into a client's infrastructure.

I would like the product to be more interoperable with other solutions: more hybrids.

It's a very stable product. I don't have any problems with it.

It is very scalable.

I would rate the technical support for this solution an eight out of ten.

This is my first solution of this type.

The initial setup is very straightforward. It is very intuitive to install.

I am an integrator for this type of solution.

I have reduced the time to troubleshoot for my customers. This solution can be used towards a problem that has been existing in infrastructure for months, and no one know what is. Then, in a matter of minutes, I can find the solution and provide it to my customer.

Install and use it. It is a very good, though it needs a few tweaks.

We mostly use it for debugging or troubleshooting when some application doesn't work. We can look at the vRealize Operations Manager and troubleshoot from there. 

We also use it for capacity planning. 

When we have problems with applications, we are fast with troubleshooting because we use vROps.

The solution has helped us a lot to troubleshoot issues and improve quality of service.

• It has many types of metrics.
• The dashboards are very easy to use.

vROps is user-friendly. You have custom-made dashboards, which are provide by VMware. You just configure them, and it works.

We had some problems with updating it. The two times that we upgraded vRealize Operations Manager, we lost all our data.

When we not updating vROps, it works perfectly.

Scalability is great. We have two instances of vROps, and we haven't had to scale it yet.

We haven't opened any cases yet.

We did not have a previous solution.

The initial setup was straightforward.

We would like to build custom dashboards in the standard license. Right now, this is available in the enterprise license, not the standard license.

We used Grafana to monitor our environment. With vROps, you have all the VMware specific metrics and dashboards. It's much harder to invest time in another solution where you have to build it on your own.

We just considered vROps. Grafana was something that we designed on our own afterwards.

I would recommend vROps.

We use it to obtain an overview of what is happening in our cloud infrastructure, e.g., our utilization, trends, and how long before I need to upgrade my hardware,

It removes the guess work. It gives me real data and analysis in a very user-friendly way that I can show to my management without going deep into numbers. It hides all the complex numbers and visualizes them into very nice, full-looking colors and graphs. So, it makes it easy to use.

Trend analysis: It gives us insights into problems which will happen in future.

It would be nice if it could tell me more about my hardware, if there were any updates on the network that should be deployed, if some firmware needs to be deployed on the server, etc.

The stability is excellent. It has never crashed, so I have no complaints there. It just works forever.

We have a small setup. So far, I haven't tested it on a large networks. However, for our setup, which is a couple of servers, it works fine.

I haven't called the support for this solution.

I was not using a solution previously. We got a recommendation from VMware to try this product, and we loved it.

It is very easy to set up.

As integrators, we deployed it ourselves.

We have seen good ROI results. It has made our lives easier. We have a 100TB storage, and it gives us an overview, including databases, how the storage is being utilized, etc. It makes it very easy to find information out.

I haven't used a competitor's product.

Only VMware was on our list because we were already using all the other VMware solutions, like vSphere, NSX, and vCenter. Therefore, we wanted something to run on top of those products, preferably from VMware, so it could integrate in a better way.

I'm happy with it. It does all what it promises and helps us.

We are a VMware partner and integrator, so we deploy it to a lot of our customers. We love promoting this product to all of our customers.

We use it to gain more insight into our environment, with a simple, easy-to-use interface. We are a small team looking after a very large environment and without it we would be lost on a day-to-day basis.

The insight that we get from all our vSAN clusters is probably our biggest use case, and where we get the most use out of it.

We're a pretty lean team. Like most organizations, our training budgets are tight. Without an intuitive product like vROps, we wouldn't be able to get the insight that we do into our environment on a day-to-day basis.

The integration with the rest of the vSphere product suite is the most valuable feature, as we are a big vSAN user. It is fully back integrated into the vSphere Web Client, and we're getting all vSAN analytics that we need.

Stability has been bombproof, as far as we are concerned. We have never had any issues with it.

We have in excess of about 2000 hosts and had no issues from a scale point of view.

We have not used the technical support.

We weren't using anything else previously. It was the case that we were missing a monitoring solution, and this solution was the obvious fit because of the integration with everything that we already had in place.

The initial setup is straightforward. The installation process takes you through in a simple, easy to deploy manner. We were had everything up and running within the space of a day. Then, we have just evoled the product ever since.

We deployed it ourselves.

Our budgets are always tight. We would like to have more features at lower licensing levels for easier access to them.

From a hardware point of view, we looked at SolarWinds. They have a good offering, but the integration is lacking from our point of view. We needed something that would just work without having to put time and effort into it.

I personally have used some of the other solutions in this space. I've found that you tend to have to put more manpower into getting them up and running. This is what drew us to vROps.

Don't knock it because it's a vendor-specific solution. It does do what it says on the tin and helps us on a day-to-day basis.

We use it for proactive and reactive monitoring. 

I just came off a contract where capacity management was a major issue. They hadn't planned for it or made any provisions for it. So, they were looking at the operations teams to sort of do capacity management for them. This project came along, I picked it up, used vROps, and was able to say, "This is what's going on. This is what we are going to have to do. This is what we need to do to be where we want be."

Its ability to resolve an issue from within the application rather than going somewhere else to resolve it.

The dashboard is a single pane of glass for troubleshooting.

I've never had an issue with stability.

It is very easy to scale. However, in the beginning, I picked up an implementation that had been designed wrong from the ground up.

Ideally, somebody using the technical support when I found out the configuration was incorrect.

I still received a lot of help from the support agent who dealt with my case. What he couldn't do was tell me what to do to bring it back into line. However, he told me what it needed to look like, which was very well documented anyway. Though, having someone point you in the right direction can be a good thing.

The initial setup can be complex, but it is not too complex for me. I consider it straightforward.

We are an integrator.

We have seen huge ROI. 

It has certainly reduced troubleshooting, especially when we have less experienced support technicians than engineers looking at it. It guides them as to where to find the solution. Now, I have a lot less junior staff coming up to me asking what has gone wrong because it displays on the dashboard what they can do to resolve it.

In terms of integration, between this product and everything else in the VM product line, it is very easy to just pick this up as opposed to looking elsewhere.

Use it! It makes perfect sense.

It is very intuitive and user-friendly. The solution is a lot more intuitive and user-friendly these days than it was before.

We are deploying this solution to monitor our customers' environments. We use it to look at IOPS and the VMs and for monitoring consumption.

This solution has helped improve our organization because we can now monitor our customers' environmental problems as well as our own and give the correct answers as to what the source of a problem is. 

It has also reduced the time it takes to troubleshoot problems and has improved the quality of service for our users.

Monitoring is the most valuable feature for us. When our customers have a problem and we can monitor it in real time or evaluate the history of the problem.

We have found this solution to be user-friendly because it's fairly simple to navigate. We can see if it connects problems with storage, consumption, or other issues.

I rated this solution an eight and not a ten because we work to give a multi-tenant product to our customers and vROps doesn't meet our needs.

The stability is good because we can do an HA environment. 

Scalability works well. We have many customers and have never had any issues with it. 

We got this solution because we knew we needed a monitoring solution. We decided on this specific solution because of its direct integration features.

The initial setup was straightforward. It was a simple deployment. 

We implemented it ourselves. 

Our ROI is that we have been able to reduce the time it takes to look into a problem. 

Cost isn't a problem for us because it's included in our licensing. 

Opsview was another vendor we looked at. We didn't go with it because we liked vROps' use case. It allows us to see simply and graphically what a problem is and we can export a report of the problem for our customer, which is very valuable to us. Opsview gave us some information but we found it to be slower. With vROps, we can monitor every feature and vendor; we can monitor the environment which means we can monitor everything. 

Cost savings isn't a problem for us because we have enough resources with the cloud provider.

If you're looking into vROps and similar solutions, I would recommend vROps because it's a good program.

I use it for full diagnostics and predictive problems for the applications or services that we run.

Over-provisioning helps us a bit, and we have a lot over-provisioned VMs. Thus, we show different teams that this type of resource can help manage their environment.

With over-provisioning, we track it all. This is one of the main benefits as it is a reactive and proactive full diagnostic. We can see if the servers are behaving differently and why: Is it quiet or busy? The system is quite good.

• I like the dashboards. We can view in our service groups before something in our service goes wrong and causes issues.
• It is user-friendly, because you can visually set up dashboards for people, such as traffic light systems. 
• The integration with vCenter is what makes it a superior product. 
• There is no hassle setting it up, as it works straight out-of-the-box.
• It has a nice user interface.
• Its ease of use.

In vCenter 6.7, there are themes. I would like to see that add to vRealize Operations as well. It is very nice.

The stability has been good. It is just an appliance that needs to be installed. Give it an IP address, name it, and it works fine.

The scalability has been fine.

The technical support has been fine.

We had a license already for this product. Therefore, we thought we would use the license rather than buying a new product.

The initial setup was easy. We installed the appliance, gave it an IP address, and assigned the relevant passwords.

We installed it ourselves.

If the VMs were trimmed, then we wouldn't have to buy as much software/hardware, and this means less licenses. While most of it is VMware licenses, which are relatively cheap, there are SQL licenses for Microsoft, and this is where we could start saving a lot of money.

I would recommend to try the solution.

We use it for monitoring and troubleshooting the performance and stability of our VMware.

If we get reports of applications that are running slowly, we are able to drill into the VM and all the statistics, and see where the bottlenecks are or what the issues are.

The solution has helped reduce the time to troubleshoot issues. It gives us greater insight into all capacity utilization, which helps us plan better.

For us, the most valuable feature is the insight into real-time performance.

At times we find the solution to be intuitive and user-friendly. It's getting better. Version 6 was terrible but 7 is a lot better. There is still room for improvement. It needs to be a bit more intuitive.

I would like to see more integration between vRealize Operations, Log Insight, and Network Insight. It would be nice if they worked a bit better together.

So far, stability is fine.

As for scalability, we've already added an extra node and it was a nice and simple, click, click, done. The scalability is good so far.

We have not had to use technical support yet.

We didn't have a solution that gave us in-depth performance stats or capacity planning in the VMware stack. We were a VMware customer, so it made sense to go with a VMware product. Compared to other products the feature set, use cases, and costs of vROps are fine. It's the integration points that led us to go with VMware, there's better, tighter integration using vROps.

The initial setup was straightforward. It took us half a day.

We used a consultant for the deployment. We used Assist Inc, and they were brilliant.

In terms of ROI, we're getting there. However, it's only been live for a couple months.

We've looked at other solutions before, but we've never found one that does what VROps does. We've looked at Veeam ONE and VMTurbo, but I don't think they're around anymore. That's part of the problem: There were vendors that did the monitoring and they've all crashed and burned. VROps wouldn't do that.

My advice would be, do a hands-on lab. Get to grips with it before you deploy it.

I rate it at eight out of ten. It's a great product. It integrates well with the VMware stack. It covers all the VMware technologies. I just need it to be more intuitive, so that's why it's an eight and not a nine or a ten.

The primary use case is that we are transforming our customer's physical and virtual infrastructure, who are afraid of anything that can happen in a virtual environment. Our job is to make a sort of private cloud, not to sell virtual machines, but to host the workload.

The main point of installing, deploying, and troubleshooting with vRealize Operations is to provide visual dashboards to ensure that the entire workload is functioning properly. Because we sell our infrastructure to clients, they need to be able to operate it. Therefore, they must have the visibility, even if they don't know how the system works from the inside.

We have to be stable to provide high availability because it's a high value market. Therefore, we have to ensure everything works all the time.

It is intuitive and user-friendly.

We are looking to optimize all the parts. For example, vCenter can be fully deployed automatically, which is not the case with vROps. We can click some next buttons to integrate vCenter and would like these type of features for vROps, if possible.

It is stable.

The technical support is good and helpful. 

The initial setup is easy.

We bought the server from a third-party. 

The first thing that we did was ask VMware what type of hardware we should buy. They helped us by providing insight in which type of server to buy, then they helped us by providing the support to integrate the solution.

We chose VMware and its solution because it was the most easily supportable. We know some of their consultants and our people know the products.

Use VMware to support the solution. Don't go at it alone.

We use it to monitor our virtual infrastructure for VDI. It is also used in our server infrastructure for basic monitoring or solving issues.

Our organization is a government company which is focused on thinking about other nations and companies.