The Supervision Service allows you to define actions based on specific conditions using decision tables. Depending on which conditions are met, the service can log messages in the System Log, apply an overload protection configuration, or generate an event. You can configure these conditions using any available MIMs in the workflow, such as throughput or queue size.

The Supervision Service is available for real-time workflows and can be configured in the Services tab in the Workflow Properties dialog. You can manually trigger the Supervision Service with action overload using mzcli commands for maintenance or other purposes. After manual activation, you must switch it back to automatic mode for the settings in the Services tab to retake effect.

Page navigation

Configuration of the Supervision Service

To open the configuration for the Supervision Service, open the Workflow Properties dialog in a real-time workflow configuration, click on the Services tab, click on the Add button, select the Supervision option and click OK.

WF_properties_Supervision_service.png

Setting

Description

Execution Interval (ms)

Enter the time interval, in milliseconds, with which current MIM values should be checked against the conditions in the decision tables. This configuration will be valid for all decision tables.

Decision Tables

A Decision Table holds the conditions you set and the actions that are meant to happen when those conditions are met. All the decision tables you configure will be listed in this section. Click Add to add a new decision table. We recommend configuring different decision tables for different purposes, for example, one for aggregation rules and one for data enrichment.

note

Note!
You can change the order of your decision tables, but this does not affect the functionality. All decision tables will be applied.

Note!
You can change the order of your decision tables, but this does not affect the functionality. All decision tables will be applied.

Creating a Decision Table

Click Add_button.png to add a new decision table, the Add Decision Tables dialog opens. This is where you configure a Decision Table. In a Decision Table, actions are triggered based on predefined conditions. Conditions and actions are configured separately. When you select to add a new decision table, the Add Decision Tables dialog opens.

Add_decision_tables.png

Setting

Description

Decision Table

Enter a name for your decision table in the Name field.

Table Parameters

Click the buttons Action Lists and Conditions Lists to configure the different conditions and actions for this table.

Decisions

Each configured condition list will be displayed in the Conditions column. Each of these conditions can be set to either True, False or -. If you want to add more columns to set up different combinations of conditions, you can right-click the Action column heading and select to add more columns. For each column with a condition combination, you can then select which action to take in the drop-down list containing all configured actions.

Configure Decision tables - high level steps

  1. Configure the conditions. The conditions you configure are based on different MIM parameters having defined values.
     

  2. Configure the actions. Depending on your workflow configuration you can select different options when configuring the actions. These options are:

    1. Generate a Supervision event to reject messages

    2. Log an entry in the System Log

    3. Add Overload Protection to reject messages (this option is only available if you have Radius or Diameter collection agents in your workflow).

note

Note!

If you are using Diameter or Radius Collection agents in your workflow, you can also select from a range of Diameter and Radius specific overload protection strategies in order to only reject specific types of messages. See Diameter Stack Agent Configuration(4.3) and Radius Server Agent with Supervision Service(4.3)for further information about these strategies.

Note!

If you are using Diameter or Radius Collection agents in your workflow, you can also select from a range of Diameter and Radius specific overload protection strategies in order to only reject specific types of messages. See Diameter Stack Agent Configuration(4.3) and Radius Server Agent with Supervision Service(4.3)for further information about these strategies.

  1. Set the newly created conditions to True , False or - (ignore), then select an action for each one.

note

Note!
When a condition is evaluated to true, the corresponding action will be performed only once, until any other condition is also evaluated to true. Generally, this means that a minimum of two conditions are required in the decision table.

Note!
When a condition is evaluated to true, the corresponding action will be performed only once, until any other condition is also evaluated to true. Generally, this means that a minimum of two conditions are required in the decision table.

  1. Set a name for the decision table if you haven’t already done so.
     

  2. Click Add. The decision table is added and you can repeat steps 1 to 4 to add additional tables.

multiple_decision_tables.png

Configure conditions

  1. From the Add Decision Tables dialog, click Condition Lists.

  2. You will come to the Condition Lists dialogue. Click Add to open the Add Condition List dialog.

  3. Click Add. You will come to the Add Condition dialogue.

Add_Conditions_process.png

  1. In the Add Condition dialogue:

Add Condition option

Description

Left Operand

Select the MIM Field that you want to add your condition to.

Operator list

This is the drop-down list located between the two operands. Select from:

  • > (greater than)

  • < (less than)

  • == (equals)

  • != (does not equal)

Right Operand

Select either the MIM Field against which the selected left operand will be compared, or add a constant value.

  1. Click Add to add the condition to the condition list.
     

  2. Repeat steps 4 to 5 until you have added all the conditions you want to have in the condition list and then click Close when you are finished.

    You will return to the Add Condition List dialog.

  3. Enter a name for the condition list in the Name field.

  4. In the Match field select if you want all the conditions in the list to be matched or, if only one condition is required to match by selecting either of the buttons Any of the Following or All of the Following.

