|
|
|
|
|
by lazide
49 days ago
|
|
It’s the trade offs. If you have an actual enforced cap, those services will be disabled until you resolve the cap - which depending on the latency for usage updates, may be hours after you pass the cap, and hours after you resolve the issue. Or you have ‘warnings’, and your services keep working, but you spend more $$. Previously, people seemed to be more worried about service outages than raw $$. Now it’s the other way around. It’s a common issue with disk quotas in on-prem systems too, and they tend to cause a lot of similar types of problems in both directions. |
|