Configuring the Log File Agent

Configure the Log File Agent to add the metadata and attributes such as type, site or module, which Log Analysis uses to map to the logical data source and Resource ID. The Resource ID is used to uniquely identify the physical data source.

Before you begin

You can install a new Log File Agent or you can integrate an existing Log File Agent. For more information about installing and configuring the Log File Agent, see Streaming data with the IBM Tivoli Monitoring Log File Agent.

Procedure

To add the required information to the configuration, edit the configuration or .conf file. The required parameters are:
```
LogSources=<log_path>
FileComparisonMode=CompareByAllMatches
ServerLocation=<haproxy_server_host>
ServerPort=<haproxy_port>
```
where <log_path> is the path to log files. <haproxy_server_host> and <haproxy_port> are the host name and proxy port used by HAProxy.

To populate the fields that are required for each event, update the format or .fmt file with the specific values that are required for your deployment. For example:

REGEX AllRecords
(.*)
hostname LABEL
-file FILENAME
RemoteHost DEFAULT
logpath PRINTF(%s,file)
type SystemOut
instance testInstance
cluster NONE
module WAS
env DEV
functional NONE
site PUNE
text $1
END

Restart the Log File Agent. For example, if you are using the internal Log File Agent, enter the following command:
```
<LFA_install_directory>/utilities/lfautil.sh
```

What to do next

To facilitate efficient processing, create LFA subnodes. For more information, see Configuring Log File Agent subnodes.