From d0398f695adbf273c6c24faf8bf55bb0cd7f6417 Mon Sep 17 00:00:00 2001 From: Jorge Turrado Date: Mon, 25 Jul 2022 23:35:02 +0200 Subject: [PATCH] feat: Introduce activationThreshold/minMetricValue for MySQL Scaler Signed-off-by: Jorge Turrado --- content/docs/2.8/scalers/mysql.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/docs/2.8/scalers/mysql.md b/content/docs/2.8/scalers/mysql.md index 8395efa84..d323b57f7 100644 --- a/content/docs/2.8/scalers/mysql.md +++ b/content/docs/2.8/scalers/mysql.md @@ -15,6 +15,7 @@ The trigger always requires the following information: - `query` - A MySQL query that should return single numeric value. - `queryValue` - A threshold that is used as `targetValue` or `targetAverageValue` (depending on the trigger metric type) in HPA. (This value can be a float) +- `activationQueryValue` - Target value for activating the scaler. Learn more about activation [here](./../concepts/scaling-deployments.md#activating-and-scaling-thresholds).(Default: `0`, Optional, This value can be a float) To provide information about how to connect to MySQL you can provide: @@ -87,6 +88,7 @@ spec: - type: mysql metadata: queryValue: "4.4" + activationQueryValue: "5.4" query: "SELECT CEIL(COUNT(*) / 6) FROM task_instance WHERE state='running' OR state='queued'" authenticationRef: name: keda-trigger-auth-mysql-secret