How do I configure the Entuity integration with Moogsoft?

To configure the Entuity integration with Moogsoft

How Entuity incidents are mapped to Moogsoft

Entuity incidents can be pushed from Entuity to Moogsoft AIOps using the Moogsoft RESTful services.

To configure the Entuity integration with Moogsoft:

1. In Moogsoft:
   1. Navigate to Integrations > Install UI.
   2. Create a default Webhook LAM and set a name for the integration. This will establish the Moogsoft endpoint for Entuity to connect with, together with the user and password for the Moogsoft client that uses basic authentication. You do not need to make changes to the other editable dialogs.
      
      
2. In Entuity:
   1. Navigate to the ${ENTUITY_HOME}/etc directory.
   2. Create a file called Moogsoft.cfg.
   3. Add a named 'section' to the file that lists key-value pairs for port, host, path, user and password. These values will be available in the Integrations > Install UI for the Moogsoft Webhook LAM created in step 1 above:
      
      

      [default]
      port-443
      host=endpoint.moogsoft.io
      path=/events/webhook_ena
      user=Webhook
      pass=password

      
      Note, the section name 'default' will be used by the Entuity integration to identify the values for connecting to Moogsoft.
      
      Note, if the configuration file that specifies these connection properties is not named Moogsoft.cfg and/or is not located in the ${ENTUITY_HOME}/etc directory, then the actual location of the file will need to be defined in the Entuity startup_XX.cfg configuration file under the eventEngine section. You can do this by specifying the JVM property, 'moog.cfg', within the eventEngine start command:
      
      

      -Dmoog.cfg=${ENTUITY_HOME}${FPS}etc${FPS}YourMoogsoftConfig.cfg

3. In Entuity, you will then need to set up the Entuity Incident Trigger to forward Entuity incidents to Moogsoft:
   1. Click Main Menu and then Administration.
   2. Click Event Administration to open the Event Administration page.
   3. Under the Incidents tab, click Edit Global Triggers at the bottom of the browser.
   4. In the Edit Global Triggers window, click Add to open the Create Trigger window.
   5. Click Add to add an action. In the Type list, select the Named Action 'Send to Moogsoft', and give this Action a name.
   6. Ensure that the trigger is enabled (in the top right check box in the Create Trigger window) before clicking OK.
   7. Ensure that these changes to this event's project is saved and deployed.
   
   Note, to connect with Moogsoft using values that are specified in a section other than 'default' in Moogsoft.cfg, edit the Action created above and specify the desired value for the cname parameter in the Edit Action dialog.
   
   
4. In a multi-server configuration of Entuity, some information about the consolidation server must be available in the main section of the Entuity entuity.cfg file on all servers. This data will be included in the payload that is sent to Moogsoft for reverse communication:
   

   consolidation_server_name=servername
   consolidation_server_web_port=X
   consolidation_server_web_ssl=true or false

5. In Moogsoft:
   1. Set up the data to be used for Moogsoft deduplication by navigating to Integrations > Alert Noise Reduction UI.
   2. Edit the Signature Editor by removing the existing default entries and replacing them with the word 'signature' (with no quotation marks). The value of the signature field in the payload that is sent to Moogsoft will be used for their deduplication analysis.
   
   Note, this setting will be required until the proprietary Entuity LAM is available, at which point it will already be set as the default signature field.

How Entuity incidents are mapped to Moogsoft: 

The below tables describe how Entuity incidents are mapped to Moogsoft JSON fields: