Skip to main content

Ayehu

Note

Ayehu replaces the eyeShare integration.

You can install the Ayehu integration to enable triggering of automation in Ayehu from Moogsoft Onprem. The integration allows you to send alerts or Situations to Ayehu with a payload, governed by mapping rules, which will be interpreted and acted upon as required. Check with your Ayehu administrator for the payload expected in your environment.

AIOPS WORKFLOW PAYLOAD INSTANCES define the mapping rules used to generate the request payload. The rules are defined through the UI as name/rule pairs of the format shown below. When a new AIOPS WORKFLOW PAYLOAD is created, default rules are provided which can be changed or deleted, and new rules can be added to meet the requirements for the Ayehu request. See your Ayehu administrator for requirements.

MAP NAME example: defaultAlert

RULES: of the format shown below

NAME: AYEHU PAYLOAD FIELD: example: item.AlertId

RULE: STRING VALUE AND/OR EVENT REFERENCE example: $(alert_id)

The name can contain nested elements as shown, such as item.AlertId, item.Information, and other applicable elements.

The following workflow (WFE) actions are supplied for use with this integration

Automation responses can be processed by using a sendToWorkflow Graze call initiated from Ayehu (see below).

See the Ayehu documentation for more information on Ayehu.

Before You Begin

The Ayehu integration requires the Ayehu API endpoint as supplied by your Ayehu administrator (e.g. https://<mycompany>.ayehu.com/API/?Auth=AB12345).

Before you set up your integration, complete the following tasks:

  1. Obtain the username and password (if applicable) that will be used to connect to your Ayehu instances.

  2. Obtain the hostname for your Ayehu instances.

  3. Obtain the endpoint URL for Ayehu instances.

  4. Obtain any proxy settings required to allow connectivity between Moogsoft Onprem and the Ayehu instances.

Configure the Ayehu integration

To configure the integration:

  • Provide a unique integration name. You can use the default name or customize the name according to your needs.

  • Configure the Ayehu automations for alerts or Situations to initiate and identify the payload you need.

  • Define at least one instance. If you are running multiple instances of eyeShare automation, identify any differences between them so you can configure these in the integration.

See Configure Payload Mapping Rules and Macros Reference for more information on mapping rules and macros.

Configure Ayehu

A sendToWorfklow response needs to be added to all Ayehu automation workflows where results are passed back to the Moogsoft Onprem alert or Situation. The values for alert_id or sitn_id, target, and instance should be obtained from the request payload sent to Ayehu. The values for status, summary, and resultsURL are set by Ayehu after the automation runs.

Alert-based example:

https://aiops_server/graze/v1/sendToWorkflow with body of

{    
     "workflow_name" : "Ayehu Automation Response",    
     "engine_name" : "Alert Inform Engine",    
     "alert_id" : 70,    
     "workflow_name" : "Ayehu Automation Response",    
     "engine_name" : "Alert Inform Engine",    
     "alert_id" : 70,    
     "context" : {           
        "target" : "Ayehu",           
        "passedInstance" : "Ayehu1",                 
        "passedStatus" : "Complete",           
        "passedSummary" : "RC=0, NFS server restarted",           
        "passedResultsURL" : "https://ayehu-server-linkToResults"    
   }
}

Situation-based example

https://aiops_server/graze/v1/sendToWorkflow with body of

{    
     "workflow_name" : "Ayehu Automation Response",    
     "engine_name" : "Situation Inform Engine",    
     "sitn_id" : 70,    
     "workflow_name" : "Ayehu Automation Response",    
     "engine_name" : "Alert Inform Engine",    
     "alert_id" : 70,    
     "context" : {           
        "target" : "Ayehu",           
        "passedInstance" : "Ayehu1",                 
        "passedStatus" : "Complete",           
        "passedSummary" : "RC=0, NFS server restarted",           
        "passedResultsURL" : "https://ayehu-server-linkToResults"        
   }
}

Use Basic Auth for the above Graze requests using a predefined Graze user account. Configure the Content Type as application/json.

In this section: