Skip to main content


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:

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

To find out your payload format requirements, contact your ignio administrator.

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:

  • Request payload of your ignio implementation.

  • Username and Password to connect to your ignio instance.

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

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

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.


    "ceventType" :"alert",
    "summary":"RC=0, NFS server restarted",

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

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

Note that the ignio 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 ignio Alert workflows.

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

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