New SAP requirements for ping, connection, and response times

Products

• DX SaaS

Issue/Introduction

Currently, the metrics for the SAP RFC Z_SF_PROGRAM_ENROLLMENT calls are aggregated under a single processing category, which combines both connection-related metrics (e.g., connection setup, handshake, etc.) and application-level metrics (e.g., business logic execution, payload handling, etc.). 

To improve observability and troubleshooting, we request the following changes: 

Split the current processing metrics into two distinct categories: 

• Connection Metrics 
  Metrics specifically related to establishing and maintaining the RFC connection, such as: 
• Connection start time 
• Handshake latency 
• Time taken to establish the RFC connection 
• Retry or failure counts at connection level 

1. Application Process Metrics 
   Metrics focused on the execution of the actual Z_SF_PROGRAM_ENROLLMENT payload logic after the connection is established, such as: 

• payload processing metrics
• Success/Failure metrics of the transaction 

Application-specific errors or exceptions in traces.

 

Environment

DX O2 SaaS

Resolution

An enhancement requested was already raised in order to it, and will be evaluated and put in our backlog to be deployed soon. 

To follow up on the status of this request, please raise a ticket on Broadcom Support Portal and refer to this knowledge article in order to get the status.