We use the solution to monitor the capacity and performance of virtual machines.

I use two key features of VMware Aria Operations. The first one is job automation, which helps me to automate tasks and streamline operations. The second feature is capacity utilization analysis. It provides reports and insight into the real capacity utilization of VMs over the past six months.

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

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

We were using VMware vRealize Operations (vROps) for analyzing virtual machines and using it by host. We didn't use the solution for costing or optimization around costing. We used it predominantly for troubleshooting.

We use it for daily administration tasks.

Our clients use VROps to monitor their virtual machine performance, create reports, do capacity planning, and do project planning. We also use the tenant-student app for billing purposes.

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

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.

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

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

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

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

We mostly use vROps for troubleshooting and forecasting. We take some reports from previous months and years for capacity and future planning.

We wanted a tool for monitoring the entire virtualization infrastructure. In addition to infrastructure monitoring, a second use case was application monitoring. At the time we were looking, they had a tool called EPOps through which you could do application monitoring. We also heard about some other components, partner integrations for VMware, through which we could monitor the SAP landscape and storage performance.

I've been using this for managing our company's infrastructure. We have a cluster of somewhere around six nodes. 

We're using it in a hybrid mode. We have our on-premise data centers and we are operating on AWS as well. We have multiple legacy apps which require a certain type of monitoring to be enabled and we kept that enabled from the on-premise, but the advanced features for monitoring are being explored on AWS.

We use it for capacity planning, troubleshooting, and monitoring of our environment.

We provide solutions related to VMware, Docker, and Kubernetes for banking data centers. 

We use this product to monitor virtualization infrastructure and different resources that we use in our project. We implement vROps into data centers that are working together to develop vROps solutions with different interfaces. One of them is Dell EMC Adapter which is added to vROps to monitor and collect various logs related to Dell EMC storage. We also add another plugin to monitor HP.

We host around 1,200 to 1,300 virtual machines. Our data centers have more than 50 physical servers.

Its primary use case has been to give us a proper view of what is happening at an infrastructure level. This is why we opted for the product.

We have more than 137 locations across India. We started using it at a central location where our data center is located and it expanding it to locations. 

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

The most common use case for vROps is to monitor infrastructure. Infrastructure includes, for example, your virtual machines. 

If a customer has an on-premises data center, they tend to integrate their adapters with vROps. This means that if there are any issues, alerts, or anything else that goes wrong with the system, vROps will pick it up. 

It will then use an inbuilt algorithm, depending on the events and alert system that you have configured, to trigger an email. This can help you to avoid a lot of problems in the future. 

For example, if there are a few appliances that are being monitored by vROps and their root directory or any other issues are getting beyond thresholds, say 80%, it will automatically trigger an email. If you have any ticketing system integrated with vROps, it will then trigger a severity one or severity two ticket to the respective team so that they are aware that there is something that might go wrong if it is not looked at on time. 

So, it is basically helping customers to avoid those situations where they might get into any issues or trouble. So, it is monitoring your system. 

Another stuff, so it is like if you want to have any visual representation of the data, of the performances, or of the data that has gone through in the last hour, last week, you can create a lot of dashboards on that, which is a visual presentation of the data. 

So, it helps you in a long way to monitor and understand your environment.

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

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.

We initially rolled vROps out for environment health and for the ability to look at the abilities to stabilize the environment. We've actually been able to take advantage of it also with resource reclamation which was a big selling point for leadership. 

We are branching into NSX. This solution was purchased with NSX to give us more insight into our environment. We're looking to do a lot more microsegmentation and figure out what the workflows are or what the data flow is between applications and between hardware so that we can minimize bottlenecks, get a better idea of performance issues, and be able to really lock down what we're doing for security. We're also looking to make sure that our microsegmentation is set up correctly and that we don't have data leakage in places that we don't want.

Our primary use case is to make sure we're getting the best value out of our on-prem hardware in terms of matching against vendor specifications to actual operation and performance.

Optimization and reclamation.

We use vROps to manage our on-site private cloud as well as our public cloud out in OVH. It allows us to perform trending and analysis on all of our workloads to make sure that they're running as efficiently as possible.

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

Our primary use case for the product is to to look at all of our infrastructure and provide stats to our performance team for most of our applications. We integrate with vSphere and have a fairly large vSan, which we rely on vRealize Operations to keep on top of to let us know if there are disk failures, alerts, or system health issues. This is pretty much the day-to-day triaging problems of vRealize Operations. 

It has been performing very well. We've been a vRealize shop for about five years. There were early kinks in the some of the virtual appliances as we rolled them out, but for the last year and a half, it has been rock solid.

We use it to run virtual machines where we host our applications, web servers, machine servers, and even database servers, then we have segregation where we even have used it both for tests, and on production virtual machines.

We can monitor all of our relevant hosts that are stored from the same single pane of glass. We use it for daily routine operations.

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.

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.

Our primary use case is capacity planning. We do historical metrics gathering to determine if we need to rearrange our hardware resources, expand or contract them.

Our primary use case is to manage our virtual environment, to see where our hotspots are, to see where we can make improvements. It's a driver for us when it comes to purchasing and TCOs, to make sure that our money is focused on getting the most out of what we have, and utilizing the infrastructure we have in place to make sure it runs as efficiently as possible.

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

I use VMware vRealize Operations for troubleshooting, monitoring the storage and network.

We use it daily for troubleshooting. We use it for charting, for reports. It's an awesome product. The performance is good.

We use this product for troubleshooting and capacity planning.

Our troubleshooting steps include checking for performance issues, and that is the main concern. Apart from that, the capacity analysis features allow us to forecast capacity planning. We also use it for performance monitoring.

This product is what we use for all of our L1 and L2 tasks, such as increasing the amount of RAM or upgrading the CPU when configuring our VMs. Each and every task is clearly summarized.

If there is an event, such as a spike in disk activity, we are able to use vROps to clearly explain to the DB team what happened. We can look at a particular disk in the storage and determine what happened. Being able to properly explain it will help the DB team to check it on their end.

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.

For most data center operations teams, it is pretty hard to get a comprehensive view of what’s going on in their IT ecosystem. Virtualization and cloud service abstractions have made cross-platform relationships between different layers of the IT stack more complex. Heterogeneous, hybrid environments are the norm. IT pros have found visibility to be the #1 challenge facing operations teams. VMware Blue Medora management packs aggregate operations data from the leading server, storage,compute and database applications into vRealize Operations for rich analytics and helped to achieve full stack view of the environment.

We are using vROps for its monitoring and alerting mechanisms, for the entire VMware environment. We use the analytics and recommendations.

We use it for monitoring of the VMware environment. 

It has performed well. Though, I haven't found time to dig deep into it.

One use case was to get better insights into the infrastructure, to be able to do things like closed-loop automation, based on the data that we're finding within vRealize Operations. But we're also using it to get a better understanding of capacity within our environment. That was the primary use case. We've expanded those use cases through integration with Log Insight as well.

We're trying to use it for automation purposes, the automation of the process of consolidating hardware. We've had it installed for about 18 months and there's so much more we know it can do, but it's doing everything we know how to do with it right now.

For vRealize operations, we are using it to manage our entire virtual operations. 

Our primary use case of this solution is to monitor the server and desktop environment. We've never had a performance issue.

Our primary use case is to monitor the performance of the virtual machines as opposed to monitoring the performance of the OS. We'll monitor OS and stop at the OS, whereas vROps will pick up what's going on underneath. If the datastore is having a problem, it will bubble up to the VM and show us that.

I mainly use VMware vROps for capacity planning, performance tuning, and lower-sized VMs.

Our primary use case of this solution is that it helps us to monitor and troubleshoot our VMware environment.

We use it to see the actual workloads of the VMs.

We use it for monitoring our VMs and our data storage.

The primary use case of vROps is to balance our infrastructure, both from a predictive and reactive standpoint, for outage and maintenance.

We use it for data center virtualization and management.

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.

We are using vROps for checking performance and trends in the future, so we can plan our departments correctly, and make the correct calculation for new hardware, etc., for the future. The solution is performing very well for us.

We use this solution solely for reporting purposes.

We use this solution for creating workflows and managing different clouds. We are system integrators. I'm a project manager. 

I work for a Post Office service and we use this solution to monitor business core assets which help to deliver packages. There are many applications we need to monitor as part of our service and to see their availability. We also use it to analyze and to forecast. Finally, we use it for business reports for sharing the status of memory, CPU, and data storage. The solution is very big in terms of how many variables you can extract.

We have been able to use vROps to optimize our environment and do right-sizing for most of our VMs. vROps has also been able to help us in regards to forecasting and adware procurement. Therefore, we can see our utilization in the next six months and how we have been trending.

The company is multinational. We are still running on-premise with a plan of moving to the public cloud. At the end of the day, it will probably be a hybrid environment.

Our primary use case is to have everything on one dashboard in which we can look after our operations and get alerts.

We are using it to monitor our whole infrastructure, integrating SAP, and using the Madura plugin. We love it.

We mostly use it for debugging or troubleshooting when some application doesn't work. We can look at the vRealize Operations Manager and troubleshoot from there. 

We also use it for capacity planning. 

We use it for proactive and reactive monitoring. 

We use it for analytics, graphs, etc. We use it for some reports, but not too many.

At Western Carolina University, we have a lot of classrooms that are going on, a lot of logins, a lot of thin clients. Right now, we mostly want to see usage. Also, we want to troubleshoot any kind of issues we may be having.

We primarily use it for monitoring our VDI environment and the performance is okay.

We use it to identify performance issues and configure compute resources.

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.

This year, we introduced the vROps feature to our platform, as part of our infrastructure.

The main use is to provide us with visibility of our environment. It helps with proactively detecting and dealing with issues that may arise, such as problems with our hardware. It provides us with alerts when there are things that we need to perform. For example, it may say that I need to expand my disk space.

From my perspective, the visibility that it provides into our apps and infrastructure is fine. There are no concerns or issues because we only use VMware.

We are currently integrating it with different VMware products including vCenter and Cloud Director. 

Our primary use case is for monitoring as a service for cloud clients, which generates early metrics that can be detected on time and corrected, the added value that this service has delivered a feature in the form of the cloud of the corporation. The administration is very intuitive, however, you must have high knowledge of management of virtualization components. Additionally, service components and licensing topics must be kept up-to-date by verifying the cost-benefit to deliver as a service aggregated that have this service we deliver as a feature in the form of the Cloud of the Corporation.

Our primary use case of this solution is that it enables us to show value to our customer. We show them how they can get the most out of their state. It also shows us our investment and what we can do better to enhance our environment to get the most out of it.

We use vROps to gather all of the information about the infrastructure. We have a huge infrastructure which means that we need a central location where we can find anything and any kind of data. We also massively use it for reporting. 

Our primary use case of this solution is for collecting performance metrics and also for troubleshooting some performance issues. 

We use it to obtain an overview of what is happening in our cloud infrastructure, e.g., our utilization, trends, and how long before I need to upgrade my hardware,

1. There is the VMware environment for our operations.
2. We have another instance running for the VDI environment.

The primary use case for it is monitoring our VMware state and helping with troubleshooting the VMs. In terms of the performance, it works well for what we're using it for. We hope to expand its use in the future.

Primarily, today, we use it for troubleshooting problems and being proactive in the management of our capacity.

My primary use for it is monitoring and making sure that there are no issues anywhere. You have the various content packs that keep track of all of our different products and the various things we're using within the enterprise. It's a good central point for management. The performance has been good.

We mainly use it for analytics, to get insight into what they're doing, to go above and beyond what vCenter does and into actual time-based analytics.

We use it to monitor our virtualized infrastructure.

We use it for troubleshooting and capacity planning. The current version I'm running, 6.6, performs as I want. In the newer versions, they've removed some functionality and I actually discussed that with the product manager yesterday.

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

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.

Our private data center has been built on VMware technology. We are using vSAN and we use vROps as a monitoring solution to monitor the full stack, from applications to hardware. That includes the servers and Cisco switches.

The solution is deployed on-premises in our private data center.

We primarily use this solution to look at our workloads and determine where there's an additional need for space or capacity needed as well as how to optimize it. We've been using it for a few months. 

The primary use case is that we are transforming our customer's physical and virtual infrastructure, who are afraid of anything that can happen in a virtual environment. Our job is to make a sort of private cloud, not to sell virtual machines, but to host the workload.

The primary use case of this product is to essentially integrate third-party applications, as well as appliances, with the vRealize Operations for monitoring and capacity planning purposes.

Primary use case for vRealize Operations is from an optimization standpoint. We're actually getting analytics from our VMs for over-provisioned VMs, under-provisioned VMs, and making the adjustments accordingly, per the recommendation from Operations.

Our primary use case for vROps is enabling operational efficiency in the data center from a support perspective. We use it to diagnose problems and look for proactive signs of failure. This makes a big difference on the troubleshooting side.

I work in property and casualty insurance.

Our primary use case is to monitor our servers and infrastructure, provide alerting for any type of system issues that we have had, and give us real-time alerts to go into the system, troubleshoot, and deep dive into what the issue may be.

vRealize Operations Manager is mostly used for troubleshooting and doing health checks for virtual machines, to make sure that they're running efficiently and that there are no performance problems for the customers' uses.

The performance of the solution is sufficient. It has gotten much better as the program has developed. I know that the new version 7, which was just announced, is supposed to be even better than the last version, and that version was awesome.

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

It's typically used for our interactions with our software engineers, especially when we are configuring or assigning resources to them. It is the way we get the virtual machine to be right-sized. They usually ask for more resources than they need and with this tool I can manage the resources.

VMware vRealize Operations combines multiple VMware components to deliver integrated performance, capacity, and configuration management capabilities for VMware vSphere, physical and hybrid cloud environments.

I have used VMware vRealize Operations for automating the configuration of provisioning various workloads for our ICT Operations staff.

We use vROps primarily for maximizing efficiency across the boards. We also use it for monitoring servers, seeing where we can gain back some efficiencies, and where we're wasting resources.

We use this solution to determine what systems are being utilized and whether there are issues with VMs.

We use it to manage our VDI infrastructure.

vRealize with vCenter is primarily used to monitor our EMR platform for our hospital, and overall, it gives us good insight into what's happening and alerts us to possible conditions. For the most part, it's pretty much right on target.

We use it for monitoring and maintenance of VMware environments.

We use this solution to see what we have inside of the virtual environment. We can see the compute nodes and what issues it has. We can also see the networking, data storage, all the recommendations, the issues, and the compilation as well.

The primary use case is operations management for our customers, who are looking for more insight into their environments.

Our primary use case is monitoring and reporting on our VM infrastructure for student-facing applications, classroom-facing applications, and data center infrastructure like AD and DNS.

It has performed really well. I have been using it since whatever it was called before vROps, so I have been using it for a while. It works really well.

We use it to monitor our private cloud.

Our primary use case is to automate workflows within the corporate data center and to automate in and out of the cloud, spinning up workloads in both locations. So far, the performance has been great.

We have heavily invested in VMware technology. We're running vSphere, we're running other products, and obviously, we need visibility into our environment.

In my previous organization, the basic utilization was to monitor our systems, to do a better job than just performance counters were showing within vSphere.

It was a medical institution and we had implemented a solution called Epic. Epic is a big medical system for things like admitting, billing, patient documentation, etc. It's massive. vROps has a plug-in that actually monitors Epic systems.

In my current organization, it has been performing really well. My current job is also medical and we are going to be using it for the same purposes: Not only monitoring hardware, we're also going to be using it to monitor Epic.

I use it for monitoring and capacity planning.

I work with the solution's dashboards to monitor capacity. There are many functions in the tool and I have worked with a lot of different kinds of data from vROps. It's a great tool to work with.

