17 Feb 2022 12:17 PM - last edited on 17 Feb 2022 11:59 PM by Karolina_Linda
I am observing User sessions in total on the Environment details page (screenshot below) to be two time less that the amount reported by metric Session count - billed without replay.
Session replay is not enabled and there is only one application that consumes DEM.
Any idea why there is two times difference between both metrics?
Which one we should consider for license consumption?
Session count isn’t equal DEM units!
Depending on the type of session (real user, synthetic test,…) these consume 0.25 DEM units or 1 DEM unit. You need to do the maths yourself to go from sessions to DEM.
Hi @mkulov ,
what I experienced while building a central consumption monitoring is that you have to make sure to look at all billing metrics. (billing.synthetic, billing.apps.web, ...)
I usually exported those using my timeseries streamer and put them in a fine granular timeseries DB and then on a dashboard which allows me advanced queries/operations on that data. I found that this is pretty precise and always matched the consumption shown by Dynatrace on tenant-level.
Never noticed a difference, unless when not summing up with correct timeframes.
Did you consider the synthetic ones as well (though it shows 0 on your screenshot?)
I did some tests and found this: If you display single value by SUM aggregation of metric "builtin:billing.apps.web.sessionsWithoutReplayByApplication" per actual month interval (since 1st day of actual month) you will get same number of sessions as number displayed in montly environment consumption.
If you have more apps then you have to count it for all of them:
If you have also mobile ones, then +:
Yes, we are using SUM aggregation.
However we are observing value twice bigger than the monthly license consumption.
Yellow box is twice bigger than the monthly black box in the first screenshot.
There is just one application consuming DEM and no session replay.
But you forget to set timeframe to actual month (not last 30 days) !
Yes, good catch.
The consumption is quite constant in this application though and cannot fluctuate by a factor of two.