How does Dynatrace OneAgent license calculation host units apply to post 16GB?

[ravi_kumar11]

I see Host Units from this link the license calculation applies for 8GB as 0.5 and from 16 GB it's 1 and 32GB it's 2.. so on.

What about the server running with 18GB of RAM does the 1.5 host unit is applied or it will be 2 host units.. ?

[peter_brandl]

If a host falls between the values (e.g. 18GB as in your example) the number is rounded up. Meaning it will consume 2 HU. Detailed documentation also explaining this behaviour can be found here: https://www.dynatrace.com/support/help/reference/monitoring-consumption-calculation/

[Radoslaw_Szulgo]

No it odes not. It will consume 2 host units. Fractions are only for < 16 GB. Eg. 8GB takes 0.5 host units. 4GB takes 0.25HU and <2 GB takes 0.1HU

[Julius_Loman · Accepted solution]

Above 16GB, it is rounded up. So everything above 16GB becomes 2 HU until 32GB. Above 32GB until 48GB it is 3 HU, etc. This applies for full stack mode.

For infrastructure mode, the 0.3 coefficient applies, but the consumed HU will never cross 1 HU. So for a host in infrastructure mode, you will not consume more than 1 HU.

[Kundesaibaba]

please share the details/DOCs along with application/OS name where and how much we applied the Dynatrace for monitoring the HOST unit consumption 

[Julius_Loman]

@Kundesaibaba always check the documentation . If you are on classic licensing (host units) see this. If you are on DPS (new licensing model with host gibihours), see this.

[PierreGutierrez]

Hi @Julius_Loman 

I think that that definition that you mentioned about consumption for Host units - Full Stack has changed.
As I understand it, the documentation does not mention any rule that rounding up is from 16Gb.
https://docs.dynatrace.com/docs/shortlink/application-and-infrastructure-host-units#host-units 

For that reason, with the documentation, I understand that now in all cases the rounding is upwards (shown in the example)

[Julius_Loman]

@PierreGutierrez no it has not changed. It was always rounded up, (also below 8GB), I just did not specifically mention that in my post as the question was for hosts above 16GB. There is also a tolerance (not sure about the exact limit, but I think there is 500MB above 16GB and a lot less below 16GB), so a host with 16.4GB RAM is still 1HU and 16.5GB becomes 2HU.

[nils_stellhorn]

Hi Julius,

Coincidentally, I was working on a host unit metric to ingest into our Dynatrace managed cluster and checked back with the Dynatrace support how it specifically works and if there are any tolerances applicable. I also asked them for a table with Host Unit values based on some GiB examples. This is their response:
If a host falls between two values, e.g. 20 GB of RAM falls between the 16 and 32 tier, the value from 32 is taken.

There is no cutoff point to the tier, in other words it is immediately falling into the following category once it is above the previous tier limit.

In other words, no tolerances are applicable and once you are above the indicated GiB, you immediately get priced by the next higher tier category. 

[Julius_Loman]

@nils_stellhorn Actually there is small, undocumented tolerance. From what I remember, it's 50MiB for hosts under 16GiB and 500MiB for hosts over 16GiB. So a host of 16.3 GiB is still 1 HU while 16.5 is 2HU. 

For HU metric - check for example https://github.com/Alanata-a-s/Dynatrace-License-Reporting-Scripts I wrote a while ago. We internally developed an extension 2.0 which provides this functionality among other features such as automatic host onboarding.