Before you configure vRealize Log Insight to collect alarms, events, and tasks data from your vSphere environment, you must connect vRealize Log Insight to one or more vCenter Server systems.
About this task
vRealize Log Insight can collect two types of data from vCenter Server instances and the ESXi hosts that they manage.
Events, tasks, and alerts are structured data with specific meaning. If configured,vRealize Log Insight pulls events, tasks, and alerts from the registered vCenter Server instances.
Logs contain unstructured data that can be analyzed in vRealize Log Insight. ESXi hosts or vCenter Server Appliance instances can push their logs to vRealize Log Insight through syslog.
For the level of integration that you want to achieve, verify that you have user credentials with enough privileges to perform the necessary configuration on the vCenter Server system and its ESXi hosts.
Level of Integration
Events, tasks, and alarms collection
is a system-defined privilege. When you add a custom role and do not assign any privileges to it, the role is created as a Read Only role with three system-defined privileges: , , and .
Syslog configuration on ESXi hostsNote:
You must configure the permission on the top-level folder within the vCenter Server inventory, and verify that the Propagate to children check box is selected.
Verify that you know the IP address or domain name of the vCenter Server system.
Verify that you are logged in to the vRealize Log Insightportnumber Web user interface as a user with the Edit Admin permission. The URL format is https://log-insight-host, where log-insight-host is the IP address or host name of the vRealize Log Insight virtual appliance.
- Click the configuration drop-down menu icon and select Administration.
- Under Integration, click vSphere.
- Type the IP address and credentials for a vCenter Server, and click Test Connection.
It is recommended that you use service account credentials.
- (Optional) : To register another vCenter Server, click Add vCenter Server and repeat steps 3 through 5.
Do not register vCenter Server systems with duplicate names or IP addresses. vRealize Log Insight does not check for duplicate vCenter Server names. You must verify that the list of registered vCenter Server systems does not contain duplicate entries.
- Click Save.
What to do next
Start collecting events, tasks, and alarms data from the vCenter Server instance that you registered. See Configure vRealize Log Insight to Pull Events, Tasks, and Alarms from vCenter Server Instance.
Start collecting syslog feeds from the ESXi hosts that the vCenter Server manages. See Configure an ESXi Host to Forward Log Events to vRealize Log Insight.