Test the reporting feature

Verify that components of the reporting feature are functioning properly.

  1. Check that the reporting services are running.
    1. In the Console, under the Service View of the Cluster Health Dashboard, check that the State of the plc and purger services are STARTED.
    2. If you are running the Derby demo database, check that the State of the derbydb service is STARTED.
  2. Check that there are no error messages in the reporting logs.
    1. View the EGO_TOP/perf/logs/plc.host_name.log file.
    2. Verify that there are no ERROR messages and that, in the DataLoader Statistics section, there are data loader statistics messages for the data loaders in the last hour.
      You need to find statistics messages for the following data loaders:
      • egoconsumerresloader

      • egodynamicresloader

      • egoeventsloader

      • egostaticresloader

      • symsessionloader

      • symsessionhistloader

      • symtaskhistloader

    3. View the data purger and data loader log files and verify that there are no ERROR messages in these files.
      You need to view the following log files:
      • EGO_TOP/perf/logs/dataloader/egoconsumerresloader.host_name.log

      • EGO_TOP/perf/logs/dataloader/egodynamicresloader.host_name.log

      • EGO_TOP/perf/logs/dataloader/egoeventsloader.host_name.log

      • EGO_TOP/perf/logs/dataloader/egostaticresloader.host_name.log

      • EGO_TOP/perf/logs/purger.host_name.log

      • EGO_TOP/perf/logs/dataloader/symsessionloader.host_name.log

      • EGO_TOP/perf/logs/dataloader/symsessionhistloader.host_name.log

      • EGO_TOP/perf/logs/dataloader/symtaskhistloader.host_name.log

  3. Check the report output.
    1. Produce a standard report.
    2. Verify that the standard report produces a chart or table with data for your cluster.

If you were not able to verify that these components are functioning properly, identify the cause of these problems and correct them.