Skip to main content

# eyeShare

You can use this integration to:

• Enable automation triggers for Ayehu eyeShare from Moogsoft Enterprise.

• Send alerts or Situations to eyeShare with a payload to initiate a request.

Payloads define the eyeShare tasks to carry out when an alert or Situation triggers, and the mapping rules which generate the request payload. You define these as name:rule pairs in the Workflow Payload Mapping Rules section. To find out your payload format requirements, contact your eyeShare administrator.

After you configure an automation integration, Moogsoft Enterprise automatically creates the 'eyeShare Alert' and 'eyeShare Situation' workflow engines. You must define separate workflows to forward alerts or Situations to these workflow engines and process them using the following functions:

See the eyeShare documentation for details on eyeShare components.

## Before You Begin

The eyeShare integration has been validated with the eyeShare eyeShareWebService_Generic endpoint. Before you start to set up your integration, ensure you know the following values:

• Username and Password to connect to your eyeShare instance.

• Hostname of your eyeShare instance.

• Endpoint URL for your eyeShare instance.

• Proxy Settings: Configuration required to access eyeShare.

## Configure the eyeShare Integration

To configure the integration:

1. Navigate to the Integrations tab.

2. Click Ayehu eyeShare in the Notification and Collaboration section.

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

4. Configure the eyeShare automations for alerts or Situations to initiate and identify the payload you need.

5. 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 the eyeShare Reference for descriptions of all properties.

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

## Configure eyeShare

You must add a Moolet Inform response to all eyeShare automation workflows, where results pass back to the Moogsoft Enterprise alert or Situation. The eyeShare automation must extract values for ceventType, ceventId, tool, and instance from the request. Either pass these values as part of the message or supply them in additional mapping rules. If you only have one eyeShare instance, you can hardcode tool and instance into the Moolet Inform response.

eyeShare sets the values for summary and resultsURL after the automation runs.

### Example

https://aiops_server/graze/v1/mooletInforms?target=EyeshareAutomationResponse&subject=responseFromAutomation&details=
{
"ceventType" :"alert",
"ceventId":363,
"instance":"eyeShare1",
"tool":"eyeShare",
"status":"Complete",
"summary":"RC=0, NFS server restarted",
"resultsURL":"https://<i>eyeShare-server-linkToResults</i>"
}
&request=mooletInforms

For Situations, you must specify "ceventType":"situation" in your template rule.

After you complete the configuration, you can make eyeShare automation requests in your workflows. See setAutomationPayload for more information.

Note that the eyeShare Alert workflow engine processes the output of 'Alert Workflows'. If you are using Cookbook or Tempus, you must configure these to process the output of eyeShare Alert workflows.

For Cookbook, in Settings > Cookbook, set Process Output Of to Other Moolet(s) and enter "eyeShare Alert Workflows", in addition to any other automation alert workflows you are using. See Configure a Cookbook for more information.

For Tempus, use the Graze API to change the value. See addTempus and updateTempus for more information.