Reporting with the Central Performance History 

Purpose

The most important functions of reporting with the Central Performance History (CPH) are explained in the following sections:

·        The basis for reporting is the report definition (see Creating a Report Definition). In a report definition, you define which data the report should contain; namely:

¡        MTE class

¡        Systems of the MTE classes

¡        Aggregate and granularity

As you will usually be interested in the history of the same MTE classes again and again with reporting, you create the most important report definitions during the configuration of the CPH.

·        To execute a report, first specify the desired report definition. When Scheduling and Executing a Report, you decide which period the report should cover and the format of the output of the report. You can also schedule reports as a periodic job that is then automatically run, for example, once a month.

·        You have various options for archiving executed reports. You can, for example, save them as ASCII or Excel files or in a separate database. You can display the contents of the reports of this data at any time in the CPH (see Displaying Central Performance History Reports).

·        In addition to the performance values, you can also display the header data of a report (see Displaying Report Properties).

 Central Performance History of the Monitoring Architecture start page