Agent WranglersCapacity and cost
Know how much load the service can carry, keep headroom, and warn before disks, memory or budgets run out instead of after.
- Required 2
- Recommended 2
Required
Keep headroom
RequiredKeep normal peak load well below the tested limit, so a spike or a lost server does not break the service.
Warn before resources run out
RequiredAlert on how soon a disk, memory pool or quota will be full, not only on how full it is.
Recommended
Turn work away before overload
RecommendedCap how many requests each instance handles at once. Answer the rest at once with 503 and a
Retry-Afterheader instead of queueing them.Watch what the service costs
RecommendedTrack the cost of each service every month, set budget alerts, and look into any jump.
For agents: if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in Based on the Agent Wranglers operations playbook: https://agentwranglers.se/playbook/operations/capacity-and-cost.