17 Nov 2021 06:59 PM - last edited on 15 Jul 2022 03:59 AM by AgataWlodarczyk
I had a support ticket because I tried to have a chart on a dashboard with Avg and 90% values of the same custom metric, but they both would not display at the same time. Was told that I needed to put them on two separate charts.
They should be allowed on the same chart - other combinations of avg, max, and count are allowed.
Solved! Go to Solution.
I just gave it a try with one of the built-in metrics and it works together for both aggregations. What type of custom metric do you have?
It's a response time on a calculated service metric, for Database Service Type filtered on a particular sql statement
can you please provide more details because as @Babar_Qayyum points out that should work Could you maybe send me your support ticket?
Sorry, I missed your reply! I have checked your referenced ticket and triggered a review of it internally with the backend team responsible because I don't understand why it should be possible with all other metrics but not with the one you're using. I'd argue that's a bug! In the meantime, have you tried to do plot it again? So is it still happening that you don't see it? Just to be sure.
Again, I am sorry for missing your reply!
The issue is not that Dynatrace cannot chart both values at the same time. The issue is that the values are identical. Let me explain.
Unless configured otherwise in the Code mode tab, the Data Explorer performs a space aggregation on the metric datapoints. After applying such a space aggregation in Dynatrace, you can use all available aggregations on the transformed data. In many cases, this behavior is reasonable, but there are pitfalls.
For example, consider a counter metric that natively only supports the aggregation value. The metrics has the dimension host and the following values per host:
After applying a space aggregation, the per host values are merged and you can chart the min (= 1), the max (= 5), the sum (= 8), the avg (= 2.66) and so on. Also the percentiles are calculated based on the three values. Reasonable, isn't it?
In contrast, let's assume there is only the series for HOST-1 available and no additional series/dimensions. After applying the space aggregation, you can again apply all aggregations. However, as there is only one series, the space aggregation does in fact not aggregate any values. Consequently, the values for avg, min, max, sum as well as the percentiles are the same (i.e., 1 for the example above).
The issue is also described on the Metrics API FAQ page.