VMware Aria Operations Reviews

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.

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.

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.

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.

We use VMware Aria Operations for complete visibility of the configurations. It provides us with predictive analysis of the capacity, helping us plan the scalability of resources.

The product has business intelligence features. We can view daily reports of the cloud products.

The product's support services need improvement.

We have been using VMware Aria Operations for more than four years.

I rate the product's stability a nine out of ten.

I rate VMware Aria Operations a nine and a half out of ten.

The technical support services could be better. We need to know the business requirements to get the reports. It is a time-consuming process. Sometimes, we have to search for every detail to make a holistic report.

The initial setup is easy. It can be deployed in any environment. It's a very dynamic product.

It is a very good product. We can download and integrate features from the portal using templates instead of creating them. I rate it a nine out of ten.

We can manage the virtual environment of our organization with the help of the solution.

They keep improving and updating their apps over time. In each new version, we get lots of good features; thus, I don't have any concerns.

They should include an integration feature through which we can connect to different vendors by installing a small plugin.

We have been using the solution for more than five years. Also, I have been using it for 16-17 years, personally.

It is a stable solution.

It is a scalable product. We have a couple of 100 users using the solution in our organization. 

We are using VMware as it is a known product that helps to manage companies' virtual environments. Consumers are accustomed to using VMware, and it's a very old product as well. That's the main reason we are using it.

I recommend others use the solution and rate it as a nine.

We use this solution to monitor the virtual infrastructure health with deep-dive analytics ensuring hypervisors, VMs, network, and storage health. We can also use it for future forecasts for virtual machines, and allocate additional resources for where contention occurs.

Efficient use of resources/planning has helped my organization.

We like that we are able to combine all infrastructure monitoring using this solution, meaning we receive analytics from across our whole network.

We would like to see an improved licensing model to be set up for this solution. The current model charges per CPU, as opposed to being product-based, which would allow us to monitor our complete virtual infrastructure under a single license.

I have been using this product for two years.

We would rate this solution a seven out of ten.