Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
on
12-06-2017
05:07 PM
- edited on
10-15-2021
09:01 PM
by
Claudia.Landiva
The assumptions made before the derived metrics calculation is initiated are:
The limitation when using the derived metrics calculator is:
A derived metric cannot be reused in another derived metric
If a derived metric has to be calculated at different levels, each metric has to be specified separately in the list of metrics under the derivedMetrics
section. For example, in the following metric tree:
Server1
Queue
Queue1
RAM ops : 9
Hdd ops: 3
Total ops:12
Queue2
Total ops : 2
Hdd ops: 6
Total ops:8
Total ops: (12 + 8 = 20)
If the "Total ops" metric is required both at the queue level and server level, then the derivedMetrics
section looks as follows:
- derivedMetricPath: “{x}|Queue|{y}|Total ops" //queue level Total ops formula: “{x}|Queue|{y}|RAM ops + {x}|Queue|{y}|Total ops” - derivedMetricPath: “{x}|Total ops" //server level Total ops formula: “{x}|Queue|{y}|RAM ops + {x}|Queue|{y}|Total ops”
The queue level “Total ops” derived metric cannot be used for calculating the server level or any other level derived metric.
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form