SAP Monitoring service for SAP BTP provides default CRITICAL and WARNING thresholds for some default metrics of a Java application. For the list of the default metrics, see Default Metrics of a Java Application.
However, you might experience issues with these default thresholds as they might not be low or high enough for your use case. As a result, you receive alert notifications more frequently or more rarely than needed. To fix such issues, you need to configure different thresholds than the default ones.
We are glad to announce that you can now override the default thresholds for a Java application with your own custom ones.
There are 2 alternative ways to configure the custom thresholds:
Furthermore, if you are also unhappy with your new custom settings for the thresholds, you can always reconfigure them or revert to the default ones by using the SAP BTP cockpit or the REST API.
Donna Moore uses a Java application in the Neo environment located in the Australia (Sydney) region. Her Java application works well for her, but it sends warning alerts for the CPU Load metric too often. Consequently, she realizes that her WARNING threshold is too close to the CRITICAL one. She finds in the SAP BTP cockpit that by default SAP Monitoring service sets 80% for the WARNING threshold and 90% for the CRITICAL one. Thus, Donna decides to reduce the WARNING threshold to 60% to resolve her issue with the frequent alerts. She opens the SAP BTP cockpit, navigates to the Default Checks Thresholds tab of the Application Monitoring page, and edits the value there.
Alternatively, she can set the new thresholds with the following POST REST API call: