Callflow testing (CPF1)

Description

This probe checks the health of a specific callflow. It executes the callflow periodically in test mode and provides information about its good execution.

Release notes

Resource configuration interface

Resource configuration parameters

• Callflow number: Callflow number to be tested and to be monitored. To avoid some issue, the callflow number must be assigned once per probe. For example *001.

Configuration example

There are 3 steps to make this probe fully functionnal:

• Probe creation: The probe needs to be created in the SOP where the specific callflow should run.
• Callflow creation: The ProbePost action must be used inside this callflow. It will post all information provided to the monitor system.
• Callflow starting: The callflow must be started periodically by STARTRECURRENTAPPLICATION. This allows us to define an periodical interval to execute the callflow and provide some variables as profile parameters.

One of these variable can be used to determine if the callflow is run in test mode (where the ProbePost action should be executed) or if it is a normal execution (where ProbePost should not be called).

Performance graphs

This probe generates 3 different graphs (g1, g2, g3). Values are defined by the ProbePost action (3 different fields). These values are number provided in this action is used to perform the graph.

Alarms

Alarm level such that OK, WARNING, CRITICAL, UNKNOWN is performed by the ProbePost action.

Possible causes

(see the tested callflow)

Possible consequences

(see the tested callflow)

Possible actions

(none documented yet)