Our primary use case of this solution is to monitor our systems and capacity planning. It has been performing great. It's a little bit of a beast to run sometimes, a lot of knobs and dials, but it runs well.

Our primary use case is for the developers to test code. Our customer care uses it to troubleshoot customers' issues. We also have a training business unit and they use it to deploy classes for customers to train. We've been using it for four years and it has been performing well. It does the functions that we need it to. We do have some issues from time to time. We're looking for more maturity out of the product but it's getting better with every release.

We use it to gain more insight into our environment, with a simple, easy-to-use interface. We are a small team looking after a very large environment and without it we would be lost on a day-to-day basis.

The insight that we get from all our vSAN clusters is probably our biggest use case, and where we get the most use out of it.

Our primary use case for this solution is to troubleshoot workloads. 

We use it to optimize and scale directory infrastructures from our customers.

We use it to monitor our system utilization, in terms of disk I/O, in terms of CPU, in terms of memory.

We use it for looking at the resources on our hosts and for looking at the resources on VM as well.

We use it for capacity management and optimization. We are just now really getting into using it.

Our primary use case of this solution is mostly monitoring and the capacity for tracking. The organization I work for has lots of different data centers. Our team is responsible for monitoring how much capacity is left. 

We primarily use it for performance and monitoring and troubleshooting for our virtual infrastructure. We also use it to monitor and troubleshoot our Dell EMC storage arrays.

We use it as a monitoring tool for our environment, it alerts us on the VM performance, capacity utilization. We also use a bit of the trending tool that it has.

Our primary use case is to manage our huge VMware infrastructure based on the public and private cloud and dedicated infrastructure. We use it to see if the VM is a good or bad size and to see if we can reduce the cost. We also use it to adjust the memory, and CPU, and to increase the network storage.

We are deploying this solution to monitor our customers' environments. We use it to look at IOPS and the VMs and for monitoring consumption.

We use it to monitor our virtual infrastructure for VDI. It is also used in our server infrastructure for basic monitoring or solving issues.

Our organization is a government company which is focused on thinking about other nations and companies.

Our use case is the monitoring of our storage system. 

We had Oracle running on VMware and wanted to have some metrics about the performance. Also, we wanted some metrics and benchmark tools for our applications, which are highly critical and latency sensitive, to integrate into dashboards so we can pinpoint issues and how they are related.

We use it for analytics and metrics of the system. We've had it installed for about a year but have really been using it just within the last month. We're still discovering the power behind it and what it can do for us.

I use it for capacity planning and day-to-day metrics for how VMs are running. Most people think their application isn't running fast enough, so you need some numbers or pretty pictures to show them. vROps is a good place to obtain them.

Optimization of our virtual environment.

I use it on a daily basis to make sure that the VMs are up and running and that there aren't any issues with any of them. If there are, then it tells me exactly where to go to fix them.

We mainly we do a lot of reporting, trending reporting, with vROps, monitoring on a day-to-day basis.

I mainly use vROps for dashboards in our main IT screens to monitor the environment and track information.

For our clients, vROps is used for managing their environments, having a single pane of glass, so they can go in and have a view of what's actually going on in their environments. That's especially true when it comes to TCO perspectives. When it comes to the TCO, they get to realize how they can start trimming down VMs that are not working, or cutting down on the resources that those VMs are using. That helps them do better in their environment and to lower their operational costs at the end of the day.

We do have the big enterprises; we've got quite an extensive team that looks after clients. But my clients are SMB clients and are where we see a need for vRealize Operations.

Our primary use case of this solution is to use it as an operations tool.

We use vRealize Operations to monitor and do capacity planning for our clients. We integrate into our architecture's environments. Mission-critical on IBM clouds was announced and so we use vROps quite extensively in all of this architecture.

Our primary use is to go back and review CPU utilization over a time period, and to reclaim resources from VMs that have been deployed.

The company I work for is Sureskills. We're a consultancy based company. We have multiple customers that we sell a lot of virtual products to. We don't just deal with that. We deal with a lot of Microsoft, Stack, and Dell EMC products as well, but we do an awful lot of VMware based products. 

Our primary use case is two-fold. From one perspective it gives the local on-site IT people some ability to see what's happening with their virtual state and let them know if there's any issues or problems that may be starting to come to the surface. Secondly, from our perspective, because we provide support to these companies, it allows us to quickly see from a number of different reasons why there would be issues from this. It's useful from both sides.

Our primary use case of this solution is for the performance monitoring. It's been performing well.

Our primary use case of this solution is for the capacity planning and also for the monitoring.  It has helped us get a clear view of the infrastructure. We spoke to people from VMware and realized this was the right solution for us. 

We're currently using it for reporting, mainly to see where we're over-committed or under-committed on resources. Right now we're still in the process of going through it on a daily basis, to see where it's going to help us improve things.

We use vRealize to monitor the health and status of our VMs, all of our hosts, and anything of that nature within our vCenter environment.

I use it for monitoring and DRS automation.

It moves our projects faster. We also use it for alarms.

Our primary use case of this solution is for monitoring our VMware infrastructure, vCloud Director, and NSX Manager. 

We use it for monitoring and troubleshooting the performance and stability of our VMware.

We use it for a general health check of the environment: What is broken and what is not performing right. 

We can do a lot more with it, and we want to, but we haven't gotten as deep into it as we want to.

We are using it to monitor our virtualized environment, to take care, ahead of time, of any problems that develop, before they become major crises. It's a complement to our existing monitoring solutions.

We use it to monitor our VMware infrastructure.

We use vROps for our many VMware infrastructures. It is mainly for IT operations because we're processing a lot of information. vROps is good for us for reporting and for monitoring hosts and VMs.

We use it for making VMware assessments.

I am a system integrator, so it's not implemented in my organization. I implement it in other customers' organizations.

I use it for full diagnostics and predictive problems for the applications or services that we run.

We use it for managing all of our hardware, the ESXi operating system, and associated VM technologies. It performs fine.

The primary use case for our organization is forecasting and troubleshooting.

We use it to monitor old ESXi's, the storage, the vCenters, the Brokers, to see if they have enough memory, CPU; to make sure they're not overloading the network.

We use vROps to monitor and manage our environment. We sell VMware as a cloud to private cloud and to big companies who don't choose to install VMware on their site.

The analytics and operations management are our primary use cases of this solution. It's been performing well. 

Our primary use case is to see what's going on with the complete infrastructure and to be able to see if there are any issues. Although it's not in real-time, we still use it effectively. We can see what the state of our environment is.

The primary use case of this solution is to monitor the user experience of our VI in finance and troubleshooting.

• Capacity management
• Performance management
• Troubleshooting

We use it for various operations to monitor and have some visibility over the platform.

We use it to help us optimize our environment and make better use of our resources.

We use it to monitor our entire infrastructure, scaling across everything compute and our Horizon implementation.

We mostly use it for monitoring and making sure that we have all of our systems right-sized. We also use it for digging in, looking at things whenever we have issues, like storage issues, etc. We don't really use it for monitoring network flows.

I use vRealize Operations to do integrations with Log Insight, vSAN, NSX, and vCloud Director (vCD).

I have used it to pull recommendations for our data center or cluster and load balancer, then apply them.

We use VMware vRealize Operations (vROps) for IT administrators to monitor our environment.

We use it to monitor our system and optimize performance.

We use it for our virtualization and infrastructure. It's used for a lot of clusters, a lot of hosts, VM workloads on-prem and a little bit off-prem. It's doing great. Really no complaints.

We use it to monitor applications, infrastructures, and operating systems.

Our primary use case of this solution is to gather analytics. We don't use it very often but it's working and collecting data. 

We use it to monitor performance.

Our primary use case is to automate redundant tasks. We're limited to two guys, so automation is beneficial. We'd eventually like an implementation of ServiceNow later down the road.

My main uses are monitoring performance reports and connecting to the VMware login site.