VMware Aria Operations for Logs Reviews

We have been using this for the last five years.

VMware Aria Operations for Logs would be used to completely monitor the health of your environment. Second is to understand your existing capacity and forecast your capacity for the next year or so. Third would be on performance management, understanding how the environment is performing, and what has to be done to optimize it. We use VMware Aria Operations for Logs for these purposes. We also use VMware Aria Operations for Logs to monitor non-VMware components as well.

VMware Aria Operations for Logs is now part of a bigger suite with several modules added. You have an option to collect logs from various sources and then you can do some sorts of analytics from it as well. All of this can be done with VMware Aria Operations for Logs.

VMware periodically provides upgrades and updates to the product. They are also extending support to various third party hardware as well. I am not sure whether they have any ready made APIs for cloud for managing cloud based environments. If they do not have this, they should probably focus on integrating VMware Aria Operations for Logs with hyperscale cloud providers such as Azure, AWS, and Google, so that we can integrate all of them together using one single tool.

VMware Aria Operations for Logs comes with the options for high availability and disaster recovery as well. The product is pretty much stable.

Scalability depends upon the licensing features. Depending upon the license you have opted, you can scale accordingly. I do not think there is a specific limit to the scalability even though there is a hard limit in terms of number of assets we can manage. Scalability can pretty much be achieved by increasing your licenses or once you reach the maximum, you can deploy one more VMware Aria Operations for Logs and then you can integrate them together.

We deploy this on customer environments. We do get tech support from VMware whenever we encounter any sorts of issues. We approach them and they help us in solving issues as well. I would rate them about nine out of ten in terms of support.

For an enterprise, it will probably take a maximum of a week from assessing the environment to design and then implementing it. One week is good enough for VMware Aria Operations for Logs implementation. When you look at integrating with various solutions and if you want to access various business cases, it completely depends upon what you are trying to incorporate, which changes the environment. Basic deployment will not take more than a week's time.

For accessing and deploying design, probably one person who understands VMware Aria Operations for Logs is good enough. When it comes to integration, we might need one additional person. To manage the environment, we just need one engineer to manage the environment.

VMware Aria Operations for Logs does have device licenses. The license is perpetual and you do not have to pay monthly as it is a one time purchase. The only thing is if you are looking for support, then you have to renew the support fee year on year, and they do have options for three years as well. For licenses that are perpetual, they do not have an expiry period.

Monitoring and managing the environment is the key area. VMware is a leader in terms of virtualization. The advantage of VMware is that their products are pretty much stable. They come with various versions so according to your business needs, you can pick and choose what you want. They have a very good support environment. Wherever you are in the world, you can reach out to your local VMware support for help. They periodically update and upgrade the product so that you are always compliant with your local regulatory and compliance requirements.

VMware Aria Operations for Logs comes in different versions. There is a standard version for small current customers, an advanced version for mid-market and SMB customers, and an enterprise based version for a larger customer base. You have an option to pick into what you want. The product is really expensive compared to other products in the market. However, considering the reliability and the value that it brings in, I think that is still manageable. You just need an engineer as part of the team to manage the whole solution and you do not need a dedicated team to manage it. I would rate this product nine out of ten overall.

Positive

Our primary use case for VMware Aria Operations for Logs is troubleshooting. We manage many different use cases, but most of all, it is for troubleshooting. The feature where we can narrow into a specific time and filter from there on the heavy hitters and anomalies is very effective for troubleshooting. 

We use this tool for infrastructure troubleshooting and for managing logs more effectively compared to other tools like Splunk.

The primary benefit to our organization is saving money on other logging tools, such as Splunk. VMware is licensed on hardware rather than the amount of data, which helps reduce costs. Instead of sending all logs to Splunk, we filter them using VMware, which saves us from paying high storage costs associated with Splunk.

The ability to narrow into a specific time to filter heavy hitters and anomalies is extremely valuable. It provides a comprehensive way to troubleshoot and analyze logs, especially for infrastructure-related issues. This tool also provides greater insight when integrated with VMware infrastructure, making it more precise than other tools.

