Welcome to the Trouble Shooting Guide for SAP Solution Manager Setup for Technical Monitoring
If this is the first time you are attempting to troubleshoot the SAP Solution Manager Setup for Technical Monitoring I recommend that you take the time to read this short introduction. It is at least important to understand the basic mechanisms on how the data is collected as this will be the first step in trying to determine the issue. The Data Collector is the mechanism that is used to collect the metrics for monitoring. Depending on the type of Data Collector the steps for troubleshooting any particular grey metric will be different and therefore it is important to determine which one is being used. Therefore the first step in your analysis will be to identify the Data Collector and the Metric ID of the grey metric.
The following are the possible Data Collectors you will encounter with a brief explanation to help you get started:
DPC RFC PULL to ABAP Managed Systems
This mechanism is used to collect ABAP Statistics from the Managed System. This is an extractor that is scheduled every 5 minutes is SAP Solution Manager. It uses an RFC connection to the Managed System where it collects the monitoring data. The extractor will call data providers, which are Function Modules, delivered as part of the ST-PI on the managed system. In the Alerting Extractor Framework it has an extended context ST_PI
The most important point to note here is the ST-PI needs to be at the correct Software level as this contains all the coding for the data collect.
DPC PUSH from the Diagnostic Agent
The mechanism is used to deliver monitoring data from the Diagnostic Agent that is the principle Data Collector. The Diagnostic Agent collects the following type of monitoring data:
- SAPOsCol data for OS Monitoring including File System Monitoring
- ABAP Availability for both System and instances (HTTP and RFC) - this is collected every minute
- JAVA Availability for both System and server processes (HTTP and GRMG) - this is collected every minute
- Database metrics that are not available in the database cockpit. This type of data collected is depending on the DB used and what data is available via the DB Cockpit. This is why we now install the Diagnostic Agent to the DB host.
The Diagnostic Agent collects the data locally in an Even Store and depending on the schedule in pushed the monitoring data to the SAP Solution Manager via web service. Availability data is pushed every 1 minutes while all the rest of the monitoring data is pushed every 5 minutes.
The most important points to note about this mechanism is that an XML Configuration file is pushed locally to the Diagnostic Agent which contains all the metric configuration of the metric data to be pushed. Also it relies heavily on the SAP Host Agent infrastructure being correctly installed and up to date.
When the SMD Agent pushes the data this triggers the DPC Push Extractor for the Diagnostic Agent in SAP Solution Manager. The data is then persisted in the metric store for the Alerting Framework and then the data is aggregated to BW.
DPC Introscope Push
The Introscope DPC Push is similar to the Diagnostic Agent DPC Push except that it is the Introscope MoM or the a single Introscope Enterprise Manager that pushes the monitoring data to SAP Solution Manager. This mechanism is only used for non ABAP Systems in particular (not all of the data for these systems is collected by the EM as it usually kept to a minimum) :
- JAVA Performance,
- Sybase Unwired Platform and more.
The most important considerations for this mechanism is that the Diagnostic Agent needs to be installed on the host of the Enterprise Manager where both the XML configuration of the metrics to be monitored and the SAP Solution Manager Web Service and authentication configuration are pushed.
The Management Modules need to be the most recent as this contains the code required for Introscope Enterprise Manager to push the data.
DPC RFC PULL for Database Cockpit
The DPC RFC Push for the database collects all the monitoring data originates from the database cockpit. This is an extractor running in the SAP Solution Manager that uses a local RFC connection to the DB Cockpit.
The most important point is that database cockpit needs to be correctly configured for this database. This is done is the Managed System Configuration
DPC for CCDB
Problem Resolution Procedures for MAI Data Providers
PROBLEM RESOLUTION PROCEDURE IS DISCONTINUED, PLEASE USE GUIDED ANSWERS INSTEAD.
Below the entry point to several guided procedures to troubleshoot MAI Data Providers. The links are organised by managed object type. Each link will direct you to the list of guided procedures to troubleshoot standard metrics delivered by SAP.