Announcing Part 2 – #vROps Webinar series 2017 – “Full Stack” monitoring with vRealize Operations Manager
As promised, vROps Webinar Series 2017 is back with the second episode of the year. Last time around we looked closely into the features of vROps 6.5 and as stated during that webinar, we will now show you how you can unlock the full capabilities of vROps using the extensibility of the platform.
If you have been following the Webinar Series, by now you have a complete visibility into the capabilities of vROps, when it comes to monitoring the vSphere infrastructure. While this infrastructure is important for the IaaS provider, what business cares about is Applications. The good news is that vROps provides you an extensible platform which can be leveraged to extend the product capability into any area where metrics exist. This could be at the layers of your Software Defined Datacenter such as Compute, Network & Storage, or in the Application Stack and it’s tiers such as App, Web and DB.
While VMware provides a number of plugins which allow you to extend the platform capabilities into applications, they also leverage strategic partners such as Blue Medora to provide you with management packs which can go deep into applications to complete the “FULL STACK VISIBILITY” which is required in any IT shop.
#vROps 6.5 – Two new enhancements/features I really liked
There is a lot of great new enhancements and improvements added in 6.5 but for the sake of brevity I shall highlight two that I really liked.
Flexibility to increase RAM in between node sizes
So if you are familiar with vROps you will know that when you deploy it you have “T-Shirt” sizes to choose from, Small, Medium, Large and now Extra Large (6.5). However an additional extra in 6.5 is support to increase the memory allocation of your vROps nodes, you will not require additional CPU for the node until you hit the next node size bracket. If in doubt check the sizing guide spreadsheet VMware has provided so you can be sure on what you can and cannot do.
This flexibility plus the introduction of a new Extra Large Node size will give you more choice and flexibility with your existing or future vROps deployments.
Direct integration with Log Insight
There was already some integration with Log Insight via the launch in context menu, but now you can access Log Insight from the home page and also when you are troubleshoot individual objects. From a UX perspective this is fantastic and just saves time and further cements the relationship the two products have. You will still need to configure the Log Insight Management Pack and point it to the vLI instance you wish to integrate your vROps cluster with.
Getting started with vRealize Log Insight 4.3 for vRealize Automation 7
In this humble consultant’s opinion, Log Insight is one of the most useful tools in the administrator’s tool belt for troubleshooting vRealize Automation. I have lost count of the number of times I’ve been asked to help troubleshoot an issue that, when asked, people don’t know which log they should be looking at. The simple fact is that vRealize Automation has a lot of log files. Correlating these log sources to provide an overall picture is a painful, manual process – unless you have Log Insight!
Installing the Content Packs
In order to get the full picture of what’s going on during a vRA deployment you will likely need to correlate logs from vRA, vRO and NSX. Installing and configuring these is pretty easy.
I am going to assume the vSphere integration has already been configured, and all ESXi hosts are forwarding their logs to Log Insight already. (more…)
Log Insight services not starting after cluster IP changes
I ran into this problem at a customer site where all the Log Insight nodes were changed due to some IP address conflicts. I think the problem occurred because the IP addresses were all changed and the VMs shut down, without time for the application to update the node IPs.
- The web interface was down, a netstat -ano | grep -i “443” showed the service was listening
- service loginsight status|restart|stop|start hung and then timed out on the Master node
- The loginsight service was not running on the Worker nodes
- /var/log/loginsight/runtime.log contains warning messages about “Cassandra cluster not ready yet”
- Running /usr/lib/loginsight/application/lib/apache-cassandra-*/bin/nodetool status showed the two data nodes down (DN) and used the old IP address
Creating a vRealize Log Insight 2.5 cluster with Integrated Load Balancing
vRealize Log Insight 2.5 improves on the clustering in previous versions with an Integrated Load Balancer (ILB) which allows you to distribute load across your cluster of Log Insight instances without actually needing an external load balancer. The advantage of this over an external load balancer is that the source IP is maintained which allows for easier analysis.
The minimum number of nodes in a cluster is three, the first node becomes the Master node and the other two become Worker nodes. The maximum number of nodes supported is six, though acording to Mr Log Insight himself, Steve Flanders, the hard limit is more:
@sammcgeown yes though hard limit in product is much higher. How big do you need?
— Steve Flanders (@smflanders) February 11, 2015
The Log Insight appliance comes in four sizes: an Extra Small, for use in labs or PoC, through to Large, which can consume a whopping 112.5GB of logs per day. Those figures scale in a linear fashion for clusters, so a 3-node cluster of large instances can consume 337.5GB per day, from 2,250 syslog connections at a rate of 22,500 events a second. See more on sizing vRealize Log Insight.
Installing and Configuring vCenter Log Insight
With the release of vCenter Log Insight Public Beta (http://communities.vmware.com/community/vmtn/vcenter/vcenter-log-insight) I thought I’d strike while the iron is hot and run through the installation and configuration.
Deploying the OVF
This is such a bread and butter task that it doesn’t require more than a few words – it’s definitely worth looking at the Sizing PDF before you deploy (VMware-vCenter-Log-Insight-1.0-Beta-Virtual-Appliance-Sizing.pdf) as it’s not small even for a test installation. If you’re using less than the recommended 8GB RAM there are additional steps to change the heap size for performance. (more…)