Version

Argent Omega 2.2A-2410-B and later

Date

Tuesday, 19 November 2024

Summary

The unique workflows in Argent Omega have been enhanced with a new option: ‘Run Workflow For Selected Nodes In Parallel’

Technical Background

A Workflow is essentially a multi-step job — with dependencies — as in a classic Job Scheduler

Another way to view a Workflow is as a super-Relator

A Workflow can execute Rule and Alert against licensed CMDB-X object on schedule just like Relator. Instead of just a few simple combinations of Rule and nodes in Monitoring Group, industrial-strength flow logic is used to control the order of execution, and when individual steps are executed or skipped.

The logic is defined as Steps in the Workflow.

Suppose, on a dozen Windows machines, the following needs to be performed on each machine:

1. Stop a set of services
2. Reboot machine
3. Start a set of services

Each task is defined as a Step in Workflow.

In Argent Omega 2.2A-2410-A and below, each Step must be associated with a Monitoring Group that defines the servers.

The issue with this approach is that if any bad machine is present in the Monitoring Group, the workflow could stop for all nodes in the Monitoring Group.

To remove this limitation, Argent Omega has been enhanced with the ‘Run Workflow for Selected Nodes in Parallel’ option. This allows all Workflow Steps to be executed across all selected nodes, even if one or more problematic nodes are present in the list.

There are options to select Servers or Devices from a list or from Monitoring Groups in which the servers are defined:

Resolution

Upgrade to Argent Omega 2.2A-2410-B or later