The tool could benefit from improved filter settings and dashboarding. While there are dashboards available, they are often created by community members and may not work after updates. It would be beneficial to have a roadmap for these dashboards to ensure consistent functionality. It would also be advantageous if the tool could process even large amounts of data faster, though this may be more related to data movement challenges rather than the software itself.

I have used VMware Aria Operations for Logs for three years.

Managing a lot of data involves reliance on hardware and network performance, which are external factors that can affect stability. If data migration occurs during a search, it alters performance, causing delays. Customers may notice differences in performance, where a search might take five seconds today and thirty seconds tomorrow.

It is easier to maintain cost control with VMware compared to other tools. Since payment is based on hardware, scalability impacts are managed more effectively than with other tools paid by data volume.

Support from VMware is competent and difficult issues often require engagement with product developers. While support staff is knowledgeable, getting access to specialists can be challenging when dealing with the limits of a product.

Positive

Previously, we used Splunk for log management but switched due to the high cost associated with Splunk. VMware Aria Operations for Logs allows us to save money while providing effective infrastructure log management.

The initial setup was not difficult as it relies on hardware requirements instead of storage pricing, making budgeting and setup more straightforward.

Using VMware Aria Operations for Logs saves money by reducing the need to purchase logging data storage in other tools like Splunk.

One major advantage of VMware compared to Splunk is pricing. VMware is licensed based on hardware rather than the amount of data, making it much cheaper. Splunk, often paid by the terabytes, becomes expensive quickly if not managed carefully.

We evaluated Splunk before using VMware Aria Operations for Logs. Each tool has different use cases, and Splunk is more like a SIEM solution. For infrastructure management, VMware Aria Operations for Logs is more precise when working with VMware environments.

When working with a specific vendor's tool for managing logs from their own infrastructure, that tool is often better and more precise than others. For VMware solutions, using VMware Aria Operations for Logs provides better data interpretation.

I'd rate the solution eight out of ten.

Negative

It's a vital tool for us when diagnosing performance issues, and recommending upgrades or downsizing, especially regarding CPU, memory, or storage latencies across our infrastructure.

In terms of monitoring and security, it's that we get alerted. We set up a system through another appliance, which is integrated with vRealize Operations for the logs, granular investigation, local analysis, and such.

The real-time log monitoring feature is minimal as we delve into logs primarily for in-depth analysis of significant issues rather than routine monitoring.

The integration is also good. Our setup includes multiple vCenters and hardware products from various vendors, ensuring seamless integration.

The events are notably more descriptive, aiding in security and event analysis. We've also integrated SkyCollector, providing valuable insights and solutions for troubleshooting.

In terms of vOps, we use templates for optimization to monitor heavy hitters on storage and CPU resources. 

In the VMware environment, one area for improvement is the handling of VM failovers due to host failures, such as unexpected shutdowns from hardware issues. 

Currently, High Availability (HA) doesn't seem to recognize whether the VMs are online during failover, treating them as offline or unavailable. I would like VMware to enhance this feature so that VMs do not restart during failover to another host. 

This change would prevent application timeouts and business disruptions, significantly reducing complaints from the business side. Such an improvement in keeping VMs online without restarting during failover would be ideal.

I actively use VMware in my professional setting. It has been over five years now.

We've transitioned from Ops Manager to VMware Aria Operations, now on version 8. We upgraded to version 8.12.1. , build 22481587 We updated it last year. 

I would rate the stability a ten out of ten. 

We frequently receive requests from the business due to our deep intelligence within the group. Our environment has a substantial footprint, making scalability critical. 

VMware Aria Operations for Logs has been instrumental because it facilitates critical alerts via email, set up through SMTP, and through Skyline Collector. 

This functionality is invaluable for troubleshooting, especially during outages, helping us to determine whether to contact VMware or our hardware vendor for support. It provides clarity on which vendor to log a case with, enabling us to make precise decisions.

