Skip to end of metadata
  • Created by Former user , last modified on 12.09.2013
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Unknown macro: {noprint}
Unknown macro: {float}

Contents

Change log:

Date:

Author:

Version:

Changes:

Completed

Ext.

Int.

Is in Core

Jira Ref.

Unknown macro: {page-info}
Unknown macro: {page-info}

0.1

Doc. created

No

 

x

N/A

N/A

Overview

Name of report

Wholesale Files Report (previously "Incoming Queue and Engine Processing")

Schedule

Every 2 hours

System

Retail/Wholesale; Prepaid/Postpaid

Customer role

Informed, Responsible

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.

CDRator Operations is involved only in case of a Managed Service Agreement with the customer.

Wholesale Files Report

At the moment the report is called Incoming Queue and Processed Records of Main Engines Report and looks like these:

And:

The report measures the incoming and outgoing work for the wholesale platform. Measuring the variation of the numbers over time (by checking different versions of this report) can help identify issues.

Field

Direction
(from the system's point of view)

Description

Handling

Minutes since last file loaded

incoming

How long in the past (in minutes) the last CDR file was loaded into the wholesale platform. If the system handles different types of CDR files, then these are displayed as separate lines.

The value should be always low. We expect to received CDR files continuously.

If the value grows then it could be that the loading functionality has problems or that the Rator system does not receive files from the network.

Number of Unrated CDRs

incoming

How many CDRs are not yet rated.

The value should be always low. We expect rating to work continuously.

If the value grows then it could be that the Rator system received a huge amount of CDRs or that there is a problem with the rating process.

Minutes since last export_file was created 

outgoing

How long in the past (in minutes) the last export file was generated; for each brand in the wholesale setup.

The value should always be low. We expect the system to rate and export these files continuously.

If the value grows then there could be problems with the processes that load and rate CDR files or with the export file generation itself.

  • No labels