Semantic conventions for Software Carbon Intensity (SCI / ISO 21031:2022)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- observability-sre
Research direction
Start with the SCI specification and the previous sustainability semantic conventions proposal in issue #2020, then review this issue's proposed components: E, I, M, R, and the composite SCI score. Done means producing a draft set of semantic conventions for review by the General Semantic Conventions SIG, potentially using the federated semconv model.
Written by the indexing model from the issue text.
Description
Background
The Software Carbon Intensity (SCI) specification (ISO/IEC 21031:2022) defines a standardised method for measuring the carbon intensity of a software system. It is maintained by the Green Software Foundation (GSF), a nonprofit consortium of 60+ member organisations operating under the Joint Development Foundation.
The formula is:
SCI = ((E × I) + M) per R
- E — energy consumed by the software system
- I — carbon intensity of the electricity consumed
- M — embodied carbon of the hardware the software runs on
- R — functional unit (normalises the score per unit of work)
The problem
SCI components map directly onto concepts that observability practitioners already instrument: energy consumption, hardware utilisation, and a functional unit. However, there are currently no shared semantic conventions for representing SCI-related measurements in OpenTelemetry. Without them, teams measuring software carbon intensity use inconsistent attribute names and metric definitions, and existing tools such as Kepler cannot be composed into a coherent pipeline without bespoke integration work.
A previous attempt to address this (#2020) stalled in 2023 when the primary driver changed roles.
What we're proposing
The GSF, in collaboration with Sarah Hsu (@greenhsu123), is convening a new project, the SCI for OpenTelemetry, to develop a proposed baseline set of semantic conventions for SCI components, covering:
- Operational energy (
E) - Carbon intensity of electricity (
I) - Embodied carbon (
M) - Functional unit (
R) - The composite SCI score
The deliverable will be a draft set of semantic conventions for SCI, which we will bring to the General Semantic Conventions SIG for review and feedback. We plan to follow the federated semconv model, hosting the registry under the GSF's own organisation.
Why now
Standardising SCI within OpenTelemetry's semantic conventions would make carbon a first-class signal alongside performance, reliability, and cost, using the same registry that already unifies other telemetry signals. Once the vocabulary is agreed, it creates a foundation for downstream tooling: collector components, SDKs, and backends that can emit and consume carbon data consistently across the ecosystem.
Regulatory requirements (CSRD, EU Taxonomy, emerging US disclosure frameworks) are also creating demand from engineering organisations that need to report on software emissions, many of whom already rely on OTel for observability.
Who we're looking for
We are actively recruiting participants for the project. We are particularly looking for people with:
- OpenTelemetry semantic conventions experience, to ensure the output maps cleanly into OTel from the start
- Green software / carbon measurement expertise: SCI, Kepler, carbon intensity data sources
- Instrumentation experience, to inform how conventions would be implemented in practice
- Interest from observability backend vendors, to ensure standardised carbon signals are consumable across the ecosystem
If you have relevant expertise, or know someone who does, we would welcome your involvement.
Applications are open to all now at: https://greensoftware.foundation/assemblies/sci-for-open-telemetry/
Contact
If you'd like to get involved or have questions, feel free to reach out to any of us directly:
- Russ Trow, Operations Director, Green Software Foundation - @russelltrow - [email protected]
- Jamie Cowan, Head of Partnerships, Green Software Foundation - @JamieACowan - [email protected]
- Sarah Hsu, Site Reliability Engineer - @greenhsu123
Related
- #2020 — previous sustainability semantic conventions proposal (2023)
- SCI Specification — the ISO standard this work is based on
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 326
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from open-telemetry/community
-
area/github-membership
Difficulty 1/5 Under an hour Newbie friendliness 1/100
open-telemetry/community#3847 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
open-telemetry/community#3846 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
open-telemetry/community#3844 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
open-telemetry/community#3823 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
open-telemetry/community#3821 · 3 comments ·
Maintainers usually reply within 1 day
All issues in open-telemetry/community
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Deltares/numba_celltree#100 · 1 comment ·
-
auto-reported bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
soup airgap-bundle --bundle-size-cap nan, inf or a cap above ~1.67e299 GiB stops with an internal ValueError/OverflowError (exit 1) instead of a usage errorPossibly taken @Keshemir claimed this today. Openbug claimed difficulty:2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MakazhanAlpamys/Soup#3045 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
dagster-io/skills#80 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day