VMware Aria Operations OverviewUNIXBusinessApplication

VMware Aria Operations is the #1 ranked solution in top Virtualization Management Tools and #2 ranked solution in top Cloud Management tools. PeerSpot users give VMware Aria Operations an average rating of 8.2 out of 10. VMware Aria Operations is most commonly compared to VMware Aria Automation: VMware Aria Operations vs VMware Aria Automation. VMware Aria Operations is popular among the large enterprise segment, accounting for 70% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 20% of all views.
VMware Aria Operations Buyer's Guide

Download the VMware Aria Operations Buyer's Guide including reviews and more. Updated: January 2023

What is VMware Aria Operations?

VMware Aria Operations is a high-ranking virtualization management and cloud management tool that automates and simplifies IT management to the applications it supports. It achieves this through full-stack visibility from physical, virtual, and cloud infrastructure. The product allows users to enable self-driving IT operations management across private, hybrid, and multi-cloud environments. This is conducted with the unified operations platform that delivers continuous performance, capacity and cost optimization, and integrated compliance through artificial intelligence (AI) and machine learning (ML), and predictive analytics.

VMware Aria Operations Use Cases

VMware Aria Operations has several use cases, some of which include:

  • Continuous performance optimization: VMware Aria Operations allows users to assure application performance at a minimal cost, facilitated by real-time predictive analytics and artificial intelligence. The product can be used to automatically balance workloads, improve consolidation rations, optimize and rightsize workloads, and avoid contention.

  • Capacity and cost management: VMware Aria Operations can be utilized to reduce cost and improve efficiency with real-time ML-based capacity and cost analytics. The solution uses these tools to visualize cost savings opportunities and accelerate decision-making.

  • Intelligent remediation: This product can also be used to predict, prevent, and troubleshoot issues with actionable insights. Through other VMware integrations, users can streamline and centralize IT operations.

  • Integrated compliance: The solution can be utilized to reduce risk and enforce IT regulatory standards for VMware Cloud through integrated compliance and automated drift remediation.

VMware Aria Operations Features

The product has various features which users can utilize. Several of the features that the 2022 version of VMware Aria Operations introduced include:

  • Management pack builder: This feature is a no-code solution that allows users to expand their operations visibility to anywhere they wish. The builder allows users to connect to a data source using an HTTP or Amazon AWS data source, as well as to make API calls, create objects, and build out relationships with other objects in the product.

  • Public cloud basic actions: This is a set of features that allows VMware Aria Operations users to initiate actions automatically via the product's UI for AWS, Microsoft Azure, or GCP CE instances.

  • Rule-based application discovery: Through this new feature of the product, users can easily discover multiple applications running in all or specific areas of infrastructure and view associated resources. This can be achieved through simple user-defined rules, including discovering applications based on tags, object names, and properties.

  • Aria Operations capacity management: This feature allows organizations to view the results of what-if analysis based on their allocation model and specify business hours for capacity calculations.

  • Alerts: This is a set of features that include components called Conditions and Symptoms, which are used to alert different types of issues on the platform.

  • User access management: Through this feature, users can benefit from improved ways to configure in VMware Aria Operations with the introduction of scopes.

  • Support for raw device mapping storage: This feature allows users to get configuration details about their raw device mapping (RDM), such as disk sharing, compatibility mode, and SCSI Bus Sharing.

VMware Aria Operations Benefits

VMware Aria Operations brings various benefits to the organizations using it. Among them are the following: 

  • The product helps organizations reduce unplanned downtime and maximize return on investment (ROI) in hybrid and multi-cloud environments.

  • VMware Aria Operations simplifies management for hybrid clouds from migration assessments.

  • Users can benefit from an accelerated journey to VMware Cloud on AWS through this solution.

  • The product can be delivered on premises or as a service, providing flexibility for its users.

  • VMware Aria Operations can increase operational efficiency through monitoring and management features.

  • The solution accelerates decision-making through detailed cost analytics, which is visualized for users' convenience.

  • VMware Aria Operations allows users to both utilize standard compliance templates and create their own custom ones.

Reviews from Real Users

Mohamed N., a tech lead VMware support engineer at a tech services company, appreciates VMware Aria Operations because it is easy to use, stable, and support is always available.

Mojtaba K., a senior system administrator at a comms service provider, values VMware Aria Operations due to the fact that its dashboards give you a glimpse of what is really going on in your virtualized environment.

VMware Aria Operations was previously known as VMware vRealize Operations (vROps), vCenter Operations Manager, VCOPS, vRealize Operations.

