Show TOC

Central Performance History of the Monitoring ArchitectureLocate this document in the navigation structure


The Central Performance History (CPH) allows you to save performance values of the monitoring architecture long-term, and to output these values in reports to compare the current performance data with its earlier development.

By default, performance values are only stored in the Alert Monitor for up to 24 hours, which is insufficient for many tasks, especially for the monitoring of Service Level Agreements (SLAs). You can store performance values for selected attributes of any systems in the CPH, and can freely define the storage period and granularity. The CPH should only exist on a central monitoring system (that is, the system in which the monitoring architecture is configured).


The goal of the CPH is to store as much information as possible while at the same time retaining as little specific data as possible. As the quantity of data is constantly growing, it is regularly reorganized. During the reorganization, data is aggregated from one time unit (such as hours) to the next coarser (such as days), and the data in the finer unit is deleted.

To display data from the CPH, you use reports. A report of this type contains a report definition that determines which performance attributes with which granularity the report should contain. To then execute the report, you must only specify the report definition and the time period that should be displayed in the report. You can also automate report execution by scheduling the reports as regular jobs.


If you use SAP Solution Manager for your central monitoring, you can also use the reporting in the System Monitoring work center to display the development of performance data over time (IT Performance Reporting).

Implementation Considerations

Using the functions of the CPH is performed in four steps; you can perform all of the steps both in the Alert Monitor (see: Using the Central Performance History from the Alert Monitor) and in the separate CPH transaction (transaction RZ23N):

  1. Define how long and with which granularity performance values should be retained in the CPH.

    This setting is stored in the Collection and Reorganization Schema. SAP delivers predefined schemata that meet most requirements. The schemata also contain information about the calculation rules that are to be used to aggregate information (see Creating and Editing Day Schema and Creating and Editing Calendar Schema). When doing this, you can weight the different hours of the day and also different days differently, to hide public holidays or hours during the night during the calculation of the aggregates.

  2. Select the performance attributes that are to be stored in the CPH.

    You can assign collection and reorganization schemata to any MTE classes of any systems (see Assigning Performance Values to Collection and Reorganization Schemata).

  3. Create the report definitions in which you determine which performance values are to be displayed.

    In a report definition, you define which MTE classes are to be displayed in which granularity in the reports that are based on this definition (see Creating a Report Definition).

  4. Execute the reports that display data from the CPH on the basis of a report definition.

    You can execute reports directly or schedule them as regular jobs that are then automatically executed. Depending on its settings, you can display the report directly on the screen or output it as a file (see Scheduling and Executing a Report).