cancel
Showing results for 
Search instead for 
Did you mean: 

Reports from online Reports central are not showing data - what might be wrong?

Moderator

Reports from online Reports central are not showing data - what might be wrong?

Reports from online Reports central are not showing data - what might be wrong?

 

1 REPLY 1
Moderator

Re: Reports from online Reports central are not showing data - what might be wrong?

Reports from online Reports central are not showing data - what might be wrong?

Reports that can be viewed via the Client and Web UI are all based on database replays. A set of packaged databases such as the Capacity Planning or Cluster Database will collect historical data and the report is effectively a database replay for a specific time period.
If a report is not working, you should;

• Check the source database used for the report.
• Confirm that the database exists and data has been collected. You can right click on the database under the
node navigation tree in the GUI and select Replay->Quick view.
• Check the period for the report. Confirm that data in the database covers the required period. In most cases,
customers will try to generate a report for last week or this month and there will not be source data if the
system has just been installed.

The packaged Cluster Database is configured to wrap on attaining a size of 300Mb or two weeks in duration. If the cluster is a larger cluster comprising five or more nodes, it may be necessary to increase the wrapping size as the
additional nodes will increase the amount of data being collected.

The Cluster Capacity Planning database is actually a database summary. Therefore, a database process will not run
constantly to collect the data. Rather a summary database process is executed each night by the NightlyProcessing
rule in the IP Telephony Analyst.

Absence of source data in the Cluster Capacity Planning database can be caused by a problem with the nightly
summary, such as the rule in the IP Telephony Analyst being disabled, it was not executed due to the trigger not being
met or it simply failed. Further troubleshooting is required if this is the case by using the AUTOOUT record to track
down the outputs from the overnight processing.

Blog: What Optimal Transaction Performance Means

A number of our customers use Prognosis to monitor the health of their payment systems. As part of this, they monitor the transactions flowing through the system ...

Read blog