From b662e9aaf7e1777723802a03019e01e249c55c46 Mon Sep 17 00:00:00 2001 From: geoffrey1330 Date: Mon, 16 Oct 2023 10:49:29 +0100 Subject: [PATCH 01/10] fixed Merge conflict in content/docs/2.11/operate/prometheus.md Signed-off-by: geoffrey1330 --- content/docs/2.11/operate/prometheus.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/docs/2.11/operate/prometheus.md b/content/docs/2.11/operate/prometheus.md index cc028aaf7..d391a1b01 100644 --- a/content/docs/2.11/operate/prometheus.md +++ b/content/docs/2.11/operate/prometheus.md @@ -16,7 +16,8 @@ The KEDA Operator exposes Prometheus metrics which can be scraped on port `8080` - `keda_scaler_metrics_latency` - The latency of retrieving current metric from each scaler. - `keda_scaler_errors` - The number of errors that have occurred for each scaler. - `keda_scaler_errors_total` - The total number of errors encountered for all scalers. -- `keda_scaled_object_errors` - The number of errors that have occurred for each ScaledObject. +- `keda_scaled_object_errors` - The number of errors that have occurred for each ScaledObejct. +- `keda_scaled_object_pause` - The number of pause scaledObject (using the annotaion detailed [here](https://keda.sh/docs/latest/concepts/scaling-deployments/#pause-autoscaling)) - `keda_resource_totals` - Total number of KEDA custom resources per namespace for each custom resource type (CRD). - `keda_trigger_totals` - Total number of triggers per trigger type. - `keda_internal_scale_loop_latency` - Total deviation (in miliseconds) between the expected execution time and the actual execution time for the scaling loop. This latency could be produced due to accumulated scalers latencies or high load. This is an internal metric. From 0cabb7e2f6cfaf4ae1aec0654a7fa1c181dca8d2 Mon Sep 17 00:00:00 2001 From: Elad Motola Date: Sat, 22 Apr 2023 15:13:10 +0300 Subject: [PATCH 02/10] pr comment Signed-off-by: Elad Motola Signed-off-by: geoffrey1330 --- content/docs/2.11/operate/prometheus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/2.11/operate/prometheus.md b/content/docs/2.11/operate/prometheus.md index d391a1b01..e35ea4b45 100644 --- a/content/docs/2.11/operate/prometheus.md +++ b/content/docs/2.11/operate/prometheus.md @@ -17,7 +17,7 @@ The KEDA Operator exposes Prometheus metrics which can be scraped on port `8080` - `keda_scaler_errors` - The number of errors that have occurred for each scaler. - `keda_scaler_errors_total` - The total number of errors encountered for all scalers. - `keda_scaled_object_errors` - The number of errors that have occurred for each ScaledObejct. -- `keda_scaled_object_pause` - The number of pause scaledObject (using the annotaion detailed [here](https://keda.sh/docs/latest/concepts/scaling-deployments/#pause-autoscaling)) +- `keda_scaled_object_paused` - The number of paused scaledObject (using the annotation detailed [here](https://keda.sh/docs/latest/concepts/scaling-deployments/#pause-autoscaling)) - `keda_resource_totals` - Total number of KEDA custom resources per namespace for each custom resource type (CRD). - `keda_trigger_totals` - Total number of triggers per trigger type. - `keda_internal_scale_loop_latency` - Total deviation (in miliseconds) between the expected execution time and the actual execution time for the scaling loop. This latency could be produced due to accumulated scalers latencies or high load. This is an internal metric. From 7ff6cbb63b8bbd7a975e9479dc77ce20f9d64adb Mon Sep 17 00:00:00 2001 From: geoffrey1330 Date: Mon, 16 Oct 2023 10:57:25 +0100 Subject: [PATCH 03/10] Improved keda_scaled_object_pause details in the docs Signed-off-by: geoffrey1330 --- content/docs/2.11/operate/prometheus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/2.11/operate/prometheus.md b/content/docs/2.11/operate/prometheus.md index e35ea4b45..612e3a9b8 100644 --- a/content/docs/2.11/operate/prometheus.md +++ b/content/docs/2.11/operate/prometheus.md @@ -12,12 +12,12 @@ The KEDA Operator exposes Prometheus metrics which can be scraped on port `8080` - `keda_build_info` - Info metric, with static information about KEDA build like: version, git commit and Golang runtime info. - `keda_scaler_active` - This metric marks whether the particular scaler is active (value == 1) or in-active (value == 0). +- `keda_scaled_object_paused` - The paused ScaledObjects in Prometheus metrics (using the annotation detailed [here](https://keda.sh/docs/latest/concepts/scaling-deployments/#pause-autoscaling)) - `keda_scaler_metrics_value` - The current value for each scaler's metric that would be used by the HPA in computing the target average. - `keda_scaler_metrics_latency` - The latency of retrieving current metric from each scaler. - `keda_scaler_errors` - The number of errors that have occurred for each scaler. - `keda_scaler_errors_total` - The total number of errors encountered for all scalers. - `keda_scaled_object_errors` - The number of errors that have occurred for each ScaledObejct. -- `keda_scaled_object_paused` - The number of paused scaledObject (using the annotation detailed [here](https://keda.sh/docs/latest/concepts/scaling-deployments/#pause-autoscaling)) - `keda_resource_totals` - Total number of KEDA custom resources per namespace for each custom resource type (CRD). - `keda_trigger_totals` - Total number of triggers per trigger type. - `keda_internal_scale_loop_latency` - Total deviation (in miliseconds) between the expected execution time and the actual execution time for the scaling loop. This latency could be produced due to accumulated scalers latencies or high load. This is an internal metric. From 469d43f69daae15b4568af3970fe0e6dc7c78c05 Mon Sep 17 00:00:00 2001 From: geoffrey1330 Date: Mon, 16 Oct 2023 11:21:46 +0100 Subject: [PATCH 04/10] Improved keda_scaled_object_pause details in the docs Signed-off-by: geoffrey1330 --- content/docs/2.11/operate/prometheus.md | 2 +- content/docs/2.13/operate/opentelemetry.md | 1 + content/docs/2.13/operate/prometheus.md | 1 + 3 files changed, 3 insertions(+), 1 deletion(-) diff --git a/content/docs/2.11/operate/prometheus.md b/content/docs/2.11/operate/prometheus.md index 612e3a9b8..e338393db 100644 --- a/content/docs/2.11/operate/prometheus.md +++ b/content/docs/2.11/operate/prometheus.md @@ -12,7 +12,7 @@ The KEDA Operator exposes Prometheus metrics which can be scraped on port `8080` - `keda_build_info` - Info metric, with static information about KEDA build like: version, git commit and Golang runtime info. - `keda_scaler_active` - This metric marks whether the particular scaler is active (value == 1) or in-active (value == 0). -- `keda_scaled_object_paused` - The paused ScaledObjects in Prometheus metrics (using the annotation detailed [here](https://keda.sh/docs/latest/concepts/scaling-deployments/#pause-autoscaling)) +- `keda_scaled_object_paused` - The paused ScaledObjects in Prometheus metrics (using the annotation detailed [here](https://keda.sh/docs/latest/concepts/scaling-deployments/#pause-autoscaling)). - `keda_scaler_metrics_value` - The current value for each scaler's metric that would be used by the HPA in computing the target average. - `keda_scaler_metrics_latency` - The latency of retrieving current metric from each scaler. - `keda_scaler_errors` - The number of errors that have occurred for each scaler. diff --git a/content/docs/2.13/operate/opentelemetry.md b/content/docs/2.13/operate/opentelemetry.md index 5d02babda..68e1ba0c5 100644 --- a/content/docs/2.13/operate/opentelemetry.md +++ b/content/docs/2.13/operate/opentelemetry.md @@ -34,6 +34,7 @@ The following metrics are being gathered: | ------ | ----------- | | `keda.build.info` | Info metric, with static information about KEDA build like: version, git commit and Golang runtime info. | | `keda.scaler.active` | This metric marks whether the particular scaler is active (value == 1) or in|active (value == 0). | +| `keda.scaled.object.paused` | This metric indicates whether a scaled object is paused (value == 1) or un|paused (value == 0). | | `keda.scaler.metrics.value` | The current value for each scaler's metric that would be used by the HPA in computing the target average. | | `keda.scaler.metrics.latency` | The latency of retrieving current metric from each scaler. | | `keda.scaler.errors` | The number of errors that have occurred for each scaler. | diff --git a/content/docs/2.13/operate/prometheus.md b/content/docs/2.13/operate/prometheus.md index 2dbcc1edc..d3e36d976 100644 --- a/content/docs/2.13/operate/prometheus.md +++ b/content/docs/2.13/operate/prometheus.md @@ -12,6 +12,7 @@ The KEDA Operator exposes Prometheus metrics which can be scraped on port `8080` - `keda_build_info` - Info metric, with static information about KEDA build like: version, git commit and Golang runtime info. - `keda_scaler_active` - This metric marks whether the particular scaler is active (value == 1) or in-active (value == 0). +- `keda_scaled_object_paused` - The paused ScaledObjects in Prometheus metrics (using the annotation detailed [here](https://keda.sh/docs/latest/concepts/scaling-deployments/#pause-autoscaling)). - `keda_scaler_metrics_value` - The current value for each scaler's metric that would be used by the HPA in computing the target average. - `keda_scaler_metrics_latency` - The latency of retrieving current metric from each scaler. - `keda_scaler_errors` - The number of errors that have occurred for each scaler. From c1909e8db039e5273873b8865ee33dff3755e042 Mon Sep 17 00:00:00 2001 From: geoffrey1330 Date: Mon, 16 Oct 2023 15:57:46 +0100 Subject: [PATCH 05/10] Improved keda_scaled_object_pause details in the docs Signed-off-by: geoffrey1330 --- content/docs/2.11/operate/prometheus.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/docs/2.11/operate/prometheus.md b/content/docs/2.11/operate/prometheus.md index e338393db..2bb0de3e6 100644 --- a/content/docs/2.11/operate/prometheus.md +++ b/content/docs/2.11/operate/prometheus.md @@ -12,7 +12,6 @@ The KEDA Operator exposes Prometheus metrics which can be scraped on port `8080` - `keda_build_info` - Info metric, with static information about KEDA build like: version, git commit and Golang runtime info. - `keda_scaler_active` - This metric marks whether the particular scaler is active (value == 1) or in-active (value == 0). -- `keda_scaled_object_paused` - The paused ScaledObjects in Prometheus metrics (using the annotation detailed [here](https://keda.sh/docs/latest/concepts/scaling-deployments/#pause-autoscaling)). - `keda_scaler_metrics_value` - The current value for each scaler's metric that would be used by the HPA in computing the target average. - `keda_scaler_metrics_latency` - The latency of retrieving current metric from each scaler. - `keda_scaler_errors` - The number of errors that have occurred for each scaler. From 432c84f9d5d7dc8cbc80e0f30fa2850eb424daa7 Mon Sep 17 00:00:00 2001 From: Geoffrey Israel Date: Mon, 16 Oct 2023 16:14:44 +0100 Subject: [PATCH 06/10] Update content/docs/2.13/operate/opentelemetry.md Co-authored-by: Zbynek Roubalik Signed-off-by: Geoffrey Israel --- content/docs/2.13/operate/opentelemetry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/2.13/operate/opentelemetry.md b/content/docs/2.13/operate/opentelemetry.md index 68e1ba0c5..b0009bd4f 100644 --- a/content/docs/2.13/operate/opentelemetry.md +++ b/content/docs/2.13/operate/opentelemetry.md @@ -34,7 +34,7 @@ The following metrics are being gathered: | ------ | ----------- | | `keda.build.info` | Info metric, with static information about KEDA build like: version, git commit and Golang runtime info. | | `keda.scaler.active` | This metric marks whether the particular scaler is active (value == 1) or in|active (value == 0). | -| `keda.scaled.object.paused` | This metric indicates whether a scaled object is paused (value == 1) or un|paused (value == 0). | +| `keda.scaled.object.paused` | This metric indicates whether a ScaledObject is paused (value == 1) or un-paused (value == 0). | | `keda.scaler.metrics.value` | The current value for each scaler's metric that would be used by the HPA in computing the target average. | | `keda.scaler.metrics.latency` | The latency of retrieving current metric from each scaler. | | `keda.scaler.errors` | The number of errors that have occurred for each scaler. | From 87e8e665c56627b2b8c8b7812b8c6522684b4bc0 Mon Sep 17 00:00:00 2001 From: Geoffrey Israel Date: Mon, 16 Oct 2023 16:14:59 +0100 Subject: [PATCH 07/10] Update content/docs/2.13/operate/prometheus.md Co-authored-by: Zbynek Roubalik Signed-off-by: Geoffrey Israel --- content/docs/2.13/operate/prometheus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/2.13/operate/prometheus.md b/content/docs/2.13/operate/prometheus.md index d3e36d976..65e4799ff 100644 --- a/content/docs/2.13/operate/prometheus.md +++ b/content/docs/2.13/operate/prometheus.md @@ -12,7 +12,7 @@ The KEDA Operator exposes Prometheus metrics which can be scraped on port `8080` - `keda_build_info` - Info metric, with static information about KEDA build like: version, git commit and Golang runtime info. - `keda_scaler_active` - This metric marks whether the particular scaler is active (value == 1) or in-active (value == 0). -- `keda_scaled_object_paused` - The paused ScaledObjects in Prometheus metrics (using the annotation detailed [here](https://keda.sh/docs/latest/concepts/scaling-deployments/#pause-autoscaling)). +- `keda_scaled_object_paused` - This metric indicates whether a ScaledObject is paused (value == 1) or un|paused (value == 0). - `keda_scaler_metrics_value` - The current value for each scaler's metric that would be used by the HPA in computing the target average. - `keda_scaler_metrics_latency` - The latency of retrieving current metric from each scaler. - `keda_scaler_errors` - The number of errors that have occurred for each scaler. From a9cbf295bc3fbaaf0db675c737c043f2b84a1569 Mon Sep 17 00:00:00 2001 From: Geoffrey Israel Date: Mon, 16 Oct 2023 16:15:11 +0100 Subject: [PATCH 08/10] Update content/docs/2.13/operate/opentelemetry.md Co-authored-by: Zbynek Roubalik Signed-off-by: Geoffrey Israel --- content/docs/2.13/operate/opentelemetry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/2.13/operate/opentelemetry.md b/content/docs/2.13/operate/opentelemetry.md index b0009bd4f..12a050b20 100644 --- a/content/docs/2.13/operate/opentelemetry.md +++ b/content/docs/2.13/operate/opentelemetry.md @@ -33,7 +33,7 @@ The following metrics are being gathered: | Metric | Description | | ------ | ----------- | | `keda.build.info` | Info metric, with static information about KEDA build like: version, git commit and Golang runtime info. | -| `keda.scaler.active` | This metric marks whether the particular scaler is active (value == 1) or in|active (value == 0). | +| `keda.scaler.active` | This metric marks whether the particular scaler is active (value == 1) or in-active (value == 0). | | `keda.scaled.object.paused` | This metric indicates whether a ScaledObject is paused (value == 1) or un-paused (value == 0). | | `keda.scaler.metrics.value` | The current value for each scaler's metric that would be used by the HPA in computing the target average. | | `keda.scaler.metrics.latency` | The latency of retrieving current metric from each scaler. | From 6776afb8c90f6e71675c50e8b3bc07affe283a56 Mon Sep 17 00:00:00 2001 From: Jorge Turrado Ferrero Date: Sun, 29 Oct 2023 16:48:21 +0100 Subject: [PATCH 09/10] Apply suggestions from code review Signed-off-by: Jorge Turrado Ferrero --- content/docs/2.11/operate/prometheus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/2.11/operate/prometheus.md b/content/docs/2.11/operate/prometheus.md index 2bb0de3e6..cc028aaf7 100644 --- a/content/docs/2.11/operate/prometheus.md +++ b/content/docs/2.11/operate/prometheus.md @@ -16,7 +16,7 @@ The KEDA Operator exposes Prometheus metrics which can be scraped on port `8080` - `keda_scaler_metrics_latency` - The latency of retrieving current metric from each scaler. - `keda_scaler_errors` - The number of errors that have occurred for each scaler. - `keda_scaler_errors_total` - The total number of errors encountered for all scalers. -- `keda_scaled_object_errors` - The number of errors that have occurred for each ScaledObejct. +- `keda_scaled_object_errors` - The number of errors that have occurred for each ScaledObject. - `keda_resource_totals` - Total number of KEDA custom resources per namespace for each custom resource type (CRD). - `keda_trigger_totals` - Total number of triggers per trigger type. - `keda_internal_scale_loop_latency` - Total deviation (in miliseconds) between the expected execution time and the actual execution time for the scaling loop. This latency could be produced due to accumulated scalers latencies or high load. This is an internal metric. From a0ef1ff3b6bc3cfd4540d67c9710f64b058713dd Mon Sep 17 00:00:00 2001 From: Geoffrey Israel Date: Mon, 30 Oct 2023 11:04:03 +0100 Subject: [PATCH 10/10] Update content/docs/2.13/operate/prometheus.md Co-authored-by: Zbynek Roubalik Signed-off-by: Geoffrey Israel --- content/docs/2.13/operate/prometheus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/2.13/operate/prometheus.md b/content/docs/2.13/operate/prometheus.md index 65e4799ff..a591235d1 100644 --- a/content/docs/2.13/operate/prometheus.md +++ b/content/docs/2.13/operate/prometheus.md @@ -12,7 +12,7 @@ The KEDA Operator exposes Prometheus metrics which can be scraped on port `8080` - `keda_build_info` - Info metric, with static information about KEDA build like: version, git commit and Golang runtime info. - `keda_scaler_active` - This metric marks whether the particular scaler is active (value == 1) or in-active (value == 0). -- `keda_scaled_object_paused` - This metric indicates whether a ScaledObject is paused (value == 1) or un|paused (value == 0). +- `keda_scaled_object_paused` - This metric indicates whether a ScaledObject is paused (value == 1) or un-paused (value == 0). - `keda_scaler_metrics_value` - The current value for each scaler's metric that would be used by the HPA in computing the target average. - `keda_scaler_metrics_latency` - The latency of retrieving current metric from each scaler. - `keda_scaler_errors` - The number of errors that have occurred for each scaler.