SAP Cloud Platform, the in-memory Platform-as-a-Service offering from SAP, enables customers and developers to build, extend, and run applications on SAP HANA in the cloud. It provides access to a development environment in the cloud. The platform includes a comprehensive set of services for integration, enterprise mobility, collaboration, and analytics.
Unlike the classic point-to-point interfaces like e.g. IDocs, Web Services or RFCs, when talking about monitoring for cloud services, you always also have to consider the integration component of the scenario. For most cloud services, Advanced Integration Monitoring for the cloud service itself concentrates on monitoring exceptions happening in the cloud service. But to fully monitor a cloud service scenario it is also important to monitor the integration between the cloud service and the on-premise backend system. This integration consists of different point-to-point interfaces of different types.
The following section describes the different integration options for the cloud service. Please choose the integration option you are using and consider also setting up the monitoring for the relevant interface types that are part of the integration scenario for the cloud service.
On this page we describe the monitoring categories that are available for this specific cloud service type. For information on how to set up the monitoring categories for the other technical system and cloud service types, please refer to the setup documentation of the respective interface type.
After setting up the monitoring for the single components and interface types, you can use the scenario configuration to group all relevant messages and exceptions of the cloud integration scenario in one Advanced Integration Monitoring scenario. Information how to create scenarios can be found here.
For SAP Cloud Platform the following integration scenarios are possible:
The different scenarios contain the following exceptions and point-to-point connections:
Scenario Component | Monitored Content | Monitoring Category | |
---|---|---|---|
1 | Cloud Services: SAP Cloud Platform Integration | Integration flows (iFlow) in SAP CPI | SAP Cloud Platform Integration |
2 | Cloud Services: SAP Cloud Platform Integration for data services | Exceptions in SAP CPI for data services | SAP Cloud Platform Integration for data services |
3 | Cloud Services: SAP Cloud Platform | Java logs in applications running in SAP Cloud Platform | SAP Cloud Platform Java Neo Application |
Alerts and exceptions sent from the Alert Notification Service | SAP Cloud Platform Alert Notification | ||
4 | On-premise: SAP Cloud Connector | Availability and Performance for SAP Cloud Connector | Available monitoring content in Advanced System Monitoring |
Public cloud service offerings are usually Software-as-a-Service (SaaS) solutions. This means that customers only have access to the service but not to the underlying infrastructure. Hence, the usual way to connect on-premise managed systems to Focused Run does not apply to cloud services.
However, to be able to monitor exceptions and performance in cloud services they need to be connected to Focused Run. This connection is created using the customer and cloud service specific root URL and an end-point definition, which allows Focused Run to receive information from the cloud service.
The first step is to import the SSL certificate into Focused Run. This is valid for all cloud services.
Import Cloud SSL certificate into STRUST
Export Certificate from Browser:
Import Certificate into Focused Run:
For a successful SSL handshake, please make sure the following parameter are set in the SAP Focused Run system:
Additionally you have to perform certain preparations in the cloud service to enable Focused Run to connect to the cloud service.
The following section describes the preparation steps that have to be performed if you run SAP Cloud Platform in the Neo environment. If you run SAP Cloud Platform in the Cloud Foundry environment please go to the next section.
Preparations for Java Application Error Monitoring
Determine Root URL
The API Root URL for SAP Cloud Platform depends on the host on which your account is hosted on. The host depends on the region as described here:
Create User for Java Log Monitoring
To connect to SAP Cloud Platform to collect Java application exceptions you need to provide Focused Run with a user that is allowed to read the default trace.
Write Java Errors into Default Trace
This last preparation step starts already during the development of the SAP Cloud Platform application. To be able to collect application errors, these errors must exist in the default trace for the SAP Cloud Platform java application. Hence developers must write meaningful errors in this trace. The quality of the monitored exceptions completely depends on the quality of the exceptions written by the developer.
Preparations for Alert Notifications
Enable SAP Cloud Platform Alert Notifications
Receiving alert notifications is done via the Alert Notification Service which can be enabled for your SAP Cloud Platform account.
Important: Please be aware that the use of this service is quota based (billable)!
To enable the service please follow the documentation:
Gather Connection Information
To authenticate towards the service you have to create an OAuth client in SAP Cloud Platform. Information how to do this you find here:
Please make sure to note down or copy the client secret, as it cannot be retrieved later on.
You will need the following connection information to connect SAP Focused Run.
Import the SSL certificate for Cloud Foundry
Even if used in the SAP Cloud Platform (Neo) the alert notification service technically runs in SAP Cloud Platform (Cloud Foundry). To make sure that SAP Focused Run can receive alert notifications successfully, you have to import the SSL certificate for Cloud Foundry additionally to the SSL certificate for Neo.
Preparations for E2E Application Tracing
Enable Automatic Trace Upload for SAPUI5 applications
You can enable the automatic upload of the client side trace data, which starts in the background when a trace is ended. Therefore, perform the following steps in your WebIDE or development platform for the SAPUI5 applications in focus.
Note: This operation has to be repeated for each relevant SAPUI5 application.
The following section described the preparation steps that have to be performed if you run SAP Cloud Platform in the Cloud Foundry environment.
Preparations for Alert Notifications
Enable SAP Cloud Platform Alert Notifications
Receiving alert notifications is done via the Alert Notification Service which can be enabled for your SAP Cloud Platform account.
Important: Please be aware that the use of this service is quota based (billable)!
To enable the service please follow the documentation:
Gather Connection Information
To authenticate towards the service you have to create an OAuth client in SAP Cloud Platform. Information how to do this you find here:
Please make sure to note down or copy the client secret, as it cannot be retrieved later on.
You will need the following connection information to connect SAP Focused Run.
Create Custom Alerts
SAP Cloud Foundry doesn't have any available event that come out of the box. Hence to actually receive alerts from application in SAP Cloud Foundry you have to implement the alert creation in your application.
Find more information here:
After gathering all necessary information and creating the necessary connection point or users in the cloud service, you can now create the cloud service in Focused Run.
Input Values for SAP Cloud Platform
If you want to use ANS and Java Logs in Neo, you can use one the root URLs for Neo. The actual distinction happens in the end-point configuration.
The second step is to create the end-point for the cloud service. The end-point is used to actually connect to the cloud service with user and password. Most cloud services use HTTP end-points.
Input Values for SAP Cloud Platform
For SAP Cloud Platform the input values for the end-point depend on the environment and the data you want to collect. For SAP Cloud Platform on Cloud Foundry, only Alert Notification Service events can be collected. For Neo, you can collect ANS events as well as java logs. Since the root URL between ANS and java log differs, you have to create two endpoints if you want to collect both types of data in Neo.
End-point for Cloud Foundry
End-points for Neo
If you want to collect alert notifications:
If you want to collect java logs:
You need the following end-points for the monitoring categories:
To be able to monitor interfaces of a cloud service you first have to add it to Interface & Cloud Monitoring and select the monitoring categories you want to monitor for the system.
In the next step, you see all monitoring categories which are available for the system, depending on the system type and the installed software components. Some recommended standard monitoring categories are preselected.
Select the monitoring categories in scope.
Available Monitoring Categories
For SAP Cloud Platform different monitoring categories are available.
After selecting your monitoring categories you have to maintain filters to define what exactly you want to monitor. Some monitoring categories come with standard filters that usually just select all items of this monitoring category. SAP Focused Run can handle this high amount of monitoring data, so you can stick to this standard filters. Or you can set up filters of your own.
Please note that the filters you set in the 'Monitoring' step filter the data which is collected from the managed system or cloud service. You can also set up filters later in the 'Alerting' step, which will filter the data already in Focused Run.
You can create more than one filter for a monitoring category.
Available Filter Options
You can collect all exceptions and events for SAP Cloud Platform or you can filter them using the following parameters:
SAP Cloud Platform Alert Notification
SAP Cloud Platform Java Neo Application
The following alerts are available in the different environments:
The setup of the filters for the monitoring categories only makes sure that the data is collected, however, alerts are not created automatically. To create alerts and notifications you have to create an alert individually.
In the next sub-step, you have to maintain the filter. For most monitoring categories the available filter fields will be the same as for the 'Monitoring' configuration described above.
For some metrics, you have additional filter fields or you have to maintain metric parameters. You can check the collected data in Focused Run to determine which filter values to use for alerting. Most of the fields can be found in the Collection Context of the collected data.
Please note that the filters on 'Alerting' level filter the data that is already available in Focused Run. They do not influence the data collection itself. You can only filter for data that is collected. Be aware of this if you created strict filters in the 'Monitoring' step.
In the last sub-step you have to activate the alert:
For single exceptions, the threshold type is always 'Already Rated'. This means depending on the calculation frequency the number of exceptions is checked and an alert is created if this number is bigger than 0. If you want to reduce the number of alert for these metrics, you could increase the value for the calculation frequency to increase the time between checks.
Available Metrics
For SAP Cloud Platform the following metrics are collected:
SAP Cloud Platform Alert Notification
SAP Cloud Platform Java Neo Application
To collect also the Java application part of a trace you need to activate the statistics for the Java application that you want to trace in SAP Cloud Platform.
Note: You need the role 'Developer' to start the statistics collection
To prepare SAP Focused Run for the use of trace analysis, please follow this documentation. For more information on the E2E Trace functionality in SAP Focused Run please refer to Trace Analysis.
You can start Trace Analysis for any SAPUI5 application, using the Diagnostics functionality, as described in the help portal (<Alt>+<Shift>+<Ctrl>+S key combination). Note: For mobile devices, refer to Mobile Diagnostics.
Important: Make the end-user starting a trace aware that his provided user-id is recorded in involved systems, as part of the trace data.