10c. Monitor service usage
Monitor performance to continue to assess the environmental impact of the service and check the impact of other changes on delivery.
Likely Lead Roles
Platform team, business analysis, service owner
Sub-actions
10c. (i) Ensure measurement tooling is available
10c. (ii) Measure impacts per transaction
10c. (iii) Apply tagging to resources
10c. (iv) Measure application performance
(i) Ensure measurement tooling is available
Hosting platforms should provide access to tools or data to measure cost and emissions. Use service level objectives (SLOs) to set up automated reporting and dashboards.
Environmental benefit:
The right measurement tooling and reporting enables identification of where efficiences can be found for live services.
Read more
(ii) Measure impacts per transaction
Measuring on a per transaction basis means quantifying the impacts of individual API calls, orders, or other transactions processed.
Environmental benefit:
Insight on a per transaction basis will support data-driven decision-making on reducing environmental impacts.
Read more
(iii) Apply tagging to resources
Tagging resources builds on good FinOps practice. It enables granular reporting of consumption and emissions.
Environmental benefit:
Insight on a per transaction basis supports data-driven decision-making on how to reduce environmental impacts.
Read more
(iv) Measure application performance
Continue to measure the performance of software applications to check the impact of changes on delivery.
Environmental benefit:
Continued measurement allows assessment of how changes impact environmental footprint.