DDU consumption difference

[tjay]

Hi,

I compared the DDU consumptions between the license overview and a data explorer query for DDU for the same period and noticed that there was a small difference. Can someone explain why they are different?

DDU metrics consumption by monitored entity (sum) - 459 != license overview breakdown for metrics - 451 

DDU log consumption by monitored entity (sum) - 11.4  == license overview breakdown for logs - 11.4

DDU events consumption by monitored entity (sum) - 0 == license overview breakdown for events - 0

Reported metrics DDUs by metric key - 464 != 451 (as shown above)

DDU metrics consumption by monitored entity w/o host-unit included DDUs - 464 != 451 (as shown above)

[Yosi_Neuman · Accepted solution]

Hi @tjay 

Please check the value of DDU metrics consumption by monitored entity w/o host-unit included DDUs metric this should show you the same value as shown in license overview.

For more information please check Included metrics per host unit

HTH

Yos 

[tjay]

Hi @Yosi_Neuman 

Thank you for your reply and I checked the page you mentioned.

Interestingly in the advance mode "DDU metrics consumption by monitored entity w/o host-unit included DDUs" is "builtin:billing.ddu.metrics.byEntityRaw", which reflects the total reported DDUs before any host-included considerations are performed. I thought it would be "builtin:billing.ddu.metrics.byEntity" from the name. The description seems to be contradicting.

"DDU metrics consumption by monitored entity" is "builtin:billing.ddu.metrics.byEntity".

The query results shows as follows.

"DDU metrics consumption by monitored entity w/o host-unit included DDUs" (464) > "DDU metrics consumption by monitored entity" (459) > DDU metrics on the license overview page (451)

In the advance mode it makes sense as the raw value is greater than the consumed.

"builtin:billing.ddu.metrics.byEntityRaw" (464) > "builtin:billing.ddu.metrics.byEntity" (459)

Still, both of them don't match with the amount reported in the license overview page. I tend to agree with @radek_jasinski about the differences in how it is calculated.

[radek_jasinski · Accepted solution]

Complementing @Yosi_Neuman  response:

The discrepancy you're observing between the DDU (Dynatrace Davis Data Units) consumptions in the license overview and the data explorer query for the same period likely arises due to different calculation methodologies or data aggregation processes used in these two views.

In your case, the DDU metrics consumption for monitored entities shows a sum of 459, which is not matching with the license overview breakdown for metrics that shows 451. Similarly, the reported metrics DDUs by metric key show a difference (464 vs. 451). However, the DDU log consumption and DDU events consumption are consistent across both views.

Such differences can occur if the license overview aggregates data differently, perhaps rounding off or filtering certain types of consumption that the data explorer query includes. Additionally, timing differences in data capture and processing might also contribute to these discrepancies. It's also possible that certain types of DDUs, like those not included in the host-unit, are accounted for differently in these two views, as indicated by the difference in DDU metrics consumption with and without host-unit included DDUs.

Radek