add_condition_list_3.png

  1. Click Add to add the condition list in the Add Decision Tables dialog.

  2. Repeat steps 3 to 9 until you have created all the condition lists you want to have and then click Close when you are finished. You will return to the Add Decision Tables dialog.

Add_decision_tables_dialogue .png

Now that you are back in the Decision Table dialog you can create the actions for the condition lists.

Configure Actions

To configure actions:

  1. In the Add Decision Tables dialog, click the Action Lists button.

  2. Click the Add button to open the Add Actions dialog.

  3. Click the Add button to add actions.

Add_action_process.png

  1. In this dialog, select which type of action you want to use; System Log, Overload Protection, or Supervision Event. Depending on what you choose, the options in the dialog differ.

Add Action option

Description

 

 

Action

Select from the following:

  • System Log - add a notification to the system log.

  • Supervision Event - To generate an event that can be sent to various targets depending on how you configure your Event Notifications, seeSupervision Event(4.3).

  • Overload Protection - Add an overload protection service

note

Note!
You will only see the option for an Overload Protection If you have Diameter or Radius Collection agents in your workflow.

Note!
You will only see the option for an Overload Protection If you have Diameter or Radius Collection agents in your workflow.

Description

Enter a description for the action.

Reject

This option is only available when you have selected to configure an Overload Protection action and determines the percentage of requests that should be rejected; 0, 25, 50, or 100 %.

Strategy

This option is only available when you have selected to configure an Overload Protection action and determines if you want to apply this action on all types of requests or if you only want to apply them to the requests following a selected Diameter or Radius overload protection strategy.

Content

This option is only available when you have selected to configure a Supervision Event action and it determines the content of the event. See https://infozone.atlassian.net/wiki/x/KOMkEg for more information.

Severity

This option is only available when you have selected to configure a System Log action and it determines the severity of the log entry; Information, Warning, Error, or Disaster.

Message

This option is only available when you have selected to configure a System Log action and allows you to enter a message that will be visible in the System Log.

  1. Expand the sub-steps for the option you selected

  • Enter a description in the Description field.

  • Select the percentage of messages you want to reject; 0, 25, 50, or 100 % in the Reject drop-down list.

  • In the Strategy drop-down list, you select if you want the action to be applied for all requests, or only for requests following any of the Diameter overload protection strategies.

  • Enter a description in the Description field.

  • Enter the event content in the Content field. This content can then be used when configuring Event Notifications for this event.

  • Enter a description in the Description field.

  • Select severity in the Severity drop-down list.

  • Enter an optional message in the Message field.

  1. Click Add to add the action to the action list.
     

  2. Repeat steps 4 to 5 until you have added all the required actions to the action list and then click Close. You will return to the Add Action List dialogue.

Add_action_dialogue.png

  1. Add a name and click the Add button to add the action list in the Create Decision Tables dialog.

Setting

Description

List

Enter a name for the action list in the Name field.

Action

This section contains all the actions you have added to this list.

  1. Repeat steps 1 to 8 until you have created all the necessary action lists then click Close. You will return to the Create Decision Tables dialog.
     

Configuring a Decision Table

In the Decision Table tab you will now have two columns; Conditions and Actions.

Add_Decision_Tables_with_true-false_dropdown.png

The Conditions column lists all the condition sets you have created. In the Actions column, you can set each condition to True, False, or - (Ignore), and then choose which action to trigger when the decision table criteria are met.

If you have multiple conditions, various combinations may require different actions. To add another action column, right-click the Actions column heading and select Add Column.... You can repeat this process to define actions for all necessary condition combinations.

note

Note!
Only one action can be selected for each set of combinations.

Note!
Only one action can be selected for each set of combinations.

note

Note!
When a condition is evaluated to true, the corresponding action will be performed only once, until any other condition is also evaluated to true. Generally, this means that a minimum of two conditions are required in the decision table.

Note!
When a condition is evaluated to true, the corresponding action will be performed only once, until any other condition is also evaluated to true. Generally, this means that a minimum of two conditions are required in the decision table.

Example - Decision Table with conditions and actions configured on it

Add_decision_tables_example.png

The following actions will be taken during the following conditions:

Case 1 
If the Incoming messages exceed 50, a Supervision Event will be triggered.

Case 2 
If the Incoming messages exceed 100, 25 % of the incoming Diameter Credit-Control Initial requests will be rejected.

Case 3 
If the Incoming messages exceed 150, 100 % of the incoming Diameter Credit-Control Initial requests will be rejected.

mzcli Commands

If you need to manually trigger or clear the supervision service with action overload, e g for maintenance or other purposes, you can use the mzcli wfcommand. See the wfcommand (4.3) for more information.