Workflow Monitor (3.0)

The Workflow Monitor controls workflow execution and presents a detailed view of the workflow execution status.

Agent states and events can be monitored during workflow execution and the monitor also allows for dynamic updates of the configuration for certain agents by sending commands. A command can, for example, tell an agent to flush or reset data in memory. For further information about applicable commands, see the section for the relevant agent. See also Dynamic Update in Administration and Management(3.0).


The Workflow Monitor can apply commands on only one workflow at a time, in one monitor window per workflow. The monitor functionality is not available for groups or the whole workflow configuration. The Workflow Monitor displays the active version of the workflow.

Monitoring a workflow does not imply exclusive rights to start or stop it, the workflow can be activated and deactivated by another user while monitored, or by scheduling.

Viewing Agent Events

While a workflow is running, agents report progress in terms of events. These events can be monitored in the event area at the bottom of the window. The following steps must be taken in order to view these events.

  1. To view events for all agents in the workflow, select Events for All Agents from the Event menu.

  2. To only view events for some selected agents, click each agent while holding down the <Ctrl> key on the keyboard.

    1. Select Events for Selected Agents from the Event menu.

    2. If required, rearrange the size and position of each column.

Agent Configuration

Some agents allow parts of them to be reconfigured while active. When double-clicking the agent in monitor mode, the agent's configuration is shown in the displayed dialog if the agent can be reconfigured. When the configuration has been updated it can be committed to the active workflow using the Dynamic Update button in the toolbar.


A workflow operates on a data stream and Usage Engine supplies a transaction model where persistent synchronization is made from the workflow data and agent-specific counters. In theory the synchronization could be performed continuously on a byte level, but in practice this would drastically decrease the performance of the system.

The transaction model is based on the premises that collection agents are free to initiate a transaction to the transaction server. At the moment the complete workflow is frozen and the transaction server saves the state of the workflow data that is queued for each agent. In practice, agents indirectly emit a transaction when an End Batch is propagated. When all data is secured, the workflow continues the execution.