Showing posts with label Monitor vROps. Show all posts
Showing posts with label Monitor vROps. Show all posts

Wednesday, April 29, 2015

Part 15: Re-initiate Monitoring Goals Wizard in vRealize Operations 6.0!

One of the post in my vROps 6.0 Tutorial was about understanding the Monitoring Goals in vROps 6.0. I would highly recommend that you read that post before you read this article as this one is a follow up on that post where at the end I mentioned :

"As I mentioned before, any changes to the policy now cannot be done through this wizard. You would have to manually edit the policy now to make changes or you could use my next post where I will tell you a hack which will allow you to re-run this wizard once again."
The above statement means that once you setup a vCenter Adapter to monitor a vCenter Server, you would be asked to define your monitoring goals. These monitoring goals basically translate into the default policy which are then applied on all the objects which are being monitored by that vROps instance. When you read the above mentioned article you would understand how this wizard helps you set the policy for the first time. Unfortunately, you can only run this widget once and set the default policy and to make any subsequent changes to the policy, you would have to manually edit the default policy which could be a cumbersome task if you are not well versed with how policy works!
While you do not have the option to re-run the wizard, there is a hack which was discovered when this question was asked by my colleague Woflgang Stichel who is a Business Solution Architect at VMware. His question was that one of his customer has not selected the right options while responding to the monitoring goals because of which vROps default policy is not monitoring the datastores at all. He wanted to re-run this wizard somehow to select the right options instead of diving into the policies.
Before I share the hack with you, I must mention that this is NOT a supported method and please do it at your own risk :-)

Wednesday, February 11, 2015

Part 11: Using vRealize Operations Manager to Monitor the Cluster Nodes

In the series on vRealize Operations, I wrote about the Architecture of vRealize Operations Manager which allows you to have Master and Replica nodes in a vROps Cluster. This not only allows you to distribute the adapters or solutions to more than one collectors present on each host, but also gives you resiliency in case the Master Node in the cluster fails.

With this post, I will actually share a failure which has been seen in my lab because of a couple of services failing on the master node. This resulted in a fail-over and the Replica switched over to become the Master Server. All this is possible because just like the previous releases, each and every service on your vROps nodes in being monitored by vROps itself.

Let me give you a brief description of my lab before I begin: