# BTP Cloud Foundry Application - Custom Checks

Here you will find detailed information about Custom Checks for BTP Subaccount monitored objects.

Custom checks are chosen, adapted and deployed by you for one or more monitored objects and they are designed to allow quick and easy fulfilling of business monitoring requirements. Avantra custom checks are a mix of no-code, low-code and pro-code extensions to the Avantra AIOps platform. Each monitored object type has a number of custom check capabilities.

| All custom checks within Avantra have a number of standard or common attributes. For more information please review our page on Custom Checks.

## BTP_CF_APP_LOG_CACHE

Description

This custom check locates entries, based on defined criteria, in the Cloud Foundry Loggregator Log Cache, and returns a Warning or Critical check status if any entries are returned. This is beneficial is there is a need to monitor for entries.

Reference Data

Managed Object | SAP BTP Cloud Foundry Application
Depends on | N/A

Configuration

- In the Include source type field, define source types to include in the monitoring. Separate types by comma, and wildcards `*` are allowed.

- In the Exclude source type field, define source types to exclude in the monitoring. Separate types by comma, and wildcards `*` are allowed.

- In the Include instance ID field, define instance IDs to include in the monitoring. Separate types by comma, and wildcards `*` are allowed.

- In the Exclude instance ID field, define instance IDs to exclude in the monitoring. Separate types by comma, and wildcards `*` are allowed.

- In the Include type field, define types to include in the monitoring. Separate types by comma, and wildcards `*` are allowed.

- In the Exclude type field, define types to exclude in the monitoring. Separate types by comma, and wildcards `*` are allowed.

- In the Message includes string field, define strings to include in the monitoring. Separate types by comma, and wildcards `*` are allowed.

- In the Message excludes string field, define strings to exclude in the monitoring. Separate types by comma, and wildcards `*` are allowed.

- The JSON parse message attempt checkbox, when checked will attempt to parse the message as JSON and allow for filtering on JSON property values. The Ignore messages that are invalid JSON checkbox, when checked will skip messages that are not in a valid JSON format. This only works if the JSON parse message attempt checkbox is checked.

- The JSON property filter is a multi-line list where entries can be added by clicking `+` and removed by clicking `-` on the row that is to be removed. This filter is used to define a property’s string inclusion and exclusion criteria for filtering. Wildcards `*` are allowed.

- The Warning threshold and Critical threshold boxes are numerical entries. These fields are used when the Problem if messages found checkbox is checked.

  If the Problem if messages found checkbox is checked, Warning and Critical statuses would be set if the number of messages are equal or higher than the defined number.

  If the Problem if messages found checkbox is not checked, Warning and Critical statuses would be set if the number of messages are equal or less than the defined number.