Cloud Service - Built-in Checks

CPI_CertificateUserMappingExpiration displays any user mapping certificates that are within the defined expiration window (default is 120 days).

The values in the check match the JMS Resources overview (accessed via Overview / Manage Message Queues monitor. Select Check to execute the consistency checks. Then Details). The list of the critical queues is provided in the check output. There are no monitoring parameters for this check.

CPI_KeystoreExpiration displays any keystore certificates that are within the defined expiration window (default is 120 days).

CPI_MessageLogs checks the SAP Cloud Integration message log for all failed messages over a period of time (default is 21 days) where the statuses is ESCALATED or FAILED.

As of SCC version 2.15.0, this check reads the list of all back-end systems connected to the SAP Cloud Connector and gets detailed information for each connection.

This check retrieves the information about the certificate status on SAP Cloud Connector (SCC) to check the validity of the certificates used.

This RealTime Monitoring check monitors open connections for service channels (connections to the cloud). Check results provide information for any open connections.

This check verifies that the Cloud Connector is up and running. The purpose of this health check is only to verify that the Cloud Connector is not down.

As of SCC version 2.10.0, this check lists all subaccounts connected to SAP Cloud Connector.

As of SCC version 2.11.0, this check displays the data of top time consumers provided by the Cloud Connector performance monitor.

As of SCC version 2.15.0, this check reads the list of all back-end systems connected to the SAP Cloud Connector and gets detailed information for each connection.

This check monitors the memory usage in SAP Cloud Connector (SCC). The SCC API is used to retrieve the physical, virtual, and heap memory used / free counts.

As of SCC version 2.10.0, this check reads the data provided by the Cloud Connector performance monitor.

If Avantra can connect to the cloud service, then SO_Connect is OK and a message showing that the connect attempt was successful is shown.

If Avantra cannot connect, the check turns to WARNING or CRITICAL with an error message.

This check monitors certificates that are seen in the app Maintain Client Certificate. For information on the Maintain Client Certificate app, see SAP S/4HANA Cloud Public Edition Documentation - Maintain Client Certificates.

Warning and Critical check statuses can be set to trigger when the number of days until expiration of a certificate is less than defined thresholds.

The check can also be configured to ignore expired certificates if they remain expired for more than a defined number of days, and to exclude a list of certificate names from being monitored.

This check verifies that the Content Security Policy is enables in SAP S/4HANA Public Cloud. If not enabled, it will give instructions on how to enable the policy. If the policy is configured insecurely with HTTPS or Wildcards, the check will return a warning.

The check can be configured to allow for Wildcards and/or HTTP by using monitoring parameters.

This check is used to monitor the users with critical authorizations.

A user with critical authorizations is defined as one with any business role that contains any business catalog that is also in the SAP standard SAP_BR_ADMINISTRATOR role in the monitored system.

The check is configurable for Warning and Critical status alerts for when the number of users with critical roles reaches certain thresholds, as well as configuring any catalogs or roles for the check to ignore.

This check records the number of failed logons that have occurred within the last hour, compares to the previous hours average over the past week, and alert if the number of failed logons are to high. Additionally, the check can alert for higher than average or higher than an absolute value of failed logons per hour.

This check is required to connect Avantra to the S/4HANA Cloud Public Edition login page (for manual login). Additionally it confirms valid redirection to the SAP Cloud Identity Services, checks that a suitable login screen is provided, and records the time taken for redirection in milliseconds.

Monitoring parameters can be configured to alert if login times go above specific thresholds.

If the redirect fails for any reason, the check status is set to Critical with an error message displayed. If an IAS is unavailable, the check status is set to Warning with an error message displayed.