Show TOC

Background documentationData Flow for Monitoring Data

 

E2E Monitoring and Alerting Infrastructure (MAI) data is put in the SAP Solution Manager BI by the Extractor Framework (EFWK), and in particular, the Alerting Framework. No process chains and DataSources are used, the data is written directly to DSOs by extractors.

Note Note

For more information about the data flow for ABAP statistics data, see Data Flow for Statistics Data

End of the note.

The monitoring data is written to the following DSOs using the alerting framework:

DSO

Description

0CCMAGGR

Threshold Values for Performance Data (Direct Write)

0CCMBUFF

Buffer for CCMS Performance Data (Direct Write)

0CCMTHRS

Threshold Values for Performance Data (Direct Write)

0CCMLAST

Last Performance Data

0CCMVAL1/0CCMVAL2

DSO Value for Performance Data in the Last 24 Hours

To allow further use of the monitoring data, it must be written into InfoCubes. This is done by the following two jobs:

  • The job CCMS_CPH_RAW_DATA_UPDATE writes the original data from the DSO 0CCMBUFF to the InfoCubes. It is executed once an hour.

  • The job CCMS_CPH_AGGR_DATA_UPDATE writes the aggregated data from the DSO 0CCMAGGR to the InfoCubes. It is executed once a day.

There are two InfoCubes with identical structures (twin Cubes) for each time resolution of the monitoring data. The data is initially written to the first InfoCube in each case, until the end of retention period for the relevant resolution, as specified in the setup of the interactive reporting. More data is then written to the second Cube in each case, until the end of the set retention period is reached there, too. The first Cube is then deleted, and the cycle starts again.

The monitoring data is used above all by Interactive Reporting and the Metric Monitor. Interactive Reporting only displays aggregates from hourly resolution, the Metric Monitor also needs the raw data. Two different MultiCubes, for different queries, are therefore required.