SAP BTP Cloud Foundry Application - Built-in Checks

This check retrieves and displays Cloud Foundry audit events relating to the application, and if any alert is of the types listed in the monitoring parameters CFAuditEventsWarning and CFAuditEventsCritical, the check status is Warning or Critical.

By default, the check only displays the Warning and Critical audit events but this behavior can be configured with the monitoring parameter CFAuditEventsShowAll. By default, alerts since the last run of the check are displayed, but this can be configured with the monitoring parameters CFAuditEventsSinceLastRun and CFAuditEventsPastMinutes.

See also the Custom Check BTP_CF_APP_AUDIT_EVENTS.

This check verifies that the most recent build of the application is STAGED.

If the status is STAGING, the check status is set to Warning. If the status is FAILED, the check status is set to Critical.

This check monitors the percentage of CPU entitlement and percentage of total host CPU that is currently in use, and returns Warning or Critical check status if they are higher than defined thresholds.

This check monitors the percentage of disk used out of the application’s entitlement, and returns Warning or Critical check statuses if the usage is higher than defined thresholds.

This check verifies the status of the current droplet of the application and of the most recently modified droplet.

If the status of the most recently modified or current droplet has a status that is not STAGED or FAILED, the check status is set to Warning.

If the status of the running droplet is FAILED, the check status is set to Critical.

This check lists events in the Cloud Foundry Loggregator Log Cache that represent times the CPU usage spiked above the application’s entitlement.

Warning and Critical check status thresholds can be defined, which will be returned if the time spent in a spike is higher than defined percentages.

If there is less than four hours of data, the check will not return information.

This check reads the contents of the Loggregator Log Cache and identifies entries that are a HTTP error from the application router. The log content is then parsed into a readable and usable format. Warning and Critical check status can be configured for when there are more errors than is defined in thresholds. The check can also be configured to include or exclude specific HTTP errors.

This check reads the contents of the Cloud Foundry Loggregator Log Cache to identify entries that are a Java Exception. It then parses content into a usable and readable format to highlight the root cause of errors.

You can configure the check to include or exclude specific exception types and underlying exception types.

This check monitors the percentage of memory used compared to the amount of memory in the application’s entitlement (allocated memory). Warning and Critical check status thresholds can be configured.

The check monitors process instances of the application, that the number of processes running is more than a defined minimum value, and that the number of crashed processes is below a defined maximum.

This check lists and verifies that all HTTP routes respond in a defined time (in milliseconds). The check status can be configured to return as Warning or Critical if the response time is longer than defined thresholds.

This check monitors the number of days are left until the Cloud Foundry stack in use reaches its end of life date of the underlying Linux distribution.

The check status can be set as Warning or Critical when the end of life date is closer in time than the defined value.

This check is dependent on data released periodically by the vendors of the Linux distributions and by SAP. The support dates used are stored in monitoring parameter CFStackSupportDates. Avantra will attempt to keep the default value up to date, but customers may need to configure updated maintenance dates until the next Avantra release can be installed.