After configuring log forwarding from Fleet Management to VCF Operations for Logs, the logs are not being transferred to VCF Operations for Logs.
VCF Operations Fleet Management 9.0.1.0
VCF Operations for Logs 9.0.1.0
The log forwarding functionality fails because the required Content pack is not installed, preventing the liagent from correctly processing and forwarding the system logs.
Ensure the Fleet Content Pack is installed on the VCF Operations for Logs server before proceeding with the following agent configuration steps:
1.Connect to the Fleet Management appliance via SSH as the root user.
2.Verify that the log forwarding configuration set in the GUI is correctly reflected in the following file:
/var/lib/loginsight-agent/liagent.ini
Example:
[server]
hostname = <FQDN_or_IP_of_VCF_Operations_for_Logs>
proto = syslog
port = 514
reconnect = 30
ssl = no
ssl_accept_any = yes
ssl_accept_any_trusted = yes
3.Create a backup of the liagent.ini file.
Example:
cp liagent.ini liagent.ini.bak
4.Edit the liagent.ini file as follows:
# Uncomment the appropriate section to collect system logs
# The recommended way is to enable the Linux content pack from VCF Operations for Logs server
[filelog|syslog] <-- Uncomment this line
directory=/var/log/* <-- Uncomment and append "/*" to the end
#include=messages;messages.?;syslog;syslog.?
5.Restart the liagentd service to apply the changes.
systemctl restart liagentd
After restarting, verify that the service status is Active.
systemctl status liagentd
6.Verify the log forwarding status within the VCF Operations for Logs interface to confirm logs are being received from Fleet Management.