The Monitoring and Alerting Infrastructure (MAI) passes long-term storage metrics to the Business Warehouse (BW) for reports (for example Interactive Reporting). All MAI metrics are relevant for reporting, by default, so they are written to BW.
System load problems, for example MAI and reporting performance problems, too large metric data volume in BW, or too large Re-Do log files in the database, can arise, depending on the number of metrics to be passed. For the analysis of such problems, it is useful to know which metric types require the greatest data volume in BW. Use this program to determine that.
To display the metric types with the greatest BI data volume, call the transaction MAI_TOOLS. Go to expert mode, and, in the Analysis
tab, choose Metric Types with High BW Data Volume
.
When you call the program, a selection screen in which you can make the following entries, appears.
Display the number of metric types
Specify the number of metric types to be displayed. The metric types with the most metrics in the selected interval are displayed.
Extractor Type
The default extractor type is DPC
(Data Provider Connector). All metrics passed from the Monitoring and Alerting Infrastructure (MAI) to be saved in BW, are checked. There is also the extractor type CCM
for metrics from the CCMS infrastructure.
Time (Hours)
The time period for which the metrics are to be checked. The default interval is 48 hours, so the metrics which were written into BW in the last 48 hours are examined.
Make the required entries, and choose (Execute
). The metric types with the most metrics are displayed in a table:
Column Title | Description |
---|---|
| The technical name of the metric type in the reporting is displayed. This can be the name of the MAI metric type, because they are mapped. This ensures the continuity of the data in BW, independently of the supply infrastructure. |
| The technical name of the MAI metric type is displayed. Note The system ID is added to host metrics when the data record is saved in BW, so there can be several entries per metric type for host metrics. End of the note. |
| The short description of the metric type is output. |
| The ID of a metric type is a 32–character GUID, which is shown, for example, in various log messages. |
| The selected extractor type, |
| The number of metrics written to BW for the selected time interval, is output. This number is a relative measure of the BW memory requirement. Note Simple metrics usually have one metric per managed object (e.g. a dialog response time per ABAP instance. Metric groups (e.g. the proportion of a file system used End of the note. |
If you determine that some metrics which you do not need for reporting have a particularly large memory requirement in BW, you flag them as not relevant for reporting. Proceed as follows:
Determine which template, which managed objects and which monitoring application case are affected:
The flag for whether a metric is to be saved in BW, is saved in templates. To determine which templates are assigned to a metric, use the program Display Metric Details
(see Display Use of Program Metric Details). Copy the Type ID of the metric type into the clipboard.
Run the program by calling transaction MAI_TOOLS, and choose Disply Metric Details
.
Copy the ID into the input field Metric Type ID
in the selection screen, activate the Display Assigned Templates
flag, and choose (Execute
). The assigned templates are listed, with other information. The Monitoring Use Case
and the Managed Object Name
are relevant.
Change this template or, if it was delivered by SAP, base a customer template on it:
Note
The handling depends on the monitoring use case. The following description refers to the System Monitoring
use case.
Start the SAP Solution Manager configuration by calling transaction SOLMAN_SETUP, choose Technical Monitoring
in the navigation bar, and choose a monitoring use case in the Technical Monitoring
group box.
Go to the Template Management
and choose this template in the list.
Go to edit mode by choosing Edit
.
If it is a template delivered by SAP, choose Create Customer Template
, and specify a name.
Go to the Metrics
tab, choose a metric, and Change Settings
.
In the Metric Type Details
subscreen, choose the Data Usage
tab, and delete the Send Values to SAP NetWeaver Business Warehouse
flag.
Save your changes
Copy and activate the changed template for its managed objects. The procedure depends on whether the template is new or adapted:
You are still in SAP Solution Manager configuration. Go to Specify Scope
and select managed objects.
Go to Monitoring Setup
.
For a new template, choose Assign Templates
for the managed objects, and choose the new template.
Choose
.