# Moogsoft Docs

## Configure the Sumo Logic LAM

Th e Sumo Logic LAM posts Sumo Logic alerts to Moogsoft AIOps as events.

You can install a basic Sumo Logic integration via the UI by supplying connection details and configuring a few parameters. See Sumo Logic for integration steps.

Configure the Sumo Logic LAM if you want to configure custom properties, set up high availability or configure advanced options that are not available in the UI integration.

# Before You Begin

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

• You have an active Sumo Logic account.
• You have the necessary permissions to configure a webhook connection and metric monitor in Sumo Logic.
• Sumo Logic can make requests to external endpoints over port 443.

If you are configuring a distributed deployment refer to High Availability first. You will need the details of the server configuration you are going to use for HA.

# Configure the LAM

Edit the configuration file to control the behavior of the Sumo Logic LAM. You can find the file at  \$MOOGSOFT_HOME/config/sumo_logic_lam.conf 

See the Sumo Logic LAM Reference for a full description of all properties. Some properties in the file are commented out by default. Uncomment properties to enable them .

1. Configure the connection properties for Sumo Logic:
• port : Port on which Moogsoft AIOps receives data from Sumo Logic.

2. Configure authentication:
• authentication_type : Type of authentication HTTP used by the LAM. Defaults to Basic.
• authentication_cache : Whether to cache the username and password for the current connection when the authentication type is Basic.

3. Configure the LAM behavior:
• rest_response_mode : When to send a REST response. See the Sumo Logic LAM Reference for the options.
• rpc_response_timeout : Number of seconds to wait for a REST response.
• event_ack_mode : When moogfarmd acknowledges events from the Sumo Logic LAM during the event processing pipeline.

• accept_all_json : Allows the LAM to read and process all forms of JSON.
• lists_contain_multiple_events : Whether Moogsoft AIOPs interprets a JSON list as multiple events.

4. Configure the SSL properties if you want to encrypt communications between the LAM and Sumo Logic:
• use_ssl : Whether to use SSL certification.
• path_to_ssl_files : Path to the directory that contains the SSL certificates.
• ssl_key_filename : The SSL server key file.
• ssl_cert_filename : The SSL root CA file.
• use_client_certificates : Whether to use SSL client certification.
• client_ca_filename : The SSL client CA file.
• auth_token or encrypted_auth_token : Authentication token in the request body.
• ssl_protocols : Sets the allowed SSL protocols.

5. Optionally configure the LAM identification and the log file details:

• name : Identifies the event sent to the message bus by the Sumo Logic LAM.
• log : Name and location of the Sumo Logic LAM log file.

6. Review the severity conversion rules. Sumo Logic only has three severity levels and does not have an equivalent for the 'Clear' severity. The default severity mapping in the Sumo Logic LAM configuration file is:

{
"severity":
{
"MissingData" : 2,
"Warning": 3,
"Critical": 5,
moog_lookup_default: 1
}
},

You can modify these mappings if required. See Severity Reference for details.

## Configure Sumo Logic

Refer to Sumo Logic and follow the instructions under Configure Sumo Logic .

## Example

The following example demonstrates an example Sumo Logic configuration.

monitor:
{
name					 	  : "SumoLogic Lam",
class                    	  : "CRestMonitor",
port                     	  : 48019,
use_ssl                  	  : false,
#path_to_ssl_files       	  : "config",
#ssl_key_filename        	  : "server.key",
#ssl_cert_filename       	  : "server.pem",
#use_client_certificates 	  : false,
#client_ca_filename      	  : "ca.crt",
#auth_token              	  : "my_secret",
#encrypted_auth_token    	  : "dfJtTQMGiFHfiq7sCmxguBt6Jv+eytkoiKCquSB/7iWxpgGsG2aez3z2j7SuBtKj",
#ssl_protocols				  : [ "TLSv1.2" ],
authentication_type			  : "basic",
authentication_cache		  : true,
accept_all_json          	  : true,
lists_contain_multiple_events : false,
rest_response_mode 	 		  : "on_receipt",
rpc_response_timeout		  : 20,
event_ack_mode 				  : "queued_for_processing"
}

# Configure for High Availability

Configure the Sumo Logic LAM for high availability if required. See Integrations HA Configuration for details.

# Configure LAMbot Filtering

The Sumo Logic LAMbot filters and processes Sumo Logic LAM events using the "SumoLogicLam.js" stream, then sends them to the message bus.

The LAMbot moves overflow properties to custom info and performs any filtering you configure in the LAMbot file. See Data Parsing for details.

If you don’t want to map overflow properties, you can comment out the presend property in the filter section to bypass the LAMbot and send events straight to the message bus. This speeds up processing if you have a high volume of incoming Sumo Logic alerts.

Alternatively , you can define a custom stream to receive Sumo Logic LAM events. See Alert Builder Moolet for details.

filter:
{
presend: "SumoLogicLam.js"
}

# Start and Stop the LAM

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

The LAM service name is  sumologiclamd  .

See Control Moogsoft AIOps Processes for the commands to start, stop and restart the LAM.

You can use a GET request to check the status of the Sumo Logic LAM. The request uses the authentication type and header authentication token defined in the Sumo Logic LAM configuration file . See Check the LAM Status in the REST LAM Configuration Guide for further information and examples.

# Configure Sumo Logic

After you have the Sumo Logic LAM running and listening for incoming requests, you can configure a webhook in Sumo Logic. See "Configure Sumo Logic" in Sumo Logic .