Page Comparison

{noprint}{float:right|width=300px|background=lightgrey|border=solid blue 2px|margin=10px|padding=8px}
*Contents*
{toc:all=true|depth=4|excerpt=true|indent=14px}
{float}{noprint}
*Change log:*
|| *Date:* || *Author:* || *Version:* || *Changes:* || Completed || *Ext.* || *Int.* || *Is in Core* || Jira Ref. ||
| {page-info:created-date|dateFormat=dd MMMM yyyy} | {page-info:created-user} | 0.1 | Doc. created | Yes/No | | x | N/A | N/A |




h1. Abstract

The System Status Report,
formerly
knownThe asSystem Basic SystemStatus 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 includes provisioning errors and WF activities waiting for user action.


* Issues to be handled by CDRator 
CDRator\- CDRator Operations will fix all errors in report which are not included in first section of the report.

{note:title=Exclusive Report}
This report is available only to customers with a Managed Service Agreement.
{note}

h1. Example


The top of the report:

!example-report-3.png|border=1!

{note}


Customers are 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.

{note}


CDRator Operations ensures the elements on the queues don't grow because of bugs with the system.

The second table thatcontains the elements handled by CDRator Operations handles:


!example-report-4.png|border=1!