SAP BTP, Cloud Foundry environment

This page explains how to connect SAP BTP, Cloud Foundry environment to SAP Focused Run. For the setup of the supported monitoring applications, please click on the monitoring application below.

Currently, the following monitoring applications are supported for SAP BTP, Cloud Foundry environment:

Setup Steps in SAP BTP, Cloud Foundry environment

Setup Steps to Enable Monitoring for Customer-built BTP Applications

As of SAP Focused Run 4.0 FP02, Health MonitoringException Monitoring, and Real User Monitoring can collect OpenTelemetry metrics sent via the OpenTelemetry@SAP infrastructure. These metrics are created in applications built by customers running in SAP BTP Cloud Foundry, after the application has been properly instrumented. 

To enable SAP Focused Run to receive OpenTelemetry metrics for cloud services you need to activate OpenTelemetry via the SAP Focused Run Reverse Proxy using SAP Cloud ALM. Please follow the following setup document to do this:

To enable your custom SAP BTP application to send OpenTelemetry metrics you have to instrument it. You can find information on how to instrument your custom SAP BTP application to send OpenTelemetry metrics to SAP Cloud ALM here:

The setup in the custom SAP BTP application is identical for SAP Cloud ALM and SAP Focused Run. The data routing infrastructure inside SAP Cloud ALM makes sure that the metrics are sent to the correct receiver. 

Setup Steps in SAP Focused Run

Input Values for SAP BTP, Cloud Foundry environment

  • Environment: Cloud Foundry
  • Account: Your account ID
  • Root Account URL:
    • Cloud Foundry: "url" value of the service key

  • Global:
    • API Type: Alert Notifications (field is obsolete w/ SAP Focused Run 4.0 FP03)
    • API Root URL: "url" value of the service key
    • Description: A meaningful description
    • Use Case: Choose Exception Monitoring
  • Authentication:
    • Type: OAUTH
    • OAuth URL: "oauth_url" of the service key
    • Client ID: "client_id" of the service key
    • Client Secret: "client_secret" of the service key
  • Section 'Proxy':
    • If necessary add proxy information to connect to the cloud service