A report displays Central Performance History (CPH) data. This database is the long-term memory for all relevant performance data for your IT landscape.
You can use reports to display the developments of performance values over time, for example to
· Document the fulfillment of Service Level Agreements (SLAs)
· Identify and correct possible performance problems in good time
· Identify connections between different performance values
The basis of a report is always a report definition. In a report definition, you define, among other things:
· For which MTE classes performance values should be displayed in the report
· The time granularity in which the values should be displayed
You can ultimately create a report (manually or automatically as a regularly scheduled job) on the basis of a report definition of this type. In the report, you define
· The time periods for which data should be displayed
· The format in which the data should be displayed (such as directly on the screen, or exported as an Excel worksheet)
The distinction between report definition and the actual report serves primarily to allow you to more easily create reports for particular MTE classes (such as CPU utilization, buffer quality, or response times): You only need to create the definition once, and you can then reuse these definitions as required.
Note that displaying data from the CPH (reporting) and storing data in the CPH (by Assigning Collection and Reorganization Schemata) are independent of each other. To use the CPH, you must perform both steps, or at least activate the predefined default settings (see Tutorial).
Central Performance History of the Monitoring Architecture start page