add SUM_MAX_INSTANCES_FETCHED

saagie · Sep 10, 2024 · 6bf9203 · 6bf9203
1 parent e5135dd
commit 6bf9203
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/technologies/app/saagie-usage-monitoring/README.md b/technologies/app/saagie-usage-monitoring/README.md
@@ -18,8 +18,9 @@ To deploy Saagie Usage Monitoring on your platform, you need to create a user wi
   - `SAAGIE_AND_S3` if you want to monitor Saagie and S3 buckets
 - IP_HDFS (Required if MONITORING_OPT=`SAAGIE_AND_DATALAKE`) : Namenode IP
 - AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_S3_ENDPOINT and AWS_REGION_NAME (Required if MONITORING_OPT=`SAAGIE_AND_S3`)
-- SAAGIE_SUM_CRON : Cron to collect Saagie informations on API (Optionnal, Default value : `0 * * * *`)
+- SAAGIE_SUM_CRON : Cron to collect Saagie informations on API (Default value : `0 * * * *`)
 - REQUEST_TIMEOUT : Manage SaagieAPI request timeout (Default value in seconds : `10`)
+- SUM_MAX_INSTANCES_FETCHED : Number of instances recovered, for jobs and pipelines (Default value : `1000`)
 
 For an external Postgres database : 
 - SAAGIE_PG_HOST : Postgresql host (Default value : `localhost`)

diff --git a/technologies/app/saagie-usage-monitoring/saagie-usage-monitoring-2023.05/code/utils.py b/technologies/app/saagie-usage-monitoring/saagie-usage-monitoring-2023.05/code/utils.py
@@ -30,7 +30,7 @@
 timeout = int(os.environ["REQUEST_TIMEOUT"])
 
 # Workaround for platforms with too many instances
-MAX_INSTANCES_FETCHED = os.environ.get("SMT_MAX_INSTANCES_FETCHED", 1000)
+MAX_INSTANCES_FETCHED = os.environ.get("SUM_MAX_INSTANCES_FETCHED", 1000)
 
 
 class SaagieUtils(object):