Loading...
Loading...
In order to handle outliers in APM scoring engine, we have target max and target min values in indicator table. However, when the max application weight that is obtained for a particluar fiscal period, among the business application, the target max and target min are adjusted for scaling purpose. For example, Lets say we have data points as [10,20,30], and the target max and target min defined are 1000 and -200 respectively. Now, if we consider the given target max and target min values, then the scaling of applications would dense down to a single point and rationalizing business applications would not be possible. Hence to avoid this problem, we take the Max(targetMax, max of application weights). and Min(targetMin, min of application weights) So now our target max and target min shall be for above example as 30, 15 respectively. However, there is ask to consider the target max and target min values set in indicator form.
Open the application indicator list. Open an indicator. Notice the target maximum and minimum values. Open the indicator scores list (APM, not PA). Search on indicators where the opened indicator is contained. Notice that the target maximum and minimum values are different than those defined on the application indicator.
We have introduced a new field "consider_absolute_value" in indicator table, upon checking this field, the target max and target min values defined on indicator shall persist.
PRB1487208
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.