Change log:
Date: | Author: | Version: | Changes: | Completed | Ext. | Int. | Is in Core | Jira Ref. |
|---|---|---|---|---|---|---|---|---|
25 februar 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 | System Status Report |
Schedule | Daily |
System | Retail/Wholesale; Prepaid/Postpaid |
Customer role | Informed, Responsible |
CDRator Operations role | Informed, Responsible |
CDRator role | Informed |
Description of the roles:
- Escalate - the recipient escalates to the Informed role if the content of the report becomes a concern.
- Informed - the recipient gathers information by the content of the report. No reaction is expected.
- Responsible - the recipient is expected to read the content of the report (or a part of it) and to take the necessary actions.
System Status Report
The System Status Report returns the status of several queues of the system and represents an overall system health check.
There are (usually) two sections of the report:
- Issues to be handled by customer - This section normally includes provisioning errors and workflow activities waiting for user action. Depending on the system configuration and different agreements with the customer, other queues could be added to the list.
- Issues to be handled by CDRator - This section includes activities which are responsibility of CDRator Operations.
Queues and Fields
The report groups the queues as follows (depending on the system configuration, one or more of the points below could be missing):
- Workflows waiting for user action
- Provisioning errors
- Workflow activities in error
- Rate errors
- Alert pending in error
- Subscription fees in error
- Process monitor alerts
The total number of elements belonging to a group is reported in the header.
Every element of the queue has these fields:
- Activity - an extended description of the field.
- Total - the number of occurrences of that activity.
- Newest - the most recent date and time that activity occurred. This column may be called Latest in some reports.
- Oldest - the oldest date and time the activity occurred.
Newest and Oldest follow a conditional formatting scheme:
- Red and bold - if the timestamp is within the day the report is generated.
- Orange - if the timestamp is older than 1 to 10 days before the date of report generation.
- Black - if the timestamp is older than 10 days before the date of report generation.
Brand
If relevant, the Brand is part of the report:
Activities Handled by Customer
The customer is expected to check this part of the report on a daily basis and to perform the necessary actions to reduce the amount of the queues.
The first part of the report contains the activities that must be handled by the customer:
CDRator Operations ensure that the elements on the queues do not grow because of bugs in the system.
Activities Handled by CDRator Operations
The second table contains the elements handled by CDRator Operations:
CDRator Operations independently react and handle the activities in this section.