This topic is addressed in detail in KBA 3553320 - How to decide metric threshold values for SAP Cloud ALM Health Monitoring? The KBA outlines some example scenarios using an imagined system landscape, and how their holistic information is used to make informed decisions when establishing metric threshold values.
In short, it is fine to use the pre-packaged "default" threshold values. But you will get maximum value out of Health Monitoring if you opt for custom values. To determine the Custom values, you must consider several factors in order to determine the importance of a metric, and thus what are appropriate threshold values. These factors can include:
- The role the System+Client/Cloud Service plays in the landscape (Dev, Quality, etc.).
- If the metric reaches "Critical", do you consider this a potential "business down" scenario?
- Do you need to be reactive at an earlier stage when a metric value starts to rise, or can you wait until much later for it to be addressed?
Customers know their own landscape and business best, so they are equipped to outline these factors in great detail. Outlining these details for each System+Client/Cloud Service and metric allows you to holistically determine if a metric is important in the first place, and what values best represent the business needs.
SAP Support cannot provide bespoke detailed advice for Customers, as that is not a product issue/bug and instead a Consulting topic that must be addressed by an appropriate organization. If assistance is required, you will need to leverage a Consulting service to get further input.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.