When troubleshooting BPMon objects, you can follow the procedure listed below. Please note that for some monitoring objects (e.g. job monitoring objects or interface monitoring objects) the procedure may differ slightly.
Step 1: Check the Health of the Monitoring Object
Access the Solution Manager Launchpad via transaction /nSOLMAN_WORKCENTER. In there, choose tile "Object Administration" in section "Business Process Monitoring" to access the BPOps Object Administration.
(click picture to enlarge)
Naivgate to your monitoring object. Note that in some releases, you also have to select the system role and the site.
Go to tab "Runtime Overview" and find your monitoring object. Check the Health in column "Health". This column will tell you whether the data collection got triggered as expected and whether the data collection on the managed system was triggered. The trigger of the data collection can also be checked in column "Last BPMon Data Collection". The time stamp displayed there is the same information as in table /SOMO/MA_MAPPING on the managed system.
Step 2: Get the MonID and Context ID for your BPMon Objects
In the Object Administration, use the pen-icon to access the configuration of your monitoring object.
Once you are in the configuration of the monitoring object, you can use the Technical Information and the link to the Directory Browser to find the relevant technical IDs:
In the technical IDs, you can find the Monitoring ID and the Context ID (may also be referred to as managed object ID).
Step 3: Get the Metric ID and the data provider.
Via the Directory Browser, you can access the MAI details for your monitoring object. That includes the metric ID in tab Others" (note that each key figure selected in the monitoring object has a separate metric ID, Via lead selection you choose your key figure).
In tab "Data Collection", you can find the data collection information for your key figure. Important is the data provider, source and collection mode.
Data collection mode "Synchronous Data Collection" refers to direct data collection via RFC, collection mode "Asynchronous Data Collection" feres to data collection via background jo BPM_DATA_COLLECTION_<counter>_<client>.
With Alerting on Analytics, the data collection happens on the Solution Manager via ST-coding. The data source is the Analytics cube filled previously by the Analytics object. The filling of the Analytics cube triggers the data collection for the Alerting on Analytics object. The data collection happens on demand.
Step 4: Manually trigger the data collection
For monitoring objects with synchronous data collection, you can manually trigger the data collection via report E2E_DPC_GET_DATA_CHECK. Run this report via transaction SE38.
Enter the Metric ID and managed object ID for your key figure. Afterwards, execute.
If the data collection was successful, you will see a green rating in the result screen, in addition to an alert text and a measured value.
If the data collection was not successful, you will see a red rating and some kind of error message as in the example below.
Step 5: Check if the Data Collection Extractor is running
To ensure that the data collectors get correctly triggered, check whether the extractors for data collection run correctly. To do so, go to area 'Solution Manager Administration' in the launch pad and execute tile 'Extractors - Alerting Administration'.
This opens the Extractor Administration. There, filter for name "DPC PULL CORE“ and your managed system in column "System".
BPMon data collection for Alerting objects happens via DPC PULL extractors with extended context ST_PI_CLNT<client>_*. Extractors are scheduled per managed system. For Alerting on Analytics, the managed system is the local system (SolMan) and the data collection happens via ST source.
If extractors are active but not running (last data collection time is in the past), check if job EFWK RESOURCE MANAGER is scheduled on Solution Manager (in that case no monitoring objects would return results).
If the 'Last Status' of the data collection is red or yellow, check the Extractor Log details to see the reason.
Step 6: Check for Banned Providers
If the data collection for some monitoring objects does not work according to schedule or does not work at all, it could be that the provider collecting data for the monitoring object is banned.
To check this, access the Extractor Administration as described in step 5 and go to tab "Banned Providers". Look wthether there is an entry for the provider you noted from step 3 (for the relevant managed system).
In case of banned providers, check whether you can change the data collection for the monitoring object from dialog to backround. Note that you may have to change more than one monitoring object. Afterwards, release the data provider and check whether it gets banned again. In case all your monitoring objects are already running in background, open an Incident to SAP.
Step 7: Check Data Collection on the Managed System
If the data collection on the managed system gets triggered correctly (all extractors running as expected), but the results are not returned as expected, you can switch on the data collection logging via the Object Administration (Tab "Runtime Overview").
Highlight the alerting object and choose "Activate Logging". You can choose the time span for which the logging should be active (from 30 minutes up to 4 weeks). Column "Logging until" shows until when the logging for the data collection is active.
Logging should only be activated for troubleshooting for single objects to avoid performance issues on the managed system.
Once logging information is available, you can access the information at the bottom of tab "Runtime Overview".
(Click picture to enlarge)
The logging information will give detailed information regarding when the data collection was triggered, what the result was and when it was finished.
(Click picture to enlarge)
You can also access the information via transaction SLG1 on the managed system (object /SDF/E2E, sub-object /SOMO/BPMON).
- No labels