The Log Insight Linux Agent collects events from log files on Linux machines and forwards them to the vRealize Log Insight server.

In a Linux system, applications can store log data in flat text files on the file system. The Log Insight Linux Agent can monitor directories and collect events from flat text log files.

The Log Insight Linux Agent runs as a daemon and starts immediately after installation. After installation, you can configure the following options:

  • Select the target vRealize Log Insight server to which the Log Insight Linux Agent forwards events.

  • Configure which directories the Log Insight Linux Agent monitors.

The Log Insight Linux Agent supports the following distributions and versions.

  • RHEL 5, RHEL 6, and RHEL 7

  • SLES 11 SP3 and SLES 12 SP1

  • Ubuntu 12.04 LTS, 14.04 LTS, and 16.04 LTS

The Log Insight Linux Agent writes its own operation log files to /var/log/loginsight-agent/liagent_*.log. Log files are rotated when the Log Insight Linux Agent is restarted and when they reach a size of 10 MB. A combined limit of 50 MB are kept in rotation.

To download the Log Insight Linux Agent package, navigate to the Administration page of the vRealize Log Insight Web user interface, click Agents in the Management section, and click the appropriate package link.

If you implement a default installation of the Log Insight Linux Agent for a user without root privileges to use, the default configuration might create problems with the data collection. The agent does not log a warning that the subscription to the channel is unsuccessful. and files in the collection do not have read permissions. The message Inaccessible log file ... will try later is repeatedly added to the log. You can comment out the default configuration that is causing the problem or change the user permissions.

If you use an rpm or DEB package to install Linux agents, the init.d script named liagentd is installed as part of the package installation. The bin package adds the script, but does not register it. You can register the script manually.

You can verify that the installation was successful by running the (/sbin/)service liagentd status command.