# 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.

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:

• 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.

## 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=
{
"ceventId":363,
"instance":"eyeShare1",
"tool":"eyeShare",
"status":"Complete",
"summary":"RC=0, NFS server restarted",
&request=mooletInforms
For Situations, you must specify "ceventType":"situation" in your template rule.