We have different business units with their own machines, and we grant them access to the console. The OS teams for Microsoft and Linux manage the operating systems. 

This is what we call a managed environment. Including production access, we're looking at around 300 people due to security reasons; not everyone has access, and those who do have power user access, not an administrator.

I would rate the scalability a ten out of ten.

VMware stands out in its product specialization, including engineering, storage, and compute networking. The escalation process is quick, and they are reliable engineers.

So, the customer service and support are good. The escalation process is effective. If an engineer can't find the problem, they escalate it further to a specialized team in engineering, and then possibly to DevOps to look into the code. It's intensive, so for me, it's good.

Positive

I've done capitalized operations, but in the beginning, when we started the VMware deployments, it took me a day to complete because it was not a deployment on a local area network, a flat network, but it was a deployment in a DMZ. 

So, one had to ensure that the rules are in place for port forwarding and such. It was not an easy deployment, but it took me a day to complete everything, including securing the storage.

We use it on a private cloud, on-premises. The private cloud is a VMware internal product. We're not integrated with an external cloud, but we do have Azure and AWS in another team. They run in their own space. 

So, our setup is a pure native VMware internal cloud.

We handle our own maintenance. For major upgrades, we schedule a call in advance with the vendor in case we bump into issues. We perform our own upgrades across our environment, following VMware's recommendations.

We are a team of ten engineers for maintenance and deployment. 

As long as we have documentation from VMware, it's easy to follow instructions, so it's not complex. 

For anything complex, we first upgrade in the lab to see if we are successful. If there are issues, we then involve VMware for assistance, proceed to a non-prod environment, and then into production.

The product's price is reasonable, but when it comes to SQL licensing, it's a bit expensive.

So, it's expensive, not extremely expensive. I would rate the pricing a two out of ten, with ten being very cheap. 

About a decade or 15 years back, we kind of did a POC, but then before even Azure or AWS was in the picture, there was something from Microsoft.

We were just playing around with it, nothing much. But we're not really a Microsoft shop in that context, even though we do have some of their products, but not really with regard to virtualization. We thought VMware was the best way to go.

Overall, I would rate this product a ten out of ten. 

I've recommended this product to friends who work for other companies because companies use different products. We also use vSAN, which is quite a good product as well.

The solution is quite user-friendly.

The tool does not provide a centralized pane for monitoring. We must go to different consoles with different licenses associated with them. Nutanix Prism offers such features in one pane, and there’s no need for additional licenses. Prism also provides life cycle management functions.

I have been using the solution for the past four months.

The tool is highly scalable because we can add nodes on the fly and quickly integrate them. We don't need to put any host in maintenance mode. It can be easily added on when required. It is quite user-friendly.

There are different categories of support. We will not get expert-level support immediately. We must go through some levels of approval. A ticket will first land in L2. Then, the team will log a ticket to L3, which consists of a senior technical lead team.

It takes some time. It's not that fast, but it is okay. If a mission-critical application is expected to have a downtime, we get the support after one or two hours. We cannot reach the senior engineer directly. It will always go from L2 to L3.

Neutral

The Prism console and Aria Operations are both competent enough. However, I prefer Prism. The Acropolis hypervisor is preinstalled in Prism. We just have to integrate the Prism console. All the performance analytics will appear on the central pane of the Prism console. Nutanix Prism is more user-friendly compared to VMware Aria Operations.

Prism is a great tool to have a central visibility for everything. We don't need to log in to another console to visualize something. For example, if we want to do heartbeat monitoring of a virtual machine, everything appears on a central dashboard. We don't need to go to VM to see the performance.

The initial setup was easy because it was a pre-integrated system. It was a quick deployment. We did not have a lot of challenges. The deployment took three days to deploy.

We evaluated Microsoft’s Hyper-V solution. We chose VMware because it's more user-friendly. VMware has a virtualized approach. It is working on improving the solution for a long time. It has good expertise on the technical as well as research front. It continuously improves the products. VMware is better than Hyper-V.

