You can use the self-monitoring of the Central Performance History (CPH) to monitor the most important functions of the CPH; these include the following data:
You can use the self-monitoring of the CPH both to identify possible errors during the operation of the CPH and to monitor the functioning of the data collection. You can identify how high the workload is during the data collection by monitoring the runtime of the relevant jobs and the number of data records transferred. In the same way, you can monitor the workload due to the reorganization of the performance values and therefore determine the optimal frequency for the various jobs.
The monitor contains the following monitoring tree elements (MTEs):
MTE | Description |
---|---|
Data collection |
Information about the scope and times of data collection |
Remote System: <System ID> |
Subtree with the number of data records that were transferred to the CPH with a CCMS agent (see Collecting and Reorganizing Performance Values) |
... values pushed by agent |
Number of data records, broken down by the resolution (minutes, quarter-hours, and hours) |
Total collection info |
Scope of the data collection in the local system |
Start and end of ... collection |
Start and end time of the job that writes the performance values of the relevant resolution to the CPH |
Runtime ... collection |
Runtime of the job |
Collected ... values |
Number of data records collected by the job |
Server: <Name> |
Scope of the data collection in the local system, broken down by the individual application servers |
Runtime ... collection Collected ... values |
Similar to above, but restricted to the corresponding application server |
General CPH status information |
Error messages for data collection, reporting, and reorganization (including data collection from remote systems) |
CPH error count (collection) |
Number of errors during the last data collection run |
Data collection message |
Data collection error messages; in most cases, either the scheduling for the corresponding job does not exist or is incorrect; or there are communication problems with remote systems or CCMS agents |
Reporting message |
Error messages for automatic reporting (for reports that are started using the periodic job SAP_CCMS_CPH_REPORT) |
CPH error count (reorg/report) |
Number of errors that occurred during the last reorganization run or during the automatic report execution |
Reorganization message |
Error messages for the reorganization of the CPH; in most cases, the scheduling of the corresponding job does not exist or is incorrect |
Reporting |
Scope and last time of the automatic reporting |
Start and end time of report execution |
Start and end time of the job that starts the reports that are to be executed in the background |
Automatic reporting runtime |
Runtime of the job |
Number of created reports |
Number of reports started by this job |
Reorganization |
Scope and time of the last reorganization of the CPH |
Start and end time of reorganization |
Start and end time of the reorganization job |
Reorganization runtime |
Runtime of the job; depending on the scope of the data collection, the reorganization can create a significant system workload , which is why the relevant job, SAP_CCMS_PERFDB_REORG, only runs once a week by default. If this workload is not critical in your system landscape, you can schedule the job more frequently. |
Reorganized objects |
Number of data records aggregated during the last reorganization run |
Deleted objects |
Number of data records deleted during the last reorganization run because the defined retention period was exceeded |
To start the monitor, follow the procedure below:
Central Performance History of the Monitoring Architecture start page