[ACTION] Proposal 3 - Report

[ADiTuri]

Task Description

Parent Issue #83

This issue is about discussing a strategy on the reporting capabilities of a Green Review.
There are two open points to address:

• Metrics: What kind of metrics do we select for a green review?
• Long term storage: Where and how do we save the green metrics?

Metrics

At the moment we have agreed on the SCI score calculation, details of how we compute the SCI score can be found here.

Open points on the current approach

From the last milestone we had two open points:

1. Embodied carbon: plays a significant role in the SCI. This might not be relevant for the CNCF projects interested in the review, cause it is just dependent on the infrastructure we choose to use.
2. Functional unit: We choose a time functional unit of 15 minutes, are we fine with this or is there any other improvement we would like to do?

Possible extensions

This issue would also like to address possible extensions on the metrics we would like to consider:

• Traditional SRE metrics (provider could be the simple k8s SDK)
• More low level energy metrics (right now we have an aggregate at container level)
• Any other metric that might be interesting for future release

Long Term storage

This section works under the assumption that we have already a chosen set of green metrics.
At the moment we don't store any metrics, the energy metric is just show live on the dashboard for the target container. We would like to store the metrics for future analytical purposes.
The proposal should suggest:

• a long term storage technology
• a process for storing the green metrics
• integration with the current grafana dashboard

Goals to achieve

• Draft the proposal for the metrics extension
• Draft the proposal for the long term storage
• Review the proposals and merge

Nice to have

• Find experts for the metric topic
• FInd experts for the long term storage topic

[rossf7]

The 3 SRE metrics for CPU and memory requested by the Falco team are in this comment

We should consider these in the proposal to not lose the previous discussion.

[ChrisChinchilla]

@rossf7 and @ADiTuri I am more than happy to think about the metrics part to begin with as it fits with my work right now too. I am less confident or experienced on ideas for the storage part, but it's also an excuse to explore some new database engines…