Hello.
Idea
In DPS licensing model, have the ability to cap (limit) the consumption par capability, per environment.
Problem
In Classic, I can protect myself against over consumptions by capping it per environment and per license type (DDU|DEM|HU|SEC)(some time on a per month basis). This avoids the house of cards effect, where one single not-properly understood setting can jeopardize the entire monitoring. *Real life* examples: One single log source switched to trace level (factor >= x1000 !), can burn DDU allocation, One single over verbose metric Prometheus source can blast the DDU allocation in 1 day. Uncontrolled RUM enabled applications can drain the DEM allocation.
AFAIU, in DPS one single capability over consuming can either block all capabilities if budget is drained empty, and/or incur unplanned non provisioned extra financial cost. In other words I see DPS as extra operational risks, extra financial risk, and extra %FTE to keep in check all the very nice alerts we could set up - yet none of them avoiding the risk.
Practically
Prior to license model migration from Classic to DPS, I have difficulties selling it to my management : we don't really need DPS (for now), it incurs more operational and financial risks, and will requires some extra FTE to fiddle through. (By 24.08.2026 a forum search on DPS reveal quite some draw backs, like extensions management cost calculation gone, excel extracts, dashboard reinvention, loss of insight like Settings:Consumption:Davis data units pools, ...).
Note
IMHO it is not enough to be told "but, you can control and verify these through alerts / dashboards". I feel I'd prefer circuit brakers. Also telling me "the DPS budget can be reallocated temporarily somewhere else" means that I'll put at risk an other capability, and simply postpone the problem.
Regards.
--
Gilles
