Skip to Content
Author's profile photo Former Member

How to troubleshoot the technical monitoring (Basic)

In this document I wanted to write how to troubleshoot in technical monitoring, basically we can have various issues in the technical monitoring like data is not coming, alerts are not getting generated or incidents are not getting generated. This document will provide you the basic details where to start the troubleshooting.

Data is not reported

This is one common issue especially when we are using the customized alerts and metrics. In order to start with, first we need to check the metric id, monitor id etc. All these details can be checked from the below link or navigate to E2E alerting browser.


I had narrow down with the managed object type as technical instance however you can have other multiple options, select the instance


Navigate to the metrics that you have created as shown below


Now go to transaction MAI_TOOLS and the transaction Metric Trouble shoot if you want to perform the metric troubleshooting


Input the monitored object id/ metric id and execute here you will find the various logs associated with your metric.

  However main area of interest here is the data provider connector check for PULL_RFC metrics.


Input the metric and managed object id and execute, here you can see if the extractor is visible and you can check the collection and received parameters


Further you can find the target cube details in RSA1 for e.g 0SM_USER or 0SM_ESRAV etc, and then check in the extractors responsible to fill that data.



Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.