vRealize Operations and vRealize Log Insight Integrated

This two products work brillantly together but there are few things we need to get full integration between working as you would expect.

There are a number of steps required.(this is based on at least LogIsnight 3.3.2 and vRops 6.2)

Log Insight Alerting and InContext Launching

If you are running vRops 6.2 or older then you need to first install the Log Insight Management Pack for vRops, this can be downloaded from Solution  Exchange. If you have installed vRops 6.3 then the latest Log Insight Management Pack is already installed for you. But you still need to create the Admin user in vRops

Download the PAK file and save to a location where it can be uploaded to the vRops cluster.

In vRops, log into the main GUI as an admin user, then browse to Administration>Solutions, then choose the small green cross to add a solution

LI Solution

Then follow the wizard to upload the pak to vRops

LI Solution 2

Once completed, the Management Pack will be shown in the Solutions GUI, there is no configuration from the vRops side required

LI Mgmt Pack Installed

Before continuing ensure you have created either an Active Directory Service Account or Local User with full admin rights in vRops, re this post for more details

Now that all vRops side of things has been configured.

Go to Log Insight and log in as an admin user. Then under Administration (three small lines top right corner), go to vRealize Operations in the right hand column. Then add in the details of the vRops Master node, and the user details created for this access, in my case I have a local user in vRops called Log Insight.
LI User in LI

Save the settings and it will go through a few minutes of configuring the integration into vRops, and it will return a success message.

Launch in Context

LI Saved

Test integration by browsing to a relevant object in vRops and ensure the “Search for logs in vRops in vRealize Log Insight” is shown and will launch an instance of LI when clicked on.vRops to LI Link

 

vRops Syslogging into Log Insight

This is the second step required now to send syslog from vRops to Log Insight. Thankful this can be easily achieved from LogInsight without digging into the vRops config.  This is helped by the fact vRops already has installed the Log Insight agent.

First step is to install the vRops Log Insight Content pack which will provide vRops dashboards and standard agent configuration files. So if your Log Insight cluster can connect to the internet, open up the Content Pack menu under the three small lines in the top right corner, under Market Place find the vRops content pack and go through the steps to simply install this.

If you don’t have install access, the content pack can be downloaded from Solution Exchange, as a vlcp file. Once download in LI, open up the Content Pack menu and choose Import Content Pack in the bottom right corner and browser to find the VLCP file downloaded from Solution exchange, then follow through the wizard to install.(note it is already installed in this environment which is why it shows in the right hand menu.

LI Content Pack

You will now see the VMware – vRops 6.x under installed content packs, and if you go dashboards then it will show under the list of available dashboard groups

Dashboard List

The final step is set up Syslogging from the hosts to your LogInsight environment. Go to Administration > Agents. With the Content Pack came a template for the LI Agent on vRops. Pull down the All Agents list and there is a vRops 6.x -Sample, if you hover over the right hand side you will see Copy Template choose this to create a new Template for your node (you will need one of these per node you have deployed of vRops)

Screen Shot 2016-08-31 at 09.12.23

So create a new Agent group and give it a useful name, in this case will be for vRops 6.3 – Master for the Master node.

Create Agent Group

You are then given the Agent Configuration Gui with 3.3.2 and above the Agent Configuration Builder is new in 3.3.2 and if you don’t see it as below you need to enable it as an experimental feature in 3.3.2(in 3.3.6 it is part of the standard build)

Agent Configuration Edit Agent Configuration Build

The template contains sections for each log and values need to be updated to reflect your environment

Agent Configuration Options

vmw_vr_ops_appname – do not change

vmw_vr_ops_logtype – do not change

vmw_vr_ops_clustername – normally the cluster VIP name

vmw_vr_ops_clusterrole – can be Master, Replica, Data, or RemoteCollector, see (Administrator>Cluster Management), in this case it is MastervRops cluster role for LI Agent

vmw_vr_ops_nodename -taken from vrops cluster management (Administrator>Cluster Management)vRops node name for LI Agent

vmw_vr_ops_hostname – taken from vrops cluster management (Administrator>Cluster Management)

vRops node ip for LI Agent

So that the agent build reflects the following;

Agent Configuration FinalThese settings now need to be set on all File Logs. (It can be quicker to go into to the Edit mode, copy the content to notepad and do a find/replace and then copy it back to the Edit mode screen!).

Then if you have to apply the Agent configuration to the node, set the filter to apply the agent to node either by IP or Hostname

Assign Agent to Node

Then at the bottom of the Agent Configuration, choose Save Agent group.

Setup up LI Agent if it is not talking to vRops

It maybe that LI Agent is not talking to vRops, so you may need to initially update the LI Agent on the vRops Server. Connect via the console to vRops and log in with root (if you have never done this before the password is blank and it will prompt for a reset). Then browse to to/var/lib/loginsight-agent/use VI to edit the liagnet.ini file to amend the hostname, proto, port and ssl options to allow communication to talk to the Log Insight cluster.

Liagnetini

Then save and restart the agent,

#/etc/init.d/liagentd restart

What if you have multiple vRops Nodes.

If you have multiple nodes at this time you need to create an Agent group for each node due to an issue with the file log names need to be unique. So you would copy the vRops 6.x Template to create a new agent group i.e. it might be called then vRops 6.3 – Replica

vrops li replica

of course you need to update the file log sections as previous, but in this case the

vmw_vr_ops_clusterrole – would be replica

vmw_vr_ops_nodename -would be the name of the replica taken from cluster management

vmw_vr_ops_hostname – taken from vrops cluster management (Administrator>Cluster Management)

But in the Agent Configuration Editor, you need to access the Edit mode and at the [filelog|******] filed it needs to be editted to make it unique on each section i.e

[filelog|ANALYTICS-analytics]

becomes

[filelog|ANALYTICS-analytics -REPLICA]

LI Agent Replica edit

Leave a Reply

Your email address will not be published. Required fields are marked *