VMware Aria Operations Customers

Science Applications International Corporation, Tribune Media, Heartland Payment Systems, Telkom Indonesia, Columbia Sportswear, iGATE, CSS Corp, Angel Broking, Adira Finance, Hipskind, Beiersdorf Shared Services, Innovate Mas Indonesia, Adobe, Cleveland Clinic Abu Dhabi , Join Experience S.A, Borusan Holdings, Department of Transport - Abu Dhabi

VMware Aria Operations Video

VMware Aria Operations Pricing Advice

What users are saying about VMware Aria Operations pricing:
  • "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."
  • "The billing is complicated because every country has a different option. Here in Chile, we don't pay for this kind of service with the Chilean pesos. We use another currency. In the future, I think vROps needs to work with governments for a native solution."
  • "This is an enterprise-level product and everything is included in the VMware Suite license."
  • "The licensing is not clear at the moment if the on-premises pricing is the same as on the cloud. I am checking on the pricing. However, you can save a lot of money with the cloud solution because you need to spend time installing, upgrading, and connecting with the on-premises solution. Also, you don't need to spend time scheduling the maintenance and maintaining the solution when using the cloud version."
  • VMware Aria Operations Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    Tech Lead VMware Support Engineer at a tech services company with 1,001-5,000 employees
    Real User
    Easy to use, stable, and support is always available
    Pros and Cons
    • "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."
    • "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."

    What is our primary use case?

    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.

    How has it helped my organization?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    Buyer's Guide
    VMware Aria Operations
    January 2023
    Learn what your peers think about VMware Aria Operations. Get advice and tips from experienced pros sharing their opinions. Updated: January 2023.
    670,523 professionals have used our research since 2012.

    For how long have I used the solution?

    I have been using VMware for two years.

    What do I think about the stability of the solution?

    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.

    What do I think about the scalability of the solution?

    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.

    How are customer service and support?

    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.

    Which solution did I use previously and why did I switch?

    VMware is the first solution that I used for virtualization.

    How was the initial setup?

    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.

    What about the implementation team?

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

    What was our ROI?

    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.

    Which other solutions did I evaluate?

    We did not evaluate other options before choosing VMware.

    What other advice do I have?

    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.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Other
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Senior System Administrator at a comms service provider with 201-500 employees
    Real User
    Its dashboards give you a glimpse of what is really going on in your virtualized environment
    Pros and Cons
    • "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."
    • "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."

    What is our primary use case?

    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.

    How has it helped my organization?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

    I have been using vROps for a year.

    There is a team of multiple people at my company working with vROps.

    What do I think about the stability of the solution?

    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.

    What do I think about the scalability of the solution?

    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.

    How are customer service and technical support?

    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.

    Which solution did I use previously and why did I switch?

    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.

    How was the initial setup?

    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.

    What about the implementation team?

    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.

    What was our ROI?

    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.

    Which other solutions did I evaluate?

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

    What other advice do I have?

    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.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Buyer's Guide
    VMware Aria Operations
    January 2023
    Learn what your peers think about VMware Aria Operations. Get advice and tips from experienced pros sharing their opinions. Updated: January 2023.
    670,523 professionals have used our research since 2012.
    Consultant at a consultancy with 1-10 employees
    Real User
    Top 10
    Notifies you of a problem and will point you to where the location is
    Pros and Cons
    • "Our business is built around testing, measurement, and performance measurement and vROps is the primary tool. We use it in a VMware environment and we do tests in other environments. But in the VMware environment, vROps and the associated products, Log Insight and Network Insight are the primary tools that we use. It's a basic tool. It's very important for our organization."
    • "If I put on the hat of a client, I would say cost needs improvement. For clients with reasonable-sized infrastructure farms, you're looking at licensing at either per socket or per VM, and if you have an installation of any size, you're doing it per socket, and the per-socket licensing is a little heavy. Per VM license, if they have large numbers of VM, it is just not practical."

    What is our primary use case?

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

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

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

    How has it helped my organization?

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

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

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

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

    What is most valuable?

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

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

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

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

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

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

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

    What needs improvement?

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

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

    For how long have I used the solution?

    I have been using vROps for six years.

    What do I think about the stability of the solution?

    We found it to be very stable. 

    What do I think about the scalability of the solution?

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

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

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

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

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

    How are customer service and technical support?

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

    How was the initial setup?

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

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

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

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

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

    What was our ROI?

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

    What's my experience with pricing, setup cost, and licensing?

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

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

    What other advice do I have?

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

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

    My advice would be to find a specialist. 

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

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

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Team Leader & VMware Specialist Engineer at a comms service provider with 1,001-5,000 employees
    Real User
    Top 20
    A scalable solution that is good for monitoring and day-to-day troubleshooting
    Pros and Cons
    • "For project management and new clients, the What-If Analysis is very good. You can use it for workloads. When you are adding new workloads to your platform, it helps you avoid impacting your production."
    • "In a previous version, you could click on a cluster to see a lot of information about efficiency, e.g., when you will run out of memory, CPU usage, and RAM in percentages. In newer versions, you see this information in megahertz and kilobytes, not percentage. I don't like this change so much. If you need to present information to your boss or Director of IT, the information would be better with a percentage. Now, you have only a big number and don't know the percentage of use that you are getting from the VMs. I don't know why they changed it, but I liked the percentage version more than getting the numbers for megahertz of memory. Also, kilobytes of memory is a very large number. For a simple view, gigabytes or terabytes is better."

    What is our primary use case?

    We monitor workloads with vROps. For example, if a new customer wants our services, we need to know the impact if you put their workloads in our platform, i.e., if this new workload will have any impact on the product or platform. We need to know the increase in percentage relative to CPU, memory, and disk. So, it is important to know how a new project or workload can impact the product or platform.

    How has it helped my organization?

    It can decrease the downtime of a client who recently has experienced performance issues by 10% to 15%. This tool can help you decrease those kinds of circumstances. Downtime is also about the design of the solution and how you put workloads in your infrastructure. If you put in more VMs than your infrastructure can support, you will have a big problem with all your clients. That is the reason that it is very important to check the performance every day of the ESXi host and vCenter from maintenance mode. If you periodically check if you have had a security issue, then you can resolve it as soon as possible from a security perspective.

    vROps is selling because we have a lot of customers who need to know their usage of VMs, e.g., is the sizing of our VM good or should I decrease it? Or, in reverse, I need to increase the size of the VMs. All this is about the performance and what VMs resources you can liberate from the platform.

    What is most valuable?

    It is a very good tool for day-to-day troubleshooting. For example, if you have CPU-ready VMs, you can build a report of VMs who recently had an issue. It is useful for making decisions and troubleshooting issues. I think it is the most powerful option on the market.

    You can schedule reports on the platform that are very useful day-to-day. 

    For project management and new clients, the What-If Analysis is very good. You can use it for workloads. When you are adding new workloads to your platform, it helps you avoid impacting your production.

    There is another useful tool for undersizing or downsizing VMs, which has more resources than they can handle. 

    We have a dashboard for the latency of the datastore on the storage side. For new architectures, we have a vSAN dashboard for latency based on the usage of vSAN, because you need to regularly see the used space.

    The newer versions (5, 6, and 7) are more user-friendly. There are tabs upfront where you can see if you need a dashboard, for example. You also have a building option, if you want to build in the infrastructure and how. It is very customizable from that point of view.

    It is a very good tool for efficiency. From an ESXi host perspective, you can see the CPU rate on a dashboard. For example, if the relationship is 5:1, then it is a good standard. If you exceed this, you can get into problems with VM performance. If you have a host with a VM inside of a host using the CPU, you can balance that manually. It can also help you move the VMs into clusters. 

    What needs improvement?

    The older versions are not user-friendly.

    If you have an operations center, you can put a big monitor with its dashboards so you can see what is going on in your platforms. However, there is no real-time. It takes about five minutes to refresh info. It is a good option if you need to see the entire landscape of the solution, e.g., the CPU, memory, and disks. For example, if you have plugins for VxRail, and there is a problem, will you be notified?

    They could mix in parts of VMware Skyline into vROps to make it more efficient.

    In a previous version, you could click on a cluster to see a lot of information about efficiency, e.g., when you will run out of memory, CPU usage, and RAM in percentages. In newer versions, you see this information in megahertz and kilobytes, not percentage. I don't like this change so much. If you need to present information to your boss or Director of IT, the information would be better with a percentage. Now, you have only a big number and don't know the percentage of use that you are getting from the VMs. I don't know why they changed it, but I liked the percentage version more than getting the numbers for megahertz of memory. Also, kilobytes of memory is a very large number. For a simple view, gigabytes or terabytes is better.

    With the What-If Analysis, if you put some information in, and then add another workload, it is not possible to view the two workloads in the What-If Analysis. For example, if you have a customer who wants to up your sizing by 30% more, and then you have another customer tool which needs sizing, how can you leverage resources? If you add these two customers, then your sizing might be 70%, but you only have 30% of your resources free.

    I would like to see more information about public cloud plugins with Amazon, Google Cloud, and Azure. This is really important in the future. Companies are moving to public clouds to maintain their workloads since they don't have downtime, which makes for very stable platforms.

    In the future, they could add a central administrator for vROps. For example, if you have a large environment from multiple countries, then you need to look at the landscape for performance and forecasting.

    For how long have I used the solution?

    I have been using it since 2017.

    What do I think about the stability of the solution?

    Version 6.7 is more stable than the previous version. There is no real problem with the purchase of upgrades. So, it is a very stable platform if you get good sizing of the tool. If the VMs do not have the appropriate memory and CPU, then you can probably get performance issues. So, this is important for the tool. From the disk size, it is better to choose the thicker VMDK to maintain a good performance if you had a lot of vCenters.

    What do I think about the scalability of the solution?

    It is a scalable solution. If you need more vCenters or information, you can simply add VMs onto the cluster. From the vROps cluster, you can get more resources from the VMs. You only need to deploy a new VM for the cluster of vROps, and this automatically moves the workloads. If you put an IP, then the server will recognize this new node from the cluster and the job automatically. So, it has very good scalability.

    There are a lot of plugins. For example, I use the vCloud Director plugin for private cloud. We also have VxRail. VMware and Dell EMC work very well together. From the VxRail side, there are plugins that can help show you more information for your platform.

    How are customer service and technical support?

    Their support team is very good. They will explain things to you. You are very involved with the problem. I think the Latin America team works out of Costa Rica.

    We had some problems with the views in version 6.5. It would show me 110% usage, which doesn't make sense. We opened a case with VMware. I worked with their development team in Bulgaria. We resolved the problem. 

    I had a problem with a vROps plugin because we upgraded our vCloud Director. The plugin didn't recognize the upgrade. At that moment, we are doing a workaround for this while they apply a new update from this plugin to resolve this problem.

    We had a demo for Tanzu from VMware for vCloud Director. We needed to show a customer how vCloud Director works with Tanzu and the Kubernetes solution. From that demo, we built a solution with VMware that links with vCloud Director as a platform.

    VMware Skyline detects a problem in your platform. It has the ability to create a ticket to VMware directly, then you will receive a call from VMware, "Oh, you had this problem." It also monitors security issues.

    How was the initial setup?

    The initial setup for the demo is very easy. You have 60 days to use the trial version and see what the tool has to offer to you. You only download the URL, then configure some parameters, IP, and sizing. Also, in the wizard, you have an option where you can see VMs with more CPU, memory, and disk. 

    The deployment was first a demo version, which was standalone with one VM. Then, we needed to add more vCenters to vROps, so we needed to add more VMs. Finally, we had three VMs to maintain the database of vROps.

    We started with a demo version to see what the tool has to offer our organization in regards to the VM's efficiency and health. This is very common for our company. They ask you, "What if you put more workload in our infrastructure? How will this impact a new workload in our environment?"

    You have two options to deploy VMs. 

    1. You have thin space. If you use VMs, then there is space to increase. However, if you decide to choose VMs with thin space, probably for an SQL database, there is no other good option from a performance perspective.
    2. You have thick space. For example, you have a disk of 100 GB, and you say, "All" in the first deployment.

    What's my experience with pricing, setup cost, and licensing?

    The billing is complicated because every country has a different option. Here in Chile, we don't pay for this kind of service with the Chilean pesos. We use another currency. In the future, I think vROps needs to work with governments for a native solution.

    What other advice do I have?

    It is useful for determining whether to make decisions. Also, for our troubleshooting issues, it is the most powerful option in the market.

    vROps provides a good native solution if you are using multiple VMware tools.

    The design and what you sell to customers will impact your infrastructure.

    There is a new version, but I haven't used it yet.

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

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Consultant at a tech services company with 10,001+ employees
    Consultant
    Top 20
    Dynamic interface with interactive dashboards, easy to use, helps with proper sizing
    Pros and Cons
    • "The dashboards and the interface are very easy to understand, very lively, and very dynamic."
    • "The what-if analysis section is not very advanced and there is a lot of room for improvement."

    What is our primary use case?

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

    How has it helped my organization?

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

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

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

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

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

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

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

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

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

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

    What is most valuable?

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

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

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

    What needs improvement?

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

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

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

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

    Other than this single issue, it works fine.

    What do I think about the scalability of the solution?

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

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

    How are customer service and technical support?

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

    Which solution did I use previously and why did I switch?

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

    How was the initial setup?

    This solution is very easy to deploy.

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

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

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

    What was our ROI?

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

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

    What's my experience with pricing, setup cost, and licensing?

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

    What other advice do I have?

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

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

    I would rate this solution a nine out of ten.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    System Engineer at a retailer with 10,001+ employees
    Real User
    Top 5Leaderboard
    Helps us manage and increase capacity as needed, and workload balancing has notably decreased our downtime
    Pros and Cons
    • "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."

    What is our primary use case?

    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.

    How has it helped my organization?

    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.

    What is most valuable?

    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.

    What needs improvement?

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

    For how long have I used the solution?

    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.

    What do I think about the stability of the solution?

    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.

    What do I think about the scalability of the solution?

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

    How are customer service and technical support?

    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.

    Which solution did I use previously and why did I switch?

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

    How was the initial setup?

    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.

    What's my experience with pricing, setup cost, and licensing?

    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.

    Which other solutions did I evaluate?

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

    What other advice do I have?

    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.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Pedro Nova - PeerSpot reviewer
    IT Projects at a tech services company with 11-50 employees
    Real User
    Top 20
    Useful for performance monitoring, alert monitoring, and capacity planning
    Pros and Cons
    • "I have integrated vROps with vRealize Log Insight and vRealize automation. After integrating vRealize, we tried to split and combine the logs from the login sites for more alerts and information to organize the whole infrastructure and have automation. We used many different types of scripts trying to orchestrate them all together into one solution, replacing, for example, Elasticsearch and some other scripts."
    • "The solution can improve by offering more flexible integration with other platforms or products, such as Hyper-V or Azure. Not everyone uses VMware. It would be beneficial to have a more open-source concept for integration, creating more visibility across multiple clouds."

    What is our primary use case?

    We use vROps as a monitoring solution because it is good at that. It is designed to monitor VMware data centers. 

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

    How has it helped my organization?

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

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

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

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

    What is most valuable?

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

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

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

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

    What needs improvement?

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

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

    For how long have I used the solution?

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

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

    What do I think about the stability of the solution?

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

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

    What do I think about the scalability of the solution?

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

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

    How are customer service and technical support?

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

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

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

    Which solution did I use previously and why did I switch?

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

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

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

    How was the initial setup?

    The initial setup of the solution is easy. 

    The deployment takes less than 20 minutes.

    What about the implementation team?

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

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

    I also work with third-parties and providers.

    What was our ROI?

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

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

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

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

    It gets better with every version.

    What's my experience with pricing, setup cost, and licensing?

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

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

    Which other solutions did I evaluate?

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

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

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

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

    What other advice do I have?

    My advice is to test the product.

    I am monitoring VxRail from vROps.

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

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

    Which deployment model are you using for this solution?

    Hybrid Cloud
    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
    PeerSpot user
    Deputy Manager at PacECloud
    Real User
    Top 5
    Visibility helps with cost optimization and performance tuning in a large infrastructure
    Pros and Cons
    • "One of the most valuable features is the ability to compare between AWS/Azure and the local cloud. When customers deploy something on the local cloud, with the same configuration that would apply to AWS or Azure, we can calculate the estimated cost difference between the local cloud and the public cloud. We do this kind of analysis for optimization and it is one of the best features of vROps."
    • "They need to improve the capacity and infrastructure planning side of things. Also, I would like to see them integrate more stuff, with more detailed monitoring and different cloud providers."

    What is our primary use case?

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

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

    How has it helped my organization?

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

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

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

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

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

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

    What is most valuable?

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

    The most commonly-used functions are easy to access.

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

    What needs improvement?

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

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

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

    What do I think about the scalability of the solution?

    The scalability is 4.6 out of five.

    How are customer service and technical support?

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

    Which solution did I use previously and why did I switch?

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

    How was the initial setup?

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

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

    What was our ROI?

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

    What's my experience with pricing, setup cost, and licensing?

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

    Which other solutions did I evaluate?

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

    What other advice do I have?

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

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

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

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

    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
    PeerSpot user
    Buyer's Guide
    Download our free VMware Aria Operations Report and get advice and tips from experienced pros sharing their opinions.
    Updated: January 2023
    Buyer's Guide
    Download our free VMware Aria Operations Report and get advice and tips from experienced pros sharing their opinions.