doc: expose keda_scaler_active Prometheus metric (#1045)

kedacore · Jan 17, 2023 · 276f692 · 276f692
1 parent 2e57a50
commit 276f692
Showing 1 changed file with 4 additions and 3 deletions.
diff --git a/content/docs/2.10/operate/prometheus.md b/content/docs/2.10/operate/prometheus.md
@@ -10,11 +10,12 @@ weight = 100
 
 The KEDA Operator exposes Prometheus metrics which can be scraped on port `8080` at `/metrics`. The following metrics are being gathered:
 
-- `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_activity` - This metric marks whether the particular scaler is active (value == 1) or in-active (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.
 - `keda_scaler_error_totals` - 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 ScaledObejct.
 - `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.
 - Metrics exposed by the `Operator SDK` framework as explained [here](https://sdk.operatorframework.io/docs/building-operators/golang/advanced-topics/#metrics).