Critical Processes Monitoring (Exclusive)

Change log:

Date:

Author:

Version:

Changes:

Completed

Ext.

Int.

Is in Core

Jira Ref.

13 June 2013

Luca Casarini

0.1

Doc. created

No

 

x

N/A

N/A

18 July 2013

Luca Casarini

0.2

Doc. completed

Yes

 

x

N/A

N/A

22 July 2013

SD

1.0

Checked

Yes

x

 

N/A

N/A


Contents:

Overview

Exclusive Report

This report is available only to customers with a Managed Services Agreement or Advisory Services Agreement.

Name of report

Critical Processes Monitoring Report

Schedule

Hourly

System

Retail/Wholesale; Prepaid/Postpaid

Customer role

Informed

CDRator Operations role

Informed, Responsible

CDRator role

Informed

Description of the roles:

  1. Escalate - the recipient escalates to the Informed role if the content of the report becomes a concern.
  2. Informed - the recipient gathers information by the content of the report. No reaction is expected.
  3. Responsible - the recipient is expected to read the content of the report (or a part of it) and to take the necessary actions.

Critical Processes Monitoring Report

This report gives an overview of the throughput of several critical functionalities of the system. The report is sent every hour and returns the number of records that are currently in the incoming working queue and those that were processed in the last hour by each functionality.

The processes that are part of this report may vary according to the system's configuration, but in general they are:

  • Workflow
  • Provisioning
  • Rating
  • Mail delivery
  • Recharge
  • Capture payments

As part of the Process Monitor functionality of the Rator solution, every process is monitored automatically and expected to complete its operations after every configured amount of time. If a process does not certify its completion within the configured time, an alert email claiming that the process is down is automatically sent out.

This report is used by CDRator Operations to interpret these alerts:

  • If the incoming queue is high the the process has a lot of work to do.
  • If there are handled records, then it is safe to assume the process is working correctly (e.g. Rating in the picture above).
  • If the incoming queue is constant or growing, there are no handled records, and this occurs in more than one report, then it is safe to assume there are problems with the process.