VMware Aria Operations Reviews

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.

In many cases, I have worked with vCenter within our virtualization environment. Some problems result in vCenter becoming corrupted, making it unusable. Consequently, I resort to utilizing it as a standalone server for each issue. This is the primary problem I've faced over the past two years, and for every problem that arises, I manage to resolve it. I've observed that using each server independently is the standard practice, and I occasionally utilize it for various purposes.

I have found the backup extremely useful in my use cases.               

In this vCenter, my wish is to establish a backup system that doesn't require VIN. It involves creating a backup ticket directly from the vCenter for the virtual machines and performing the backup task for each server, ensuring redundancy without the need for additional software. This would be a preferable solution if all of this could be accomplished within vCenter itself.

I have been using VMware Aria Operations for the last two years.

I would rate the stability a seven out of ten.

I would rate it seven out of ten. Based on my experience, there have been occasional issues with vCenter. One of the recurring problems involves vCenter going offline, and when that happens, I'm unable to resolve it, necessitating the installation and reintegration into the system. This has been an ongoing challenge throughout its entire lifespan. However, when it comes to accessing the servers individually, there's a different issue. While using the solution, there are frequent occurrences where, when I make changes to a machine, such as adjusting RAM or other resources, I sometimes encounter a situation where the data doesn't load properly, resulting in a yellow screen. To rectify this, I have to refresh the page and then make the necessary changes to the machine. While this can be somewhat frustrating, it's not overly difficult for me to manage, and I've learned to handle it without considering it a significant problem.

I haven't taken any formal courses on vCenter, yet I've managed to install and troubleshoot them successfully. I've relied heavily on online resources, and the wealth of information available on the Internet has proven to be a valuable asset. I haven't sought support from any specific company. However, it's possible that in the future, I might encounter a problem that I can't resolve on my own, even with online resources. At that point, reaching out to a company for assistance might be necessary.

It is not difficult but sometimes requires extensive reading and knowledge to install it. It's not a complex task, but I need to fully comprehend everything in order to install it. Sometimes network-related issues can complicate matters, and having a strong background in network infrastructure, including switches and routing, is crucial for successful execution. If there's a preference, I'd appreciate guidance on which one to install. Also, it would be convenient if I didn't have to create everything from scratch on the switch. Some elements may need to be set up physically, and then I can connect them to two switches for network installation, requiring a three-step installation process. The deployment is scheduled for two months to complete the installation and server replacement. This timeframe should encompass all aspects of the solution.

It's not particularly challenging, but it's important to remain close to the users, ensuring that the data is functioning correctly. We need to verify its operation for a week. Out of ten servers, everything is working fine. Then, I'll proceed to another server, following a similar approach, to ensure it is safely set up. We won't be dealing with desktop servers; it's more about efficient and timely execution.  

I would rate it six out of ten.

There's a smaller category that stands out due to its affordability, especially for recent versions, which I rate as four or five in terms of value. However, if you're looking for a vCenter with older, more advanced features, it comes at a significantly higher cost, and I would rate it around ten. They provide us with a choice between a recent version and one integrated, and I lean towards the former.

I would rate it overall an eight out of ten. 

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

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

vRealize has a very nice dashboard.

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

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

I've been using it for five years.

It is a very stable product.

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

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

Positive

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

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

We used a third party team for the deployment.

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

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

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

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

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

We haven't had any issues with vROps. 

I think vROps is scalable and suitable for our environment.

VMware technical support is good. 

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

The initial setup isn't complex.

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

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

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

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

We have been using the application for ten years.

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

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

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

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

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

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

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

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.