Merge branch 'main' into 456

Boavizta · Mar 15, 2024 · 7349ccd · 7349ccd
2 parents c0d8053 + f63af6d
commit 7349ccd
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 8 deletions.
diff --git a/cloud-scanner-cli/test-data/DEFAULT_RAW_IMPACTS_OF_M6GXLARGE_1HRS_FR.json b/cloud-scanner-cli/test-data/DEFAULT_RAW_IMPACTS_OF_M6GXLARGE_1HRS_FR.json
@@ -3,8 +3,8 @@
     "gwp": {
       "embedded": {
         "value": 0.0016,
-        "min": 0.0009013,
-        "max": 0.002547,
+        "min": 0.0008995,
+        "max": 0.002545,
         "warnings": [
           "End of life is not included in the calculation"
         ]
@@ -37,8 +37,8 @@
     "pe": {
       "embedded": {
         "value": 0.021,
-        "min": 0.01188,
-        "max": 0.03333,
+        "min": 0.01186,
+        "max": 0.03331,
         "warnings": [
           "End of life is not included in the calculation"
         ]

diff --git a/docs/src/explanations/methodology.md b/docs/src/explanations/methodology.md
@@ -4,17 +4,17 @@ Cloud scanner uses the Boavizta methodology to estimate the impacts of cloud res
 
 ## Source of impact data
 
-Impact data is retrieved from [BOAVIZTA reference data API](https://github.com/Boavizta/boaviztapi/) v1.1.x.
+Impact data is retrieved from [BOAVIZTA reference data API](https://github.com/Boavizta/boaviztapi/) v1.2.x.
 
 ## Methodology
 
 The general approach of Boavizta is described in [Digital &amp; environment : How to evaluate server manufacturing footprint, beyond greenhouse gas emissions? | Boavizta](https://boavizta.org/en/blog/empreinte-de-la-fabrication-d-un-serveur)
 
-The impacts (use and embedded) are attributed according to the principles described in [Cloud instances - Boavizta API documentation](https://doc.api.boavizta.org/Explanations/devices/cloud/).
+The impacts (use and embedded) are attributed according to the principles described in [Cloud instances - Boavizta API documentation](https://doc.api.boavizta.org/Explanations/services/cloud/).
 
 The results are similar to what you can visualize in [Datavizta](http://datavizta.boavizta.org/cloudimpact), but with automated inventory.
 
-⚠ Cloud scanner **underestimate the impacts of the cloud resources**. Because it only considers the _instances_ and _block storage_ a lot of impacts (network, potential redundancy, cloud control plan) are not included in the estimation.
+⚠ Cloud scanner **underestimates the impacts of the cloud resources**. Because it only considers the _instances_ and _block storage_ a several sources of impacts (network, potential redundancy, cloud control plan) are not included in the estimation.
 
 See also [other limits](../reference/limits.md).
 

diff --git a/docs/src/explanations/processing-workload.md b/docs/src/explanations/processing-workload.md
@@ -9,4 +9,4 @@ This means that instance impacts metrics data returned can be understood as: `im
 Why this default sampling period of 15 minutes ?
 
 - It seems sufficient for our current monitoring needs (but maybe we can make it configurable in the future).
-- It seems hard to go below 10 minutes (because default period  of AWS instance metrics is 5 minutes. You need to activate `detailed monitoring` (extra feature) for 1 minute granularity: [List the available CloudWatch metrics for your instances - Amazon Elastic Compute Cloud](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html#ec2-cloudwatch-metrics)).
+- It seems hard to go below 10 minutes (because default period of AWS instance metrics is 5 minutes. You need to activate `detailed monitoring` (extra feature) for 1 minute granularity: [List the available CloudWatch metrics for your instances - Amazon Elastic Compute Cloud](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html#ec2-cloudwatch-metrics)).