You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/aks/cluster-autoscaler.md
+7-10Lines changed: 7 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -224,12 +224,11 @@ The following table lists the available settings for the cluster autoscaler prof
224
224
--cluster-autoscaler-profile ""
225
225
```
226
226
227
-
## Retrieve cluster autoscaler logs, status and metrics
227
+
## Retrieve cluster autoscaler logsand status
228
228
229
229
You can retrieve logs and status updates from the cluster autoscaler to help diagnose and debug autoscaler events. AKS manages the cluster autoscaler on your behalf and runs it in the managed control plane. You can enable control plane node to see the logs and operations from the cluster autoscaler.
230
230
231
231
### [Azure CLI](#tab/azure-cli)
232
-
#### Logs
233
232
1. Set up a rule for resource logs to push cluster autoscaler logs to Log Analytics using the [instructions here][aks-view-master-logs]. Make sure you check the box for `cluster-autoscaler` when selecting options for **Logs**.
234
233
2. Select the **Log** section on your cluster.
235
234
3. Enter the following example query into Log Analytics:
@@ -242,24 +241,20 @@ You can retrieve logs and status updates from the cluster autoscaler to help dia
242
241
As long as there are logs to retrieve, you should see logs similar to the following logs:
243
242
244
243
:::image type="content" source="media/cluster-autoscaler/autoscaler-logs.png" alt-text="Screenshot of Log Analytics logs.":::
245
-
246
-
#### Status
247
-
1. View cluster autoscaler scale-up not triggered events on CLI
244
+
245
+
4. View cluster autoscaler scale-up not triggered events on CLI
248
246
```bash
249
247
kubectl get events --field-selector source=cluster-autoscaler,reason=NotTriggerScaleUp
250
248
```
251
-
2. View cluster autoscaler warning events on CLI
249
+
5. View cluster autoscaler warning events on CLI
252
250
```bash
253
251
kubectl get events --field-selector source=cluster-autoscaler,type=Warning
254
252
```
255
-
3. The cluster autoscaler also writes out the health status to a `configmap` named `cluster-autoscaler-status`. You can retrieve these logs using the following `kubectl` command:
253
+
6. The cluster autoscaler also writes out the health status to a `configmap` named `cluster-autoscaler-status`. You can retrieve these logs using the following `kubectl` command:
256
254
257
255
```bash
258
256
kubectl get configmap -n kube-system cluster-autoscaler-status -o yaml
259
257
```
260
-
#### Metrics
261
-
1. You can enable [control plane metrics (Preview)](./monitor-control-plane-metrics.md) to see the logs and operations from the cluster autoscaler with the [Azure Monitor managed service for Prometheus add-on](../azure-monitor/essentials/prometheus-metrics-overview.md)
262
-
263
258
264
259
### [Azure portal](#tab/azure-portal)
265
260
@@ -274,6 +269,8 @@ You can retrieve logs and status updates from the cluster autoscaler to help dia
274
269
---
275
270
276
271
For more information, see the [Kubernetes/autoscaler GitHub project FAQ][kubernetes-faq].
272
+
## Cluster Autoscaler Metrics
273
+
You can enable [control plane metrics (Preview)](./monitor-control-plane-metrics.md) to see the logs and operations from the [cluster autoscaler](./control-plane-metrics-default-list.md#minimal-ingestion-for-default-off-targets) with the [Azure Monitor managed service for Prometheus add-on](../azure-monitor/essentials/prometheus-metrics-overview.md)
0 commit comments