If you were talking to someone whose organization is considering VMware vRealize Operations (vROps), what would you say?
How would you rate it and why? Any other tips or advice?
VMware vRealize Operations (vROps) is a good tool that users can use for reporting purposes, forecasting, performance analysis, and in-depth troubleshooting. It is very useful. I rate VMware vRealize Operations (vROps) an eight out of ten.
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.
My advice is to take a good look at vROps. When you have a big infrastructure with a large volume of instances, monitoring everything in a single dashboard is very difficult, but with this solution, it's pretty easy. It's like a Swiss Army knife. You can troubleshoot and monitor in a single place. It's pretty convenient. Overall, this is a very good product. We are using lots of VMware technologies, including Log Insights, VMware ESXi, vCenter, and NSX. There were a lot of improvements with version 8. They integrated AWS, Azure, and Google Cloud. It is improving day by day. If some of your instances are situated in AWS and some are on Azure, and you have to monitor all the systems in a single place, that's where they're improving on things. Now, they are providing the cloud-provider stuff. We are planning to deploy Kubernetes in our data centers, because Kubernetes is a very new technology, but in our country it is not that popular yet. We will look at integrating that kind of offering later. Previously we integrated this solution with vRealize Log Insight as a trial. But later on, we stopped using vRealize Log Insight because we were using Splunk for analytics. vRealize Log Insight is a different product. When you have a lot of stuff in your data center and you need to archive and manipulate things, you need to use different tools. vRealize Log Insight is not useful for our use case.
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.
It is useful for determining whether to make decisions. Also, for our troubleshooting issues, it is the most powerful option in the market. vROps provides a good native solution if you are using multiple VMware tools. The design and what you sell to customers will impact your infrastructure. There is a new version, but I haven't used it yet. I would rate this solution as an eight out of 10.
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.
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.
My advice is to test the product. I am monitoring VxRail from vROps. Our average time for resolution depends on the issue. For example, if I receive a notification, and there is a large latency or the hard disk is filling up too fast, it will depend on the end administrator who is monitoring it. I rate VMware vROps vRealize Operations an eight out of 10.
My advice for anybody who is implementing this product is to size the environment very well. This is the first analysis that we do; we look at how big the environment is that we want to monitor and how many objects will be there, and compare this to the VMware sizing guide. You really have to analyze that and size your environment well because if it is done properly then it will give you a lot of value in monitoring. Overall, this is a good monitoring tool and I think it's the best one for me. That said, there is always room for improvement. I would rate this solution a nine out of ten.
My advice for anybody who is implementing vROps is to first learn how to troubleshoot. If any issue should arise, the first point of contact is L1 and L2. From there, instead of going to vCenter and checking the logs, use vROps. It will allow you to easily find problems and monitor them. As we are technical people, we need to develop a solution as soon as possible, instead of delaying. My preference is to log in to vROps and monitor everything. Once we locate exactly where the problem is, we can give a solution for it. Only if we do not find the cause here then we go to the logs. I would rate this solution an eight out of ten.
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 provides proactive monitoring, but it is not a real-time monitoring. It is polling every five minutes. If there is an issue in the first minute, but polling happens at the fifth minute, there is a gap of four minutes. It will capture that failure and alert in the fifth minute. It is more reactive monitoring, in that sense. But at least we know there is an issue. Overall, vROps is maturing, year by year. New versions have a lot of scope. We are not fully utilizing it, but if you understand the product features correctly, it will save you a lot of cost and reduce manual efforts. I would recommend it. If someone is looking for virtual monitoring, vROps is the best solution.
My advice would be to look at it holistically, meaning look at what you want to achieve in the final endgame. Also, evaluate a couple of products to get a feel for them and which product suits you. In addition, create roles within your company, because this needs dedicated attention when you implement it and attention to sustain it. There should also be alignment with an application team or leadership team when implementing this kind of solution.
In the future I'd like to use the plug-in and the APM. In the future, using the APM, things will be better. Nowadays, applications have under-utilization of hardware. I'm happy with the solution. There are many options for using it because of the features vROps has.
I rate VMware vRealize Operations very highly because it gives you multiple features such as compliance, agility, and staying hybrid, although if you want you can do it on-prem or on the cloud. I would recommend it regardless of the deployment, whether it's on-prem or AWS or hybrid. It is user-friendly, but it definitely requires a little tweaking in the environment when you're doing the installation to set it per your requirements, your infrastructure, and per your expectations. What are you trying to monitor? Once you're done with setting up vROps for your cluster or nodes, then it's very easy to use. It will really help you out to get to the stage of automation for your infrastructure, so you don't need to depend on manual processes at all. We are not using Kubernetes or Tanzu as of now, but we are planning to incorporate it down the line, maybe in three to six months. Overall, I would rate vROps as a nine out of 10. The one point I'm leaving out is because there is room for improvement, as I mentioned earlier.
When we speak to clients about it they often say, "I'll think about it." I think the best thing for them to do would be to actually use it, with the 60-day trial. They should play around with the tool and then come back and say, "This is what I can do in the product." That way, they would see what the product is about. I'd rather they experience something than somebody else telling them about it. Clients have access to VMware. They can download the solution from wherever they are and then start playing with it. They need to see what it can do and realize, "Wow, what an amazing tool." They need to see the benefits of the tool. It's the best monitoring tool. It is expensive, but expensive is relative. It's a matter of the client having a play with the tool and realizing what an amazing tool we have. My clients are quite small so when they do use it, it's when I'm with them. They don't understand what the product does. For me it's a big thing, but for them, it's neither here nor there. They say, "We'll deal with it when we can. We'll look into it whenever we've got the time." It's never the situation where I've come back and my client is saying "Wow, that is brilliant!" They say it's brilliant when I do it but they don't go back and start utilizing the tool. So I don't really always get the feedback that I desire. One of my colleagues is busy with a deployment at one of our clients and he's also doing the Blue Medora integration. I talk to him on a daily basis just to get an update, and he's amazed at what vRealize can do. From that perspective I think that we're quite happy with the product.
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 don't use VMware's Tanzu solution along with this solution for Kubernetes monitoring and management, but we have had discussions with the VMware team about it. It is still in discussion. Leaving the issue of cost aside, I would rate vROps at eight out of 10, in terms of the technical side, integration, and support.
We are still running vROps in parallel with some products that we are currently using. However, I am seeing the opportunity for it to take over from our other tools in the future. From what I have read, it is a great tool that you can use across multiple clouds. We are planning on implementing VMware's Tanzu solution along with vROps for Kubernetes monitoring/management in Q1 2020. I am currently familiarizing myself with it because I know it's something that I will be deploying pretty soon. I would rate this solution as a nine out of 10.
I recommend implementing vROps by first setting up a pilot environment. You need to become a master in vROps to make the best use of its features. If you don't have any experience with a lot of the features provided by vROps, you can't easily use them, and you can't understand the difference between vROps and SolarWinds and other products. So I would recommend studying it in detail. After that, you can make use of it, because vROps is a bit complex.
* Conduct workshops and capture monitoring requirements at a high level; document and understand the customer's requirements. * Study the customer’s infrastructure, as it will be useful during the implementation stage. * Align the customer's requirements, so that all the required systems are monitored in the vROps platform. * Work out the network firewall rules that are required to configure vROps. * Use the vROps sizing guidelines and sizing guide spreadsheet prior to vROps deployment. * Deploy the remote collectors for bigger environments as it puts less load on the analytics cluster. * Post deployment of vROps, you should create a full-stack relationship dashboard, as it helps to identify issues at various tiers in a typical 3-2-1 type environment. * Make use of role-based user account management. * Avoid taking snapshots or backups of vROps nodes during DT window.
Which is better and why?