How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
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 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 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.
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.
Our primary use case of this solution is for collecting performance metrics and also for troubleshooting some performance issues.
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 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 monitoring our VMware infrastructure, vCloud Director, and NSX Manager.
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.
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.
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.
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 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.
Our primary use case of this solution is that it helps us to monitor and troubleshoot our VMware environment.
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 use this solution to determine what systems are being utilized and whether there are issues with VMs.
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.
We use it for monitoring and troubleshooting the performance and stability of our VMware.
* Capacity management * Performance management * Troubleshooting
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,
I use it for full diagnostics and predictive problems for the applications or services that we run.
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.
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 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.
We use it for monitoring of the VMware environment. It has performed well. Though, I haven't found time to dig deep into it.
We use it to monitor our system and optimize performance.
We use it for managing all of our hardware, the ESXi operating system, and associated VM technologies. It performs fine.
Our primary use case for this solution is to troubleshoot workloads.
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.
We use it for analytics, graphs, etc. We use it for some reports, but not too many.
We use it for proactive and reactive monitoring.
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 to monitor applications, infrastructures, and operating systems.
We are using it to monitor our whole infrastructure, integrating SAP, and using the Madura plugin. We love it.
We use it for various operations to monitor and have some visibility over the platform.
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.
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.
The primary use case of this solution is to monitor the user experience of our VI in finance and troubleshooting.
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.
Our primary use case is to have everything on one dashboard in which we can look after our operations and get alerts.
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 optimize and scale directory infrastructures from our customers.
The primary use case is operations management for our customers, who are looking for more insight into their environments.
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.
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.
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.
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.
Optimization and reclamation.
Our primary use case of this solution is to use it as an operations tool.
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.
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 it to identify performance issues and configure compute resources.
It moves our projects faster. We also use it for alarms.
We use it to monitor our virtualized 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.
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.
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.
We use it daily for troubleshooting. We use it for charting, for reports. It's an awesome product. The performance is good.
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.
We use it to monitor performance.
We mainly we do a lot of reporting, trending reporting, with vROps, monitoring on a day-to-day basis.
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.
We use it to monitor our entire infrastructure, scaling across everything compute and our Horizon implementation.
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.
We use it for monitoring and maintenance of VMware environments.
We use it to help us optimize our environment and make better use of our resources.
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 of this solution is to monitor the server and desktop environment. We've never had a performance issue.
We use it to monitor our VMware infrastructure.
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.
I use it for monitoring and DRS automation.
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.
Optimization of our virtual environment.
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'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.
We use it to monitor our system utilization, in terms of disk I/O, in terms of CPU, in terms of memory.
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.
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 use it to monitor our private cloud.
We have heavily invested in VMware technology. We're running vSphere, we're running other products, and obviously, we need visibility into our environment.
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.
Primarily, today, we use it for troubleshooting problems and being proactive in the management of our capacity.
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 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.
We use it for capacity planning, troubleshooting, and monitoring of our environment.
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.
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.
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.
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.
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.
Our primary use case of this solution is for the performance monitoring. It's been performing well.
The analytics and operations management are our primary use cases of this solution. It's been performing well.
We use it for monitoring our VMs and our data storage.
We use it to see the actual workloads of the VMs.
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.
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.
* There is the VMware environment for our operations. * We have another instance running for the VDI environment.
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.
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 it to manage our VDI infrastructure.
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.
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 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.
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.
We primarily use it for monitoring our VDI environment and the performance is okay.
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.
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 looking at the resources on our hosts and for looking at the resources on VM as well.
The primary use case for our organization is forecasting and troubleshooting.
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.
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.
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.
For vRealize operations, we are using it to manage our entire virtual operations.
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.
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 use it for capacity management and optimization. We are just now really getting into using it.
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.