Technical Prerequisites

The following technical prerequisites have to be met in order to use the RFC monitoring:

  • The managed system is ABAP based system with basis release ≥ 7.0
  • The managed system as at least ST-PI  2008_1 SP06 or higher

Performance measurements are based on Real-User Monitoring (RUM) which is also a part of SAP Focused Run. When RFC performance monitoring is set up, RUM is automatically configured in the background.

Integration Monitoring Setup

Available Monitoring Categories

The available monitoring categories are:

  • RFC (Performance): Response time of the RFC destination based in Real-User Monitoring data
  • Connection Monitoring (SM59): Availability of RFC destination defined in SM59 in the ABAP system

Available Filter Options

RFC (Performance)

For RFC Performance Monitoring, you can collect all RFC destinations in the managed system. You can also use the following filter parameters, to restrict the data collection:

  • Function Module: The name on the called function module that you want to monitor, as seen in RUM.

Connection Monitoring (SM59)

For Connection Monitoring (SM59) you have to provide at least the connection type and the connection name:

  • Connection Name (mandatory): Name of the RFC destination as in SM59
  • Connection Type (mandatory): Type of the RFC destination as in SM59
 

Available Metrics

For interfaces of type RFC the following metrics are collected:

RFC (Performance)

  • RFC Response Time: The average response time of the RFC requests measured in RUM
    • Additional filter fields:
      • Previous Component: Previous component in the request path in RUM

Connection Monitoring (SM59)

  • Not available (via ping) RFC Destinations: Indicates that RFC destinations have not been available via RFC ping during the last collection interval
    Metric parameters:
    • LAST_N_MEASUREMENTS = Only consider the RFC if it wasn't available for the last N measurements
  • Not available (via logon) RFC Destinations: Indicates that RFC destinations have not been available via logon check during the last collection interval
    Metric parameters:
    • LAST_N_MEASUREMENTS = Only consider the RFC if it wasn't available for the last N measurements
  • RFC Latency: Latency of the RFC destination