Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Setting

Description

Value

Select an alarm value from the drop-down list.

Workflow

Click Browse... to enter the workflow(s) that you want to apply the alarm to.

Limits

Summation: Select this check box to add up the dispatchAlarmValue variable (countBillingFiles in the figure above, The Workflow Alarm Value configuration) whenever it is invoked. Alarm Detector compares this total value with the alarm limit (exceeds or falls below) and generates an alarm message accordingly.

Note: Selecting Summation means that the During Last entry refers to the time period during which a sum is added up. Once the set period has ended, that sum is compared with the limit value.

For All Workflows: Select this check box to add up the values (see Summation above) of all the workflows that the alarm supervises. Alarm Detector compares this total value with the alarm limit (exceeds or falls below) and generates an alarm message accordingly.

Note!

This check box can only be selected when Workflow is set to Any.

For further information about Limits see the section above, Host Statistic https://infozone.atlassian.net/wiki/spaces/UEPE4D/pages/107351066/Alarm+Detection+4.0#Host-Statistic-Value .

Workflow Execution Time

The Workflow Execution Time condition enables you to generate an alarm whenever the execution time of a particular, or all workflows, exceed or fall below the time limit that you specify.

...

Setting

Description

Workflow Group

Click Browse... to enter Enter the address of the workflow group to which you want to apply the alarm.

Info

Example - Configuring a Workflow Group Execution Time condition

Note
titleNote!

The parameters in the following example do not apply to any specific system and are only presented here to enhance understanding of the alarm condition.

You want the system to generate an alarm if a billing workflow group has been active longer than 3 hours.

  1. Configure an Alarm Detection that uses the Workflow Group Execution Time condition.

  2. On the Edit Alarm Condition dialog box click Browse... to , enter the workflow group you want the alarm detection to supervise.

  3. Enter a limit of Exceeds 3 hours.

The alarm will be triggered if the workflow group has been active longer than 3 hours.

...

Info

Example - Configuring a Workflow Throughput condition

Note
titleNote!

The parameters in the following example do not apply to any specific system and are only presented here to enhance understanding of the alarm condition.

You want the system to warn you on detection of decreased processing rate.

  1. Configure an Alarm Detection to use the workflow throughput condition

  2. On the Edit Alarm Condition dialog box click Browse... to , select the workflow with the processing rate that you want to supervise.

  3. Enter a limit of Falls Below 50000 (batches, UDRs, Bytearray).

The alarm will be triggered by every occurrence of a workflow slowing down its processing rate to a throughput that is lower than 50000 units per second.

...

Activation mode is independent of the rest of the profile configuration and you do not need to press Save after enabling or disabling the alarm detection.

...

On Desktop Client

On the Desktop Client, this toggle button is greyed out if there are no alarms present. You can see this button only after an alarm detection is saved.

The toggle button for the alarm detection is available on top of the alarm configuration details.

...

On Desktop Online

The alarm detection enable/disable toggle button in the Desktop Online will allow you to enable or disable individual alarms using the toggle button available next to the name of the alarm. You can also enable or disable all available alarms at one go using the Enable All or Disable All buttons.

...

Note

Note!

When importing an Alarm Detection configuration using system import or as part of workflow packages, the configuration is disabled.