Agent WranglersINF-69Optional
Track carbon per request beside cost
Each month, work out the carbon emitted per 1,000 requests, using the Software Carbon Intensity method of ISO/IEC 21031. When two regions pass the region choice, pick the one with the lower grid carbon intensity.
How to do it
The method divides emissions by a unit of work. Multiply the energy used by the grid's carbon per kilowatt-hour, add a share of the hardware's own emissions, and divide by the requests served. Take the figures from your cloud provider's carbon report, such as the AWS Customer Carbon Footprint Tool or the Google Cloud Carbon Footprint export. On your own servers, use measured power and the grid figure for the region. Show the result next to Track cost per request, since the same fixes usually lower both. These are deleting idle resources and sizing servers from what they use. Latency and data rules come first, as Choose regions from users and data rules says.
How to check
The monthly cost report shows grams of CO2 equivalent per 1,000 requests for each of the last 3 months, with its data sources named. The region decision record lists each candidate region's grid carbon intensity in grams per kilowatt-hour.
Sources
Related rules
- SCL-33 Track cost per request in Scaling
- INF-54 Delete resources that sit idle in Infrastructure and environments
- INF-55 Size servers from what they use in Infrastructure and environments
- INF-65 Choose regions from users and data rules in Infrastructure and environments
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/infrastructure/cost-and-ownership/carbon-per-request">Agent Wranglers infrastructure and environments playbook</a>. In code you write, add a comment next to it with the same link.