# Moogsoft Docs

## Introduction

The Empty moolet enables Moogsoft AIOps integrators to intercept and handle MooMS events without impacting upon the existing AIOps Event flow logic and processing. This makes available a canvas upon which individual pieces of integration logic can be superimposed.

For example, to integrate with an incident management system, such as ACMEIncidentManager, the Empty Moolet must:

• Listen to  NewThreadEntry  Events (topic on MooMS is  /sig/thread/entry/new  ) and  SigStatus  Events (topic on MooMS is  /sigs/status topic  ). Other handlers will follow in due course
• Interrogate the Events to select only those in which the incident management system has registered an interest via the Graze API  addSigCorrelationInfo  request
• Filter out those Events which were originated by the incident management system via the Graze API to avoid sending duplicate information
• Extract relevant information from the Event including the incident management system entity reference
• Send the information to the incident management system via the REST.V2 MooBot module which supports the sending of simple RESTful POST requests using basic HTTP authentication

The above example is only one way of integrating AIOps with other systems. Each integration will be dependent upon the individual use cases and systems being integrated.

The Empty Moolet can also be used in general augmentation of Alert and Situation details.

## Configuration

The Empty Moolet is simply designed to take messages off the MooMS bus according to message type and pass them to a Moolet. The configuration is correspondingly very simple and includes the message types (type maps to a unique MooMS topic) to register interest for and the name of the Moolet to pass them to. For example, if you were integrating with the ACME system, which is an incident management system, you may have configuration as follows:

name : "ACMEIncidentManager",
classname : "CEmptyMoolet",
run_on_startup : true,
moobot : "ACMEIntegration.js",
event_handlers : [
]