Skip to content

Commit 252fd6e

Browse files
authored
Update cluster-autoscaler.md
1 parent bf6835d commit 252fd6e

File tree

1 file changed

+7
-10
lines changed

1 file changed

+7
-10
lines changed

articles/aks/cluster-autoscaler.md

Lines changed: 7 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -224,12 +224,11 @@ The following table lists the available settings for the cluster autoscaler prof
224224
--cluster-autoscaler-profile ""
225225
```
226226
227-
## Retrieve cluster autoscaler logs, status and metrics
227+
## Retrieve cluster autoscaler logs and status
228228
229229
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.
230230
231231
### [Azure CLI](#tab/azure-cli)
232-
#### Logs
233232
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**.
234233
2. Select the **Log** section on your cluster.
235234
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
242241
As long as there are logs to retrieve, you should see logs similar to the following logs:
243242
244243
:::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
248246
```bash
249247
kubectl get events --field-selector source=cluster-autoscaler,reason=NotTriggerScaleUp
250248
```
251-
2. View cluster autoscaler warning events on CLI
249+
5. View cluster autoscaler warning events on CLI
252250
```bash
253251
kubectl get events --field-selector source=cluster-autoscaler,type=Warning
254252
```
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:
256254
257255
```bash
258256
kubectl get configmap -n kube-system cluster-autoscaler-status -o yaml
259257
```
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-
263258
264259
### [Azure portal](#tab/azure-portal)
265260
@@ -274,6 +269,8 @@ You can retrieve logs and status updates from the cluster autoscaler to help dia
274269
---
275270
276271
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)
277274
278275
## Next steps
279276

0 commit comments

Comments
 (0)