Workflow Engine

This feature is an Early Access Feature. An administrator can enable it at Settings > Labs > Configure > Early Access Features.

Implementers and administrators can use Workflow Engine to add custom logic for event, alert and Situation processing in Moogsoft AIOps.

Workflow Engine includes a few default workflows to help you get started:

"Closed Alerts Filter" prevents further processing of closed alerts.
"Closed Situation Filter" prevents further processing of closed Situations.
"Automated Ticketing" enables automatic ticketing using existing integrations with your incident management systems.

Other scenarios where you can implement the Workflow Engine include:

Controlling stateful workloads. For example, holding a "link down" event until Moogsoft AIOps receives a corresponding "link up" event within a time limit.
Integrating with automation frameworks for automated remediation of alerts such as if a disk space alert being received.
Extracting, transforming, and routing data for events, alerts, and Situations within Moogsoft AIOps.
Detecting the absence of events because of a missing keep alive event from a predictable source.

You can have multiple workflows running for different types of engines. The three available types of Workflow Engine are:

Each Workflow Engine is a Moolet that you can configure in the Moogsoft AIOps UI. By default Moogsoft AIOps has four workflow engines:

Name	Type	Position	Description
Event Workflows	Event	After the LAMs publish a message on the Message Bus.	Workflows for event message use cases.
Enrichment Workflows	Alert	After Alert Builder but before Maintenance Window Manager.	Workflows for alert enrichment or prior to maintenance use cases.
Alert Workflows	Alert	After Maintenance Window Manager.	Workflows for after alert maintenance.
Situation Workflows	Situation	After Situation Manager.	Workflows for Situation use cases.

In this section:

Search results