VMware Aria Operations Reviews

I use VMware Aria Operations for logs in my company. I just use it to manage the logs and to see what is happening in the security logs. VMware vCenter is used to deploy virtual machines.

I specifically use the tool for logging and looking over the various traffic flows happening within VMware. It is easy to track and see what is happening where, and it can easily figure out solutions if there are any problems inside VMware's access management tools.

As VMware is moving to Broadcom, I feel the support is becoming really bad. There are some areas VMware needs to look into, specifically regarding the connectivity provided by the tool. My company has been facing the aforementioned problem with Aria Operations, and I think it has been more than two months now, and still VMware hasn't found any patches for it. My company is not able to figure out what exactly the problem is with the tool. I am not sure if there is some problem because of the movements. I think that in terms of where the customer experience lies, I feel I have had a bad experience for two or three months, and it keeps on happening, which is impacting my production. I am not sure if VMware is able to find a solution with the product I use or if there is some other problem. There are some current issues with the support provided by Broadcom, making it an area where improvements are required.

I have been using VMware Aria Operations for three years. I am a customer of the product.

The stability of the product is something that depends on how much work a user has with the tool. If you have a very good experience with the tool, then you can do things in a very good procedure. The tool's initial deployment went well with the support from VMware. VMware's support is really good, but because of Broadcom there are some problems. Initially, the new product's implementation and deployment went well with the support from the solution.

Scalability is easy in VMware Aria Operations. The only things you need to manage are the backups and how much expansion you want with the tool. If you take a product from Microsoft or VMware, both work really well for an initial three or four years. Adding something new would mean taking a different approach, and that would depend upon the company's expansion.

My company uses just one function of the product, which is specific to our environment. There might be some other functionalities in the product that might help with certain enhancements in the area of logs, but we don't have the exact scenarios for which we can use the tool's certain functionalities.

If I specifically talk about VMware's support, then the support offered is very good, especially if I don't consider VMware's integration with Broadcom. I rate the tool's support a nine out of ten. I am not sure if I can comment on Broadcom's support services since it is still in the initial stages.

VMware vCenter is used to deploy virtual machines.

VMware solutions are easy to install. There are some available steps to install the tool and if we follow the steps, I think it is a good solution to work with for anyone.

The tool doesn't take much time to deploy. I am not sure of the time required to deploy the product because our company uses the solution for a specific function, so I believe that it might also have some other functions. The functions my company uses for logs are very easy to deploy since, just after connecting the solution, it starts getting all the logs.

It is an easy solution to use, and you need to invest in it only one time by looking at your personal usage and expansion plans. Getting a machine and everything within the solutions and bringing in the tool where you have some availability shortage need to be done only once, after which you can expand it instead of buying a fresh machine for A certain period of time, which can be an expensive affair. A product starts from the day you create a machine in the cloud solution. The solution also provides users with some features and facilities that are specific to the licensing models you have from the tool. Considering how much and what type of licenses you have, the cost might be reduced. For expansion purposes, you don't need to think about new tools because you already have the solution you purchased from VMware. With whatever expansion scope is available in the tool, it is easy to expand the solution to a few more servers. If you are going with other solutions for expansion purposes apart from VMware, then there is a cost involved. The tool is easy to use, but from the cost perspective, there might be a huge difference between other tools and VMware. You have to invest less in cloud solutions because you pay as you work with the tool. You can deploy one machine and then deploy another machine tomorrow. With VMware, you need to invest just once, after which expansion options are already available in it.

If we talk about the cloud solutions that are available in the market, I think that instead of collaborating with VMware and Microsoft or with some other solutions, VMware should focus on providing good cloud solutions. VMware should not take advantage of any other products in the market to provide the cloud version of its products since its pricing might change. For people who don't want to move away from VMware, it can be a pricey product. If you compare the prices of VMware and the cloud solutions along with the components that you may use, I feel that it may be costly.

There is no specific maintenance required for the product, and usually you get an advance notice if something like that is required. It is up to the user to schedule the maintenance as per their timeline.

I have not specifically faced any challenges in managing the solution in our virtual environment. Earlier, there were some problems with the tool.

If the product is able to fulfill your requirements, then I would say that VMware is a good product for you.

I rate the tool an eight out of ten.

We use VMware Aria Operations for the provisioning of the servers.

The solution gives suggestions regarding whether resources are underutilized or overutilized. It can also do automatic rescheduling like we do in the cloud. The solution's predictive analysis helps us in our future planning for procurement of the server, provisioning of the server, and capacity planning.

The solution’s pricing could be improved.

I have been using VMware Aria Operations for a couple of years.

VMware Aria Operations is a stable solution.

VMware Aria Operations is a scalable solution. More than 10,000 users are using the solution, and we have plans to increase the usage.

The solution’s technical support is good.

The solution is easy to deploy and doesn't require much effort. The solution's documentation helped us to do the installation and configuration.

We implemented the solution through an in-house team. For deployment, we consider doing some certifications, which is the best place to keep some items, whether on-premises or on the cloud, the cost, and compliance. After that, we make a plan and then do the deployment.

The solution is slightly expensive.

VMware Aria Operations is deployed on the cloud in our organization. If users have a valid case, they should go for the solution. Users need to pay more if they go for the premium support.

The solution's integration with other tools is good. Sometimes, we need to connect the solution with different tools, and all the tools are easily integrable.

Overall, I rate VMware Aria Operations ten out of ten.

VMware Aria Operations is a new platform that provides visibility into different areas of the infrastructure, reduces or eliminates downtime, and makes customers more proactive. It gives customers the insights they need to be proactive rather than not active, and it helps them plan for capacity needs, ensuring that they are doing their best to avoid over-provisioning or experiencing contention. It also has a self-service option so that end users can be more independent from the infrastructure team and monitor their needs.

Avoiding problems in the monitoring area is our strength. We use real-time monitoring models and real-time monitoring to do this. We also provide other capabilities, such as seeing changes in the environment.

The VMware Aria Operations solution is a very technical product and is not for everyone. As a top-of-the-chain VMware tool, it is only normal that it has a learning curve. While the UI has been improved, it may still be difficult for some users. The solution has a lot of functionality and can monitor all areas of infrastructure, such as storage and network.

I have been using VMware Aria Operations as a partner for seven years.

I rate the solution’s stability a ten out of ten.

I rate the solution’s scalability a ten out of ten.

The documentation is perfect.

Positive

The initial setup is easy. The setup time depends on the scale, but it can be as short as a few hours. Once the valet solution is deployed, you must link it to the infrastructure. This process takes a few hours, as the key must pull data from all the infrastructure components. In most cases, the valet solution will remove the entire infrastructure into CRM within a few hours or less.

I rate the initial setup an eight out of ten. 

Most small users don't adopt VMware Aria Operations until it's necessary. Small businesses are looking for it, too. We need more monitoring and insights, so we're analyzing solutions to help us out here.

I rate the solution’s pricing a five out of ten.

VMware Aria Operations has many hands-on plug-ins that can help you monitor all the elements in your infrastructure, such as storage, networks, and more, beyond VMware infrastructure itself.

Overall, I rate the solution a nine out of ten.

Primarily, we use VMware Aria Operations for monitoring VMware and the cloud. We also need to report on physical servers.

We are not currently using the solution to the extent of what it can do. But we are moving in that direction. We are in the process of getting an integration to our ServiceNow instance, which will replace a lot of small tools used for monitoring.

The ease of installation and configuration is the most valuable feature, especially for VMware and the cloud. The solution is almost one click, and we get our workload.

Adding some intelligence to VMware Aria Operations, such as event correlation, and some level of AI apps will improve the solution, similar to what we see with the more advanced monitoring solutions that we don't currently have.

I have been using the solution for almost four years.

The initial setup is straightforward.

I give the solution an eight out of ten.

Our primary use case for the solution is troubleshooting and performance monitoring.

It has allowed us to identify problems sooner and helps us with problems and issues.

The troubleshooting and performance monitoring features are valuable.

Administration and growth can be improved. For instance, if we're a large organization, the metrics continue to get collected in this environment and continually fill up, so we need to expand the cluster. Hence, more resources are always required.

We have been using the solution for five years and are currently using version 8.62.

The solution is stable.

The solution is scalable to a degree. The problem is that it goes back to the solution or management packs. The more you collect, the larger you need to expand the environment. Approximately 12 to 24 people are using it in the organization.

We previously used Densify.

The initial setup was straightforward.

We implemented it through a vendor team. Two to three people are required for deployment.

We have seen a return on investment.

I do not have information on the licensing costs.

I rate the solution an eight out of ten. The solution is good, but administration and growth can be improved.

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

The monitoring and verification functionalities were the most useful features.

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

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

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

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

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

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

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

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

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

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

I would rate this solution a seven out of ten.

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

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 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'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.

Our customers use the solution to monitor the health of the cloud platform and ensure everything is okay.

Heat maps are valuable. The alerting feature has been the most beneficial in managing virtualized environments.

The solution must provide better training options to help us make the most of the tool. The learning curve is fairly high. It's a deceptively easy product when we first look at it, but it has tremendous depth. There's a lot to it.

I have been using the solution for five years.

The tool is stable.

The tool is scalable. We use a lot of different installations of the product. Our customers are small, medium, and large enterprises.

The support is good. We often wonder whether the support team will meet the SLAs. I'm very reluctant to make all of our support issues P1. VMware is reasonably good at fixing problems. They probably don't have enough qualified engineers in Aria Operations’ support. When you get them on the phone, they are very knowledgeable.

Positive

We used Turbonomic. We do not use it anymore because it isn’t as useful. It didn't have all the features that we needed in an MSP solution.

The solution is easy to deploy. We have a lot of configuration, so it takes a lot longer. However, the basic installation takes 20 to 30 minutes. One engineer is more than enough to deploy the tool. It is reasonably easy to maintain the product.

The return on investment is reasonable. However, the features we would most want from an MSP perspective are those we can't afford because we can't pass on the costs to the customers. We will have an issue if we need more hosts and storage. Our customers cannot afford it.

Reducing the cost would be the most beneficial. The product is too expensive to implement. We can't afford the extra features because it's simply too expensive.

We are cloud providers. We use the solution as a part of our support for the customers. We should be able to model our requirements and purchase in advance. Modeling would be very useful if our platform is growing. If a customer has a particular amount of CPU, storage, and memory requirements, we'd like to model it and get ahead of the storage availability and CPU memory availability issues. We could also model the upgrades when there is a need for maintenance. Such modeling is very useful to an MSP. Overall, I rate the product an eight out of ten.