# Moogsoft Docs

## Configure the Logfile LAM

The Logfile LAM allows you to parse data in log files and send it to Moogsoft AIOps as events.

There is no UI integration for the Logfile LAM. Follow these instructions to configure the LAM.

# Before You Begin

Before you configure the Logfile LAM, ensure you have met the following requirements:

• You know the location of the log files you want to parse.
• You know the format of the log file names.
• The log files are accessible from Moogsoft AIOps.

If you are configuring the Logfile LAM for high availability, refer to High Availability first. You will need the details of the server configuration you are going to use for HA.

},

# Configure for High Availability

Configure the Logfile LAM for high availability if required. See LAMs and High Availability for details.

# Configure Parsing and Mapping

You configure parsing to break the log file up into tokens that Moogsoft AIOps uses to assemble events. You can also map parsed parameters to alert fields.

See Data Parsing for further information and examples.

# Configure the LAMbot

The Logfile LAMbot processes and filters events before sending them to the Message Bus. You can customize or bypass this processing if required. You can also load JavaScript files into the LAMbot and execute them.

See LAMbot Configuration for more information. An example Logfile LAM filter configuration is shown below.

filter:
{
presend: "LogfileLam.js"
}

# Start and Stop the LAM

Restart the Logfile LAM to activate any changes you make to the configuration file or LAMbot.

The LAM service name is  logfilelamd  .

See Control Moogsoft AIOps Processes for further details.