@Sunjit Tara
Instana is a full stack observability tool that you can use to monitor SAP. This is the second blog in the series on Transaction Code (TCode) analytics.
Read our first blog, SAP ABAP Local Transaction Analytics Using Instana, on the basics of TCode analytics.
This blog covers Erroneous TCodes, which are TCodes that could be not executed successfully. With the addition of this feature on Instana, now you can detect errors from TCode transactions and describe the root cause in Application perspective view.
All the Tcodes executed on a SAP system are organized under a single service named after the SAP system, for example, if your SAP system is called IL4, the TCode analytics associated with it will be tagged under the IL4 Service. Each TCode is represented as an endpoint within that service. You can monitor execution metrics such as throughput and latency in the service dashboard.
The Erroneous TCodes are visualized as shown in the following example. To view the visualization, on the Instana UI, go to Applications -> Services -> Summary.
Figure 1: Erroneous TCodes
The Summary page contains a section labelled as Top Endpoints where you can click the Erroneous Call Rate tab to view TCodes that were run with errors.
Figure 2: Top endpoints
Instana represents TCodes as endpoints. To view the details of TCode executions, click the Endpoints tab. Each TCode that is executed in the SAP system within the selected time range is listed along with a count of all the TCode Executions as shown in the Calls Column. The count of failed TCode executions are shown in the Erroneous Calls column along with a percentage of Erroneous TCodes in the Erroneous Call Rate column.
Instana continuously analyzes the latency of TCode executions and when it detects certain TCodes executions with abnormal latency, a Smart Alert is generated. When you click the Warning icon for the execution of the TCode SE38, endpoints similar to the following example are displayed.
Figure 3: Endpoints
You can click the Analyze Calls button to view the Unbounded Analytics dashboard. In the Analytics dashboard, you can filter called based on the SAP user, report, and so on. You can get a detailed breakdown of all calls that belong to a TCode along with the Timestamp, latency, and so on. The erroneous TCodes are tagged with a red dot. By examining these spans, you can find the root cause of the issue within this transaction.
Figure 4: Calls overview
You click a call to view details on the Call Spans, the details include error message, timestamp, user, call type, and component.
Figure 5: Call details
In addition to the analytics view, each dashboard features a dedicated Error Messages section that provides a summary of all errors that were displayed throughout the system. On this dashboard you can view individual error spans and their descriptions in detail.
Figure. 6. Error Messages section
Conclusion
This blog covers how error scenarios in local ABAP transactions within an SAP system can be monitored and visualized in Instana using the Unbounded Analytics features.
Reference
https://community.ibm.com/community/user/instana/blogs/vipin-m-v/2024/08/13/sap-abap-local-transaction-analytics
https://www.ibm.com/docs/en/instana-observability/current?topic=sap-monitoring-abap-sensor