Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add keda_scaled_object_paused to the docs #1249

Merged
merged 11 commits into from
Oct 30, 2023
2 changes: 1 addition & 1 deletion content/docs/2.11/operate/prometheus.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 ScaledObject.
- `keda_scaled_object_errors` - The number of errors that have occurred for each ScaledObejct.
JorTurFer marked this conversation as resolved.
Show resolved Hide resolved
- `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.
Expand Down
1 change: 1 addition & 0 deletions content/docs/2.13/operate/opentelemetry.md
Original file line number Diff line number Diff line change
Expand Up @@ -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). |
geoffrey1330 marked this conversation as resolved.
Show resolved Hide resolved
| `keda.scaled.object.paused` | This metric indicates whether a scaled object is paused (value == 1) or un|paused (value == 0). |
geoffrey1330 marked this conversation as resolved.
Show resolved Hide resolved
| `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. |
Expand Down
1 change: 1 addition & 0 deletions content/docs/2.13/operate/prometheus.md
Original file line number Diff line number Diff line change
Expand Up @@ -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)).
geoffrey1330 marked this conversation as resolved.
Show resolved Hide resolved
- `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.
Expand Down