It is a new integration. We can visualize the parameters better once all the systems and features are fully deployed. Overall, I rate the product an eight out of ten.

I primarily use VMware Aria Operations for Logs for troubleshooting and monitoring.

The most valuable features are log centralization and long-term retention for logs. I also appreciate the dashboards. Logs analytics capabilities are part of that too, as they work alongside dashboards. These elements help in retaining logs and providing useful insights.

The tool could be cheaper. VMware has a lot of included packages, however, it remains too expensive. The price is my first point of concern.

I have been working with the solution for more than four years.

In the last year, I haven't experienced any trouble with the tool. It has been very stable, and every time I needed it, it was available and working.

The process is simple and the steps work fine. Deploying new nodes is easy, so I'd rate its scalability highly.

The response time and quality need improvement. It takes too long to prove a problem and get a solution.

Neutral

I also use Splunk in other operations. Splunk is more sophisticated for general logs analysis and multiplatform environments. However, for VMware-specific environments, VMware Aria Operations for Logs is more appropriate.

The initial setup was extremely simple and very straightforward.

The solution could be cheaper. VMware comes with a lot of packages, however, it remains too expensive.

I rate the overall solution a ten out of ten. 

Although I don't like the support and the price could be better, the tool itself is excellent.

There are various use cases for it. We use it for Operations monitoring. It's part of VMware's suite of products, including vRealize Automation (vRA) for automation and vRealize Orchestrator (vRO) for orchestration. Previously, it was known as VMware vRealize Log Insight.

vROPs tells us about the health, risk, and efficiency of our systems. For example, it identifies over-provisioned VMs that can be rightsized. This helps with cost sustainability by reclaiming resources in VMware, reusing them, and avoiding additional servers. That's one benefit.

Secondly, it helps us identify situations where VMs need more resources so we can upsize them before encountering issues. This allows us to be more proactive on potential problems.

The insights it gives for the virtual environment are valuable. vRealize being built on vROPs and Aria being native to VMware are both plus points. However, the landscape is changing, and this is where it gets interesting.

Here's the key difference: If you only care about infrastructure and its management, then vROPs or Aria are great. But today, organizations and enterprises need end-to-end visibility. This means full-stack visibility across cloud, applications, services, all the way down to transactions. That's where other products come into play. 

vROPs or Aria limit themselves to the infrastructure layer because they lack visibility into the layers above, which require additional tools specifically designed for those purposes.

If you only need visibility up to the infrastructure layer, they're good. But that's not enough. Let's say you need a dashboard showing complete visibility for applications and stacks.  As you move up the stack, visibility into just the infrastructure isn't enough. Ultimately, you need to see how that infrastructure helps or hinders the applications and services you deliver to customers. 

That's where other products come into the picture. Now, in my case, I manage the entire VMware stack along with many other systems, creating a heterogeneous ecosystem. The challenge is having to look at multiple management consoles - vROPs for one thing, then somewhere else for another, and so on. What's truly needed is a holistic view, and that's the goal.

One of the things I like about it is its interface. When it comes to generating reports on VMs and stuff, it's very quick. 

This is very handy for the technical team, who need to generate reports quickly. So that's really good.

VMware Aria is suitable for infrastructure visibility, but for a comprehensive overview that includes applications and services, other tools are required.

The monitoring landscape is getting bigger. When it comes to infrastructure monitoring, we need more visibility. VMware needs to integrate more related applications and third-party products. That would make it more appealing to an audience beyond the VMware team.

Let me explain the scenario: Suppose I have a third-party product deployed on top of VMware, like Red Hat OpenShift containers. I generate a report using vROps, and it gives me recommendations related to OpenShift. But I can't apply those recommendations directly because Red Hat (or any third-party vendor) has its own resource management approach. This creates a conflict.

The VMware team, limited to their view of VMware, might think vROps or Aria recommendations are the gospel. But the respective application's monitoring and operations team has a different perspective on resource management. This disagreement leads to operational conflicts.

