From 79d6a4153e0b10ffbd6112b270a940bc662ca678 Mon Sep 17 00:00:00 2001 From: Amin Jamali Date: Thu, 9 May 2024 13:46:12 +0000 Subject: [PATCH] Add ability for setting app_stats Context: cloudfoundry/uptimer#115 After adding this new measurement, our CI is failing this measurement because the default value of 0 is too aggresssive for cf-deployment. This PR adds the ablity to set app_stats when needed. --- bosh-deploy-with-created-release/task.yml | 5 +++++ bosh-deploy-with-updated-release-submodule/task.yml | 5 +++++ bosh-deploy/task.yml | 5 +++++ shared-functions | 2 ++ 4 files changed, 17 insertions(+) diff --git a/bosh-deploy-with-created-release/task.yml b/bosh-deploy-with-created-release/task.yml index 621d6387..2950f093 100644 --- a/bosh-deploy-with-created-release/task.yml +++ b/bosh-deploy-with-created-release/task.yml @@ -122,6 +122,11 @@ params: # - This sets the maximum number of allowed uptimer failures for app pushability # - The default threshold value of 0 is our working value for cf-deployment, and is likely to be updated + APP_STATS_THRESHOLD: 0 + # - Optional + # - This sets the maximum number of allowed uptimer failures for app stats + # - The default threshold value of 0 is our working value for cf-deployment, and is likely to be updated + HTTP_AVAILABILITY_THRESHOLD: 0 # - Optional # - This sets the maximum number of allowed uptimer failures for http availability diff --git a/bosh-deploy-with-updated-release-submodule/task.yml b/bosh-deploy-with-updated-release-submodule/task.yml index a65079f1..3d84ad95 100644 --- a/bosh-deploy-with-updated-release-submodule/task.yml +++ b/bosh-deploy-with-updated-release-submodule/task.yml @@ -111,6 +111,11 @@ params: # - This sets the maximum number of allowed uptimer failures for app pushability # - The default threshold value of 0 is our working value for cf-deployment, and is likely to be updated + APP_STATS_THRESHOLD: 0 + # - Optional + # - This sets the maximum number of allowed uptimer failures for app stats + # - The default threshold value of 0 is our working value for cf-deployment, and is likely to be updated + HTTP_AVAILABILITY_THRESHOLD: 0 # - Optional # - This sets the maximum number of allowed uptimer failures for http availability diff --git a/bosh-deploy/task.yml b/bosh-deploy/task.yml index 576407fc..dc13a1c0 100644 --- a/bosh-deploy/task.yml +++ b/bosh-deploy/task.yml @@ -110,6 +110,11 @@ params: # - This sets the maximum number of allowed uptimer failures for app pushability # - The default threshold value of 0 is our working value for cf-deployment, and is likely to be updated + APP_STATS_THRESHOLD: 0 + # - Optional + # - This sets the maximum number of allowed uptimer failures for app stats + # - The default threshold value of 0 is our working value for cf-deployment, and is likely to be updated + HTTP_AVAILABILITY_THRESHOLD: 0 # - Optional # - This sets the maximum number of allowed uptimer failures for http availability diff --git a/shared-functions b/shared-functions index 5e990442..53533687 100644 --- a/shared-functions +++ b/shared-functions @@ -210,6 +210,7 @@ write_uptimer_deploy_config() { --arg tcp_port ${tcp_port} \ --arg available_port ${available_port} \ --arg app_pushability ${APP_PUSHABILITY_THRESHOLD} \ + --arg app_stats ${APP_STATS_THRESHOLD} \ --arg http_availability ${HTTP_AVAILABILITY_THRESHOLD} \ --arg tcp_availability ${TCP_AVAILABILITY_THRESHOLD} \ --arg recent_logs ${RECENT_LOGS_THRESHOLD} \ @@ -234,6 +235,7 @@ write_uptimer_deploy_config() { }, "allowed_failures": { "app_pushability": $app_pushability | tonumber, + "app_stats": $app_stats | tonumber, "http_availability": $http_availability | tonumber, "tcp_availability": $tcp_availability | tonumber, "recent_logs": $recent_logs | tonumber,