- Community | AppDynamics
- :
- Community Forums
- :
- Knowledge Base
- :
- Assumptions and Limitations of Derived Metric Calc...

turn on suggestions

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for

- Article History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Email to a Friend
- Printer Friendly Page
- Report Inappropriate Content

**Assumptions:**

The assumptions made before the derived metrics calculation and cluster metrics processing is initiated are:

- All the base metrics (in all different levels) are available (i.e, the metrics have been reported) for derived metrics calculation and cluster metrics processing.
- For a derived metric to be calculated, all its base metrics should have reported a valid Number.

**Limitations:**

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 of them 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 Total ops metric is required both at queue level as well as 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.

Version history

Revision #:

4 of 4

Last update:

12-06-2017
05:36 PM

Updated by: