![\"vra_cp\"](\"http:\/\/www.bussink.ch\/wp-content\/uploads\/\/2016\/05\/vra_cp.png\")
<\/a><\/p>\nWhen you install the vRA 7 Content Pack you can find the setup instruction in the tool tab. Here you will realize that you need to add two more Content Packs to be able to properly monitor a vRealize Automation installation.<\/p>\n
Lets add the Apache – CLF<\/strong> and the vRealize Orchestrator<\/strong> Content Packs in the vRLI marketplace.<\/p>\n <\/p>\n <\/p>\n <\/p>\n The vRealize Automation 7.0.1 Build 3622989 release now comes with a vRealize Log Insight Agent pre-installed. This agent is already running on the appliance when it is deployed, but it is not configured. You just need to connect using SSH to the vRA appliance and edit the \/etc\/liagent.ini<\/strong> configuration file.<\/p>\n edit the \/etc\/liagent.ini file<\/p><\/div>\n The three fields to edit are vRLI hostname, protocol (cfapi) and the port. Once this is done, you just need to restart the Log Insight Agent using service liagentd restart.<\/p>\n service liagentd restart<\/p><\/div>\n At this point the Log Insight Agent starts talking to your vRealize Log Insight host or cluster Virtual IP address.<\/p>\n When checking the vRealize Log Insight Administration<\/strong>\u00a0pane, in the Agents<\/strong> tab, I now see in my All Agents<\/strong>\u00a0the vRA Appliance communicating.<\/p>\n The Log Insight Agent is now communicating, but it does not yet have a configuration on what to send back.\u00a0Once an Agent pools the Log Insight server it will query what it needs to monitor. Here we will start to have fun and see the real power of vRealize Log Insight agent configuration.<\/p>\n We are going to use the appropriate vRA agent configuration template and make it an agent configuration that can be applied to our implementation.<\/p>\n Select the appropriate vRA agent group and Copy Template<\/p><\/div>\n From the Agent Drop-Down<\/strong> menu, scroll<\/strong> to the vRealize Automation 7 – Linux template and select on the right the Copy Template<\/strong> button. We will keep the configuration name as vRealize Automation 7 – Linux.<\/p>\n The next step is to select to which Log Insight Agents this configuration is applicable to. In the next screenshot I have selected to setup this Agent configuration using the IP Address of my vRA Appliance. I re-type the IP Address of the vRA Appliance in the filter, and use the Save New Group at the bottom.<\/p>\n Once save you can refresh<\/strong> the view and you will now see the configuration that is sent out to the qualified agent on their next regular pool of the vRLI host\/cluster.<\/p>\n Here is another view of the vRealize Automation 7 – Windows group, and you see that I have applied this configuration only to the windows servers of a vRA Enterprise deployment.<\/p>\n You can apply multiple Log Insight Agent configurations to the same server. Another vRA\u00a0example to monitor the IIS components of vRA IaaS elements<\/p>\n Example of monitoring Microsoft –\u00a0Active Directory 2012 servers<\/p>\n<\/a><\/p>\n<\/a> <\/a><\/p>\n<\/a><\/a><\/a><\/p>\n<\/a><\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n