Moogsoft Docs

Workflow Engine Tutorials

This topic collects the Moogsoft AIOps Workflow Engine tutorial videos to help you get started.

Introduction to Workflow Engine

Workflow Engine is a UI-based feature that handles custom logic for event, alert and Situation processing. The four engines - event, enricher, alert, and Situation - let you fine tune you data processing flow by checking conditions against object data, modifying project data, and controlling object routing. Building logic through the Workflow Engine enables you to customize and standardize incoming data to achieve accurate clustering and deduplication.

The following video introduces the Workflow Engine and logic implementation process:

Event workflows

Event workflows process event data after data ingestion from a LAM and before the Alert Builder. You can use an event workflow to normalize event data or drop unwanted events to prevent them from processing.

The following video introduces event workflows:

Alert workflows

Alert workflows escalate alerts. You can use an alert workflow to route a specific alert, such as a disk space alert, to a specific clustering algorithm.

The following video introduces alert workflows:

Heartbeat workflows

Heartbeat workflows detect the absence of events, such as a missing keep alive event, from a predictable source.

The following video introduces heartbeat workflows:

Situation workflows

Situation workflows integrate with ticketing or automation frameworks for remediation, enabling you to configure how and when the ticketing system creates tickets for Situations.

The following video introduces Situation workflows:

Stop workflows

The Stop Workflow Engine function prevents objects progressing through the workflow and subsequent data processing. The object only resumes processing if an update causes it to re-enter the workflow engine.

The following video introduces the Stop function: