# ignio

You can use this integration to:

• Enable automation triggers for ignio from Moogsoft Enterprise.

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

Payloads define the ignio 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. The name can contain nested elements. For example, externalRecords.externalId.

The element name externalRecords is a special path you can use to build a separate array within the request payload. Some implementations of the ignio eBonding endpoint require this format:

"body":
{
"externalRecords": [{ "externalId": "alert-480", "properties": { "dv_priority": "5" }}],
"toolName": "ExampleWI"
}

After you configure an automation integration, Moogsoft Enterprise automatically creates the 'ignio Alert' and 'ignio 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 ignio documentation for details on ignio components.

## Before You Begin

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

• Authtokens for your ignio instance.

• Endpoint URL for your ignio instance.

• Hostname of your ignio instance.

• Proxy Settings: Configuration required to access ignio.

## Configure the ignio Integration

To configure the integration:

1. Navigate to the Integrations tab.

2. Click ignio 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 ignio 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 ignio automation, identify any differences between them so you can configure these in the integration.

See the ignio Reference for descriptions of all properties.

## Configure ignio

You must add a Moolet Inform response to all ignio automation workflows, where results pass back to the Moogsoft Enterprise alert or Situation. The ignio 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 ignio instance, you can hardcode tool and instance into the Moolet Inform response.

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

### Example

https://aiops_server/graze/v1/mooletInforms?target=IgnioAutomationResponse&subject=responseFromAutomation&details=
{
"ceventId":363,
"instance":"ignio1",
"tool":"ignio",
"status":"Complete",
"summary":"RC=0, NFS server restarted",

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