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.
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.
With vROps, we have had the opportunity to increase our capacity. After vROps was installed on our infrastructure, we were able to view the impact that VM lag could cause in our environment and how we could modify such impact. It has helped us increase performance.
vROps has helped to decrease overall downtime. For example, when we planned capacity for new infrastructure, vROps was used to analyze the new projects that we needed to deploy. In some of those cases, there were many VMs to deploy and we didn't know what impact those VMs might have on the infrastructure, in terms of CPUs and memory. vROps helped us understand the particular impact of the new VMs. It reduced overall downtime by about 30 percent.
Using the solution for capacity allocation and management has also helped us to save on hardware costs, by about 20 percent.
Overall, it's a good platform and it's important to us for maintaining our environment. The challenge in maintaining our environment is made much easier with vROps. The tool provides us with the ability to respond to the causes of problems with VMs or the environment and this is power in our hands. For us, it's a powerful tool when it comes to IT infrastructure.
The monitoring features are great. I have gotten great value out of the data collected by the tool. The monitoring provides us with the ability to respond to the causes of problems with VMs or the environment.
The capacity planning is also very good because it gives me an opportunity to make a reasonable plan for increasing my infrastructure. It fills important functions for both monitoring and capacity planning.
The visibility it provides from apps to infrastructure and across multiple clouds is also great because it's a tool that aggregates a lot of data, both on-premises and in the cloud. It aggregates everything in one tool, which helps you to analyze the performance and the capacity of the infrastructure.
We have integrated vROps with vRealize Log Insight as well. We generally use vRealize Log Insight to identify, through the logs, what is happening with the VM or the infrastructure. The integration with vROps means we can look deep into the cause of a problem. The tools work very well together. vRealize Log Insight provides us with many tools and many ways to solve our problems.
I've been using VMware vRealize Operations for about five years. I have had the opportunity to work with vROps since version 6.57, and I have started working with version 8, which is the latest version. I have installed vROps for two companies.
It provides great stability, when you follow the recommendations.
As for scalability, if you follow the VMware documentation, you can have a great solution.
We have about 500 VMs in our production monitoring. Right now it is on-premises only. We intend to start using cloud, and vROps can be the tool to monitor the cloud environment.
We have had a good experience with the support for the vROps tool, although we haven't had to use support too much.
We did not have a previous solution.
The installation was straightforward. It followed VMware principles that result from working with vCenter and VMs. It's easy to implement.
At a maximum, it takes 20 to 30 minutes to set up, but the configuration can take one or two hours. Building deep reports can take even longer.
The tool is user-friendly, but you need to study to learn about the many features that the tool offers. It is not a tool that you can just start to work with when it comes to capacity planning. You need to study the documentation. But for monitoring, you can start using it right after installation because the data is easy to understand.
Overall, the value is worth the cost because it's a tool that connects with our VMware infrastructure very well. It's a solution that our provider, VMware, developed for VMware itself.
The cost is simply something we need to pay. We can't evaluate the price because we use a VMware environment, so it makes sense to use a VMware monitoring tool.
We use vROps in our VMware environment, but we have Zabbix to monitor other environments. It's a challenge to consolidate all that into one tool. I don't know if that will be possible, even in some months or years.
I recommend following the vROps documentation and, in some cases, it may be necessary to use a VMware partner.
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.
There was a system with a Docker cluster that was having really bad issues. A server would go down and the machine would move to another server, in this case a virtual machine, bringing down the whole cluster. Thanks to vROps I was able to closely check the resource usage to spread the load, so instead of having three servers we moved to a more stable solution using eight servers.
vROps has helped to decrease overall downtime by about 20 percent.
In addition, we work here with a five-year budget and we need to have a really good forecast to design solutions because those solutions must last for five years. It's not easy to increase the resources of a solution in the middle of this five-year cycle. So vROps helps a lot in seeing how the load is increasing over time. In that way, I can forecast for more than a two-year period and do so for five years, at least.
The most valuable feature is the ability to check the right-sizing of a machine because that way I can assign the real resources that are needed.
It's also user-friendly. One of the things that I really like are the ready-to-use dashboards. You can get them from a dashboard marketplace where dashboards are contributed by other people. You can use them in your facility without any problem, and some of them are really useful.
The solution also provides proactive monitoring. It's good to have a baseline of how the machine is normally working. After that you can check if it has gone beyond this baseline. If something goes away from this baseline, it usually means you have a problem and you need to fix it.
There is room for improvement when it comes to the integration with Active Directory. Sometimes I need to log in to the application using my Active Directory account, instead of using the regular admin for vRealize Operations. If I want to deploy this tool to more users, I need that.
I used vROps a lot about two years ago and I started with it again about two months ago. I'm the person who designed the whole VMware solution at ALMA Observatory and I support all of it and administer the VMware platform, among other things.
It's quite a stable solution. I have never had a problem with the solution. Every time I want to see something or check something, it's always there.
I have not needed to call VMware for technical support for this solution.
We did not have a previous solution. We only used the typical solution in vCenter for checking performance.
I wouldn't say that vROps replaced a lot of other tools but that's because there aren't too many products that are similar to vROps.
We were already customers for vROps, but at first we were not using a lot. Then we needed to do an upgrade and it was not an easy path to follow. But in terms of the setup and configuration, it was straightforward and much better than the old versions. The last version I used was v4 and, compared to that, it was completely easy.
The deployment, even though I was doing other stuff, took one or two days.
I don't think the solution saves us money, but with it I can better say how the money is spent.
We provide services to our scientists. I can say, "I will provide you with 20 virtual machines, 20 TB of disk, bandwidth, and I know it costs X. The biggest impact is the way I can see where the resources are that we are using. That makes it worth the cost.
The pricing is a little bit expensive.
Licensing is an issue because there are always changes, and by that I mean cost increases. And that's not only for vROps but for VMware, vSphere, and all the products that are involved.
I used Turbonomic a long time ago, but only as a test.
The implementation is easy. You just need to assign resources to install all the virtual machine requirements, but the process is straightforward. My biggest advice is to check the dashboard marketplace because you can find dashboards that are useful to you too. The dashboards are produced by the community. They are free, although some of them need container packs that you need to pay for, or you may need a licensee to use some of them.
We mostly use vROps for troubleshooting and forecasting. We take some reports from previous months and years for capacity and future planning.
We mostly use it for infrastructure. I know there are many packages for different apps from other vendors, but we mostly use it for VMware infrastructure. It gives us a good look inside our infrastructure, mostly in terms of capacity and reporting.
We have benefited mostly from capacity planning. During some days of the month, we have huge traffic and workloads on our systems. So, we take the previous month's reports and see the month-to-month growth so we can plan next year's capacity planning.
We have integrations with other monitoring systems, so we mostly use vROps for troubleshooting.
We mostly create our own alarms and dashboards. We use the metrics in vROps with these dashboards.
It is efficient and easy to manage. We can find what we need from the software's interface.
We did an integration with vROps and Log Insight. We use Log Insight mostly when troubleshooting and creating some alarms to send us notifications
Lately, the chargeback site has improved, but it could be simpler. You need to create your own dashboards. It should be simple to get a virtual machine and break down the compute and storage costs.
It is not real-time. It takes samples every five minutes. Therefore, we are not using it for real-time purposes.
I have been using it for more than five years.
The stability is pretty good. Besides upgrades, we don't have issues with it. There are some issues during upgrades, but I think that is normal. Sometimes, we have some errors during upgrades where we have to start over or fix some things.
Scalability is easy. You can create other vROps machines and add them to the system, making it run like a cluster. It is easy to add more depending on your requirements.
We have a couple of thousand VMs in our environment.
About 10 to 12 people in our team are mainly managing vROps demand. From time to time, it changes but other departments also use it. They don't have administration permissions on the system, but they can create their own views, dashboards, and alerts. So, many people are using it,
At my last company, we changed our monitoring system from another tool to vROps because we were not getting actions from it. Therefore, we decided to change it to vROps. Because vROps is a VMware solution, it was easier to integrate and use.
I have used two other monitoring systems. However, I didn't use them for a long time. One was very simple, doing basic monitoring, and the other was a Microsoft tool. They both have many pluses and minuses.
vROps is mainly for virtual infrastructure. The other solutions are for both physical and virtual LAN infrastructure.
The initial setup was not that complex. It was easy to set up and integrate.
The initial setup was just a couple of virtual machines, so it was a very basic installation. It was very fast. However, the implementation of the infrastructure takes months because we need to see how the system works, then decide what to monitor and report. This takes at least a couple of months.
We talked with VMware to set up a straightforward installation of the vRealize suite: Log Insight and vROps.
vROps has helped to decrease overall downtime by about 10%. We have many other monitoring solutions. This solution is just a part of our underlying infrastructure.
Log Insight has had a good effect on our overall troubleshooting. We have a huge infrastructure and can't always individually monitor it. We also did some automation for alerts.
The value that we get from vROps is okay. It could be cheaper.
I would recommend doing a PoC before using it. You can get a trial license for 30 or 60 days, so you should test it in your environment before implementing it. You should have some hands-on practice because it may not fit with your environment.
The solution is a little bit complicated to use at the beginning. When you get how it works, it is simple. You can easily make or use dashboards, notifications, and alarms.
vROps capacity allocation and management has helped us save on hardware costs, unneeded licenses, power, or other data center costs. It is not the only solution or system that we use for these purposes, but it helps.
I would rate this solution as an eight out of 10.
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.
This product contains features for proactive monitoring but we do not use it because we have our own monitoring solution. It can do things such as sending an email in response to an event.
The most valuable feature for me is the pre-implemented, existing dashboards. The fact that I don't need to create a dashboard myself is helpful. You have the option to create them but most of the dashboards and reports that we need have already been created.
I have not compared the vROps interface against other similar technology, but with respect to it being user-friendly, I haven't had any issues with it. The most commonly used functions are easy to access.
As somebody who works in operations, the capacity management features are very important. It's a very good product in that regard.
I would like to have more documentation, in the form of knowledge bases, that better explain the technology, related products, and what the capabilities are.
Having an installation guide that assists with installation and integration would be helpful.
I have been using VMware vRealize Operations for approximately six months. We are still in the beginning phase.
To this point, I haven't encountered any issues or had any alerts with this product. As we grow, maybe later it could happen, or we could experience instability in the product, but for now, it's okay.
Scalability-wise, it is good because you can create your own reports. There is no default report, but you can create your own templates or your own reports. You always have the choice of creating a new one or using an existing one.
The infrastructure team is the one that works directly with this solution. As part of that team, we provide VMware features and virtualization for our customers. There are five or six of us on the team.
We have not been in contact with technical support.
Prior to vROps, we did not use another similar solution. We implemented it in order to have as much visibility as possible for resource management. Previously, we only knew about the CPU consumption. Now, we can use the reports to better check the resources.
The initial setup is straightforward. It is just a matter of installing the appliance, setting the IPs, etc, and then performing the integrations between other VMware components. The configuration took approximately two hours.
I completed the deployment on my own.
We did not evaluate other similar solutions prior to implementing vROps.
As we are still in the beginning phase, we have not yet worked with all of the features. For example, I know that it can connect with vROps Log Insight, but we have not integrated it.
Given my experience, I'm not sure at this point whether this solution is applicable to other technologies such as AWS or Azure. However, if the support exists, it is very good because future environments and implementations will rely on multiple technologies. It will not be VMware alone, but rather, it will include AWS, Azure, and others. Support for all of these options is very nice. It appears that VMware has this vision because they already have support for the NSX and NSX-T network technology.
I expect that it will save us money in the future, but still being in the implementation phase, we have not yet had this experience.
My advice for anybody who is implementing this product is to plan for integration with your entire platform and VMware products, such as Cloud Director.
Overall, this is a good product that is easy to install and use, and integration with other products is smooth. Although we have not used all of the features, it does provide us with good visibility.
I would rate this solution an eight out of ten.
It was helpful in identifying the CPU, memory, and space utilization, which was very much important for us. We needed alerts when the utilization increased a lot, and we were able to inform the customers that we have a particular problem that could be the root cause of the problems that they might face later. They were then able to take some preventative measures in advance, which reduced a lot of problems.
It was very useful for regular monitoring, disk utilization information, and root cause analysis. It was also helpful in identifying why a specific issue is happening or why an error is occurring.
It enabled us to be more proactive in anticipating and solving problems. We could know beforehand about the machines that might be at risk for high utilization.
Alerts and monitoring were most valuable. It was also pretty user-friendly and interactive. I was able to generate good reports in PDF and HTML formats, which was really helpful.
The visibility that it provided for our infrastructure was pretty good. The snapshots were also useful.
vROps did a lot of monitoring, but in one case, we had to use Log Insight instead of vROps because vROps was not able to install the agent to enable us to have multi-monitoring. I don't exactly remember the case, but it involved monitoring all applications.
It wasn't exactly proactive. It was supposed to, but there were a lot of delays. It could also be because of our infrastructure and the way our network was set up. If vROps could be more proactive, that would be nice. It is nice to have the information beforehand, but when there is downtime, it takes a lot of time for us to be able to see an issue in real-time, which becomes a bit challenging. If there is a way to improve the data collection for the whole vCenter that would be nice because data collection takes a lot of time.
I used VMware for around five years, from 2015 till January 2021. Except for vCloud Director, I've used most VMware products such as vSphere client, Log Insight, and vRealize Automation.
It was pretty stable. I didn't find many errors while deploying the application and after the deployment.
Our environment didn't scale much, so I cannot comment on its scalability.
We had four vCenters. One was in Santa Clara, US. One was in Beijing, China. One was in Manheim, Europe, and one was in Singapore. We also had test centers, and we integrated vROps for testing there. We had one in King of Prussia and one in Switzerland. So, majorly, we had four vCenters for the production environment, and these vCenters worked with around 4,000 virtual machines.
I have not used VMware's support for vROps.
This was the first tool that we tried to deploy for monitoring.
I was involved in the initial setup of vROps. It was pretty straightforward. Most of the VMware products are pretty straightforward to install.
In terms of the implementation strategy, we have always followed the documentation provided by VMware.
We tried to evaluate many solutions, such as Prometheus, Dynatrace, Nagios, and PRTG. It was best for us to go with vROps because it is a VMware product, and it integrates best with VMware vCenter.
I would recommend vROps for an Enterprise environment. Based on my experience, it is a great tool to work with. Rather than having a big vCenter and then installing vROps, it is good to have it when you're starting with a vCenter. That's because data collection takes time, and it would become an overhead for vROps. In such a case, you might need a load balancer and multiple vROps. So, I would recommend having a vROps when you start building a vCenter. It will really help in scaling up the environment, and you'll also know if you'll need to replicate vROps or not.
We didn't use it for workload placement because we didn't have the load balancer for that. It didn't help much in decreasing the overall downtime, and it also didn't affect our operations when it comes to overall downtime due to performance issues.
I would rate vROps an eight out of 10.
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.
Using VMware vRealize Operations with Blue Medora TVS helped to centralize data center operations monitoring platform. By adding the True Visibility Suite, its helped to monitor applications, database, virtualization/cloud, compute, network and storage using one monitoring platform.
All the Blue Medora vROps management packs have features like:
· OOTB dashboards
· Collected metrics
· OOTB Reports
· Alerts and recommendations
· External relationships
· Capacity planning
One missing component was the integration of Log Insight and vRealize Business within vROps. But, with the new version of vROps (v6.5 & v6.6), this requirement was also met with, as the other products in vRealize Suite are now fully-integrated.
More than five years.
As such, no stability issues were experienced from vROps during deployment, configuration, and the collection of metrics and data into the platform.
The client decided to add an additional node to increase the capacity and resources within vROps analytics cluster so it could support the additional metrics collection process. You can scale vertically or horizontally.
I have received excellent support from VMware & Blue Medora support team.
Yes, Engineered by Blue Medora and validated by VMware, the True Visibility Suite included an extensive knowledge portal and includes 24/7/365 individualized technical support
It was implemented in-house
By using vROps plus Blue Medora TVS you can Maximize Performance, Minimize Investment
Reduce the IT tools, eliminate silos and boost IT productivity by up to 67%.
• Deploy in minutes without additional services or expertise.
• Maintain performance, reduce administration with agentless design.
The True Visibility Suite is available in three editions: Standard, Advanced and Enterprise.
These packages align with the various infrastructure teams, and offer a convenient
way to pick the best package that applies, without being tethered to just one vendor or
There were a couple of options that we considered, like Microsoft SCOM and SolarWinds, but the level of monitoring and dashboard visibility wasn’t there.
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.
It enables us to monitor the full software-defined infrastructure from the app level to the hardware level. This is the main benefit for our organization.
When there is an issue at the disk level in vSAN, vROps gives us an alarm that the issue is happening on particular disks. Other solutions cannot give this type of alert for vCenter. Even vCenter cannot give that type of information. That's what makes this feature valuable for me.
The visibility it provides from apps to infrastructure is very good, compared to other monitoring solutions in the market. We have used other solutions, and we are still using them, but for monitoring your VMware infrastructure, vROps is very good.
vROps is user-friendly, but configuration is a little bit hard. It is also hard if you want to customize it for your data center, especially without VMware training. The user interface should be improved so that a new user can easily configure it for his own use.
I have been using VMware vRealize Operations for the last four years.
The stability is good enough to monitor private and hybrid clouds. Even though we are using very few of the features of vROps, it is very good. It is very useful for a cloud provider that is managing large-scale VMware technology for their cloud. It is good monitoring and operations software for them.
It is highly scalable.
We are already in the middle of a project to increase our infrastructure and we have included vROps in that project.
Customer support is good, but the main problem is that VMware support is very costly compared to other organizations' support. When you purchase a VMware product, such as vSphere or vROps, the license is perpetual, but you also have to purchase the support service for a number of years. The support service pricing is very high compared to the license, and compared to competitive vendors.
Before vROps, we were using SolarWinds NPM. The primary reason we switched was that we were looking for a solution that would give in-depth monitoring capabilities for VMware infrastructure.
The initial deployment of vROps was straightforward. We deployed ESXi, vCenter, and then vSAN. After that, we deployed vROps on-premises to monitor our VMware vSAN cluster. There was nothing special or complex about it.
It took four to five days to deploy vROps.
We have three people who are using and managing vROps and we are monitoring about 500 virtual machines with the solution.
We used a third-party integration partner that is certified by VMware. I felt that they were not well-trained on vROps.
The value we get from vROps is fine, but it would be better if the support cost were lower.
We did not look into other solutions because, at that time, we already had our VMware infrastructure. vROps is the best option for monitoring VMware infrastructure.
If your infrastructure is VMware-based, meaning you are using vSphere, vSAN, and vCenter, and if you are a large-scale cloud service provider, you should consider vROps as your monitoring and operations solution.
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.
The tool helped the organization in all monitoring tasks when being delivered as a service for customers helps them to generate early alarm templates, being a cloud service provider is delivered as part of the IaaS to generate memory consumptions processing and storage additionally can be configured parameters such as networking and services that are configured on virtual machines. The counter you have is the license that must be configured in order to have all the games you have, cloud computing.
The tool has many benefits in the monitoring and template functions to integrate with various virtual machine operating systems in the cloud service. Integrations with operating systems are intuitive and easy to install. The most important value is the value it delivers in a cloud service to generate early alerts in cloud services. In short, this is the most granular value that this service delivers to customers, in the administration part you have facilities for the ease of documentation on the web
The database services in the tool as backup services are friendly and can be deployed in the release to production. However, in the new features, I would like to include more online documentation that can help service generate early alerts. A service provider must be generated and coupled to new technologies, as a service provider we have advanced and generated as the advancement of technology, with the help of Nutanix we have learned to identify several tools and compare them. l can help service administrators generate early alerts, for a service provider should be generated and coupled to new technologies. As a service provider we have advanced and generated with the advancement of technology, with the help of Nutanix we have learned to identify several tools and compare
I have been using vROps for five years.
Technical support is excellent.
We did evaluate other solutions.