You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-3Lines changed: 4 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ resource demand data as [Attributes](https://opentelemetry.io/docs/concepts/sign
8
8
9
9
In addition to attaching Span attributes for OpenTelemetry Traces this extension publishes the resource demand data as OpenTelemetry [Metrics](https://opentelemetry.io/docs/concepts/signals/metrics/) for all entry level transactions (e.g., API calls) of an instrumented application. You can find a list of metrics published by this extension in the corresponding [section](#OpenTelemetry-Metrics-published-by-this-extension). If you are just starting with analyzing the resource demand of your application this is the best starting point for you, before you dig into the span attributes to analyze where exactly the resources are consumed.
10
10
11
-
Furthermore, the extension follows the [Methodology](https://www.cloudcarbonfootprint.org/docs/methodology/) published by the [Cloud Carbon Footprint (CCF)](https://www.cloudcarbonfootprint.org/) project to calculate the carbon emissions of an instrumented application. It contains the [Cloud Carbon coefficients](https://github.com/cloud-carbon-footprint/ccf-coefficients) for the biggest clouds (AWS, Azure, and GCP) and their instances. Using the resource demand data and the data of the CCF coefficents allows you to calculate the carbon emissions of single API calls of your application. This is usually done in an OpenTelemetry compatible backend, you can find an example on how this works in the [Demo](#demo) section of this document. If you want to use the extension for your own application check out the [Quickstart](#Quickstart) and [Configuration Options](#configuration-options) section of this document.
11
+
Furthermore, the extension follows the [Methodology](https://www.cloudcarbonfootprint.org/docs/methodology/) published by the [Cloud Carbon Footprint (CCF)](https://www.cloudcarbonfootprint.org/) project to calculate the carbon emissions of an instrumented application. It contains data from the [CCF coefficients project](https://github.com/cloud-carbon-footprint/ccf-coefficients) for the biggest clouds (AWS, Azure, and GCP) and their instances. Using the resource demand data and the data of the CCF coefficents allows you to calculate the carbon emissions of single API calls of your application. This is usually done in an OpenTelemetry compatible backend, you can find an example on how this works in the [Demo](#demo) section of this document. If you want to use the extension for your own application check out the [Quickstart](#Quickstart) and [Configuration Options](#configuration-options) section of this document.
12
12
13
13
# Quickstart
14
14
@@ -69,7 +69,7 @@ This application will run until you stop it and generate data. While it is gener
69
69
70
70
http://localhost:3000/grafana/dashboards
71
71
72
-
After some time you can see the data produced by this application in the following dashboard. As an example the CPU and memory demands are shown as they are supported on most plattforms as well as the Emission Calculation Factors. Furthermore, we have integrated a [Software Carbon Intensity](https://sci.greensoftware.foundation/) calculation for each transaction based on this data. This calculation is based on our work presented at the [Workshop on Challenges in Performance Methods for Software Development (WOSP-C) 2024](https://www.retit.de/wp-content/uploads/2024/05/Green_Software_Metrics.pdf) and [EcoCompute](https://www.retit.de/wp-content/uploads/2024/04/2024-04-25_How_to_Measure_CO2-Emissions_For_Every_API_Call_Of_Your_Microservices.pdf) with the main difference that we are now using the [Cloud Carbon coefficients](https://github.com/cloud-carbon-footprint/ccf-coefficients) instead of an external datasource for the emission data.
72
+
After some time you can see the data produced by this application in the following dashboard. As an example the CPU and memory demands are shown as they are supported on most plattforms as well as the Emission Calculation Factors. Furthermore, we have integrated a [Software Carbon Intensity](https://sci.greensoftware.foundation/) calculation for each transaction based on this data. This calculation is based on our work presented at the [Workshop on Challenges in Performance Methods for Software Development (WOSP-C) 2024](https://www.retit.de/wp-content/uploads/2024/05/Green_Software_Metrics.pdf) and [EcoCompute](https://www.retit.de/wp-content/uploads/2024/04/2024-04-25_How_to_Measure_CO2-Emissions_For_Every_API_Call_Of_Your_Microservices.pdf) with the main difference that we are now using the [Cloud Carbon coefficients](https://github.com/cloud-carbon-footprint/ccf-coefficients) instead of an external datasource for the emission data.
73
73
74
74

75
75
@@ -145,4 +145,5 @@ Bytes written to the network by the thread processing the Span...
145
145
Bytes allocated in memory by the thread processing the Span...
146
146
147
147
io.retit.startheapbyteallocation- ...at Span start time
148
-
io.retit.endheapbyteallocation - ...at Span end time
148
+
io.retit.endheapbyteallocation - ...at Span end time
Copy file name to clipboardExpand all lines: extension/src/main/java/io/retit/opentelemetry/javaagent/extension/emissions/CloudCarbonFootprintData.java
+9-9Lines changed: 9 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -81,11 +81,11 @@ public CloudCarbonFootprintInstanceData getCloudInstanceDetails() {
0 commit comments