Now, I understand you can't completely blame VMware for that; each vendor has its own way of doing things. But VMware should somehow bridge this gap. The recommendations coming out of vROps or Aria need to be agreeable to others.

We've been using it since 2016. We've been using it for quite some time.

I would rate the stability a seven out of ten. No issues here. 

Our environment has over 7,000 VMs running on the VMware stack. The product seems quite scalable. We haven't faced any challenges there.

I would rate the scalability an eight out of ten.

We've had great direct support from the vendor, VMware. They've been very responsive. No complaints there.

Positive

The initial setup was quite straightforward. The installation itself is simple. You'll need some time to generate more insightful reports over a period, but nothing unusual. It was quick and easy. The entire deployment took a couple of days.

In our case, the entire ecosystem is completely VMware, so it's very native. We start with ESXi, then vCenter on top of it. Then comes vROPs or vRealize Operations with vRealize Automation (vRA) in between for provisioning automation and orchestration. 

vRA with vROPs helps us provision VMs quickly. vROPs also help get storage from different, non-VMware sources, further improving our provisioning operations. 

Then vROPs or Aria does real-time monitoring and tracks resource usage to ensure efficient compute resource allocation. You don't waste resources; you have them where you need them.

I would rate the pricing a three out of ten, with ten being very cheap. It is not cheap. But it is worth it. 

When it comes to virtualization and server-side virtualization, we've only been using VMware.

For infrastructure resource management within the native VMware stack, I don't think there's anything better.

I would absolutely recommend using this solution. 

Overall, I would rate the solution a seven out of ten. 

I use the solution to troubleshoot performance issues. It has a lot of dashboards. They give us an overview of the performance of the environment. We have several customers. We use the dashboards to see the performance of every customer’s environment. We can deep dive into the environment to see the issues.

I like the interface. I like the way we can build the dashboards. We integrate the solution with other products from VMware. We also have some Hyper-V hosts integrated into the tool. It does not use a lot of power because there is less hardware. It saves a lot of costs. We save almost 30% of our costs.

The tool is expensive.

I have been using the solution for two years.

The product is pretty stable. We haven’t had any big issues in the environment.

We can scale the product easily. We just need more licenses.

We contact support frequently. The support is good. We can call support for high-priority cases.

Neutral

The initial setup took weeks.

The tool is expensive. However, we get a lot of functionality for the price. The solution is worth the money. There are no additional costs associated with the product.

We also use Microsoft Hyper-V for some customers. Microsoft’s support is not as good as VMware’s. Technically, VMware is much better. VMware’s user interface is easy. It is easy to move servers around the environment.

I recommend the product to our customers. Overall, I rate the product an eight out of ten.

I primarily utilize VMware Aria Operations for Logs for analyzing the performance metrics of my infrastructure, especially focusing on performance enhancements. Recently, I've integrated some Cisco hardware with VMware API Operations to extract and analyze relevant metrics. My main goal is to optimize the performance of my infrastructure.

It allows us to gain a comprehensive overview of our infrastructure. We now receive real-time error notifications from the logging side, which has proven beneficial.

I had concerns about licensing, but there have been recent changes starting this month. Previously, we lacked VMware licenses for Operations on certain hosts where project owners were obtaining them independently. Technical support should be improved.

I have been working with it for approximately four years.

It is highly stable.

It offers good scalability, we didn't face any issues with it. We manage both Medium and Enterprise options for businesses.

We weren't satisfied with the technical support provided when we needed additional technical personnel on hand. It's essential to have someone available not just for analysis but also for resolving issues promptly. I would rate it six out of ten.

Neutral

I would rate the initial setup as eight out of ten, so relatively straightforward.

Typically, deployment only requires a few hours.

The pricing has been updated recently. Previously, it was costly.

VMware should provide comprehensive training for individuals tasked with managing their systems. However, the cost of VMware training is currently prohibitively high. Overall, I would rate it nine out of ten.