Failed to Load Vmware Vsphere Content Pack From Marketplace Please Try Again Later

vRLI 4.half dozen comes pre-installed with the capability to analyse core VMware products/components including vSphere, VSAN and vROPs.  Customers will crave the power to examine logs from other products that may or may not be VMware related and expect the same integrated feel when using filters, graphs and searching data.  To facilitate this, product content packs can be imported into the vRLI that provides the necessary rules, event types etc. that relate to the specific product the user wants to perform log assay on.

Installing a Content Pack

Content Packs are installed from the "Content Packs" bill of fare.

A content pack may either exist import directly if the administrator already has a copy or the marketplace tin exist used if the vRLI appliance has internet access to download them from the web.

In this example we are going to install the content pack for vRealize Suite Lifecycle Director 1.three.0 from the marketplace.

Once the content pack is installed it should testify upwardly in the content pack management screen.

If the pack needs to be un-installed, upgraded or you simply need to verify setup instructions then this can be done using the settings menu from inside the content pack.

Agent Configuration (Customer Side)

The configuration of the vRLI agent volition depend on what product/apparatus the agent is being used within.  Well-nigh VMware appliances volition come pre-installed with a vRLI agent but without any configuration.  Others (including servers) will likely need a vRLI amanuensis first installing and and then configuring.

In our example the agent is configured solely from within the vRSLCM GUI interface via a few fields nevertheless lets assume that nosotros have an amanuensis deployed into an appliance that doesn't take this option and it needs to be configured from the command line (equally per a Linux VM or not-VMware appliance).

The amanuensis configuration file (one time the agent is installed) is located in "/var/lib/loginsight-agent/liagent.ini".  Using Six (or any other text editor) the highlighted fields can be populated with the necessary values.  In this case we are using the CFAPI protocol rather than generic SYSLOG and nosotros are setting the log traffic to be sent over SSL.

The usual port numbers are:

CFAPI SSL = 9543
CFAPI (No SSL) = 9000
SYSLOG SSL = 6514
SYSLOG (No SSL) = 514

Note that the above port numbers tin alter depending on how the installer has configured the target server (CLI but).

Once the basic agent configuration has been done the agent should be restarted to re-read the configuration file that has simply been inverse.  The new agent should now testify within the "Agents" department of vRLI.

Agent Configuration (Server Side)

In one case the content pack is installed and our vRLI agent configured nosotros need to ascertain what information to send to vRLI and from which log files.  The content pack volition come with an agent template that specifies the log files, their locations and how they should be parsed by vRLI.  These can be constitute in the "Administration" page and so in the "Agents" department as shown below.

The "Copy Template" choice is used to take the template and create a new Agent Group from the template.  This means using the template for the agent configuration and defining i or more filters to select the agents that should have the configuration applied to.  In this case we are leaving the agent configuration as per the template and adding a filter for our vRSLCM appliance using its IP address.

Once the agent group is defined the configuration should be submitted to vRLI using the "Save Agent Group" button.

The agent grouping now shows upwardly at the top of the drop down listing every bit an agile group.

clarkmarming.blogspot.com

Source: https://vnuggets.com/2018/08/29/log-insight-analysis-for-additional-products/