Skip to content

Commit 78f25fe

Browse files
authored
Update cluster-autoscaler.md
1 parent d741211 commit 78f25fe

File tree

1 file changed

+10
-6
lines changed

1 file changed

+10
-6
lines changed

articles/aks/cluster-autoscaler.md

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -224,14 +224,14 @@ The following table lists the available settings for the cluster autoscaler prof
224224
--cluster-autoscaler-profile ""
225225
```
226226
227-
## Retrieve cluster autoscaler logs, status updates and metrics
227+
## Retrieve cluster autoscaler logs, status and metrics
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
> [!NOTE]
231231
> You can now enable [cluster autoscaler metrics (Preview)](https://learn.microsoft.com/azure/aks/monitor-control-plane-metrics) with the Azure Monitor managed service for Prometheus add-on during cluster creation or for an existing cluster
232232
233233
### [Azure CLI](#tab/azure-cli)
234-
234+
#### Logs
235235
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**.
236236
2. Select the **Log** section on your cluster.
237237
3. Enter the following example query into Log Analytics:
@@ -244,20 +244,24 @@ You can retrieve logs and status updates from the cluster autoscaler to help dia
244244
As long as there are logs to retrieve, you should see logs similar to the following logs:
245245
246246
:::image type="content" source="media/cluster-autoscaler/autoscaler-logs.png" alt-text="Screenshot of Log Analytics logs.":::
247-
248-
4. View cluster autoscaler scale-up not triggered events on CLI
247+
248+
#### Status
249+
1. View cluster autoscaler scale-up not triggered events on CLI
249250
```bash
250251
kubectl get events --field-selector source=cluster-autoscaler,reason=NotTriggerScaleUp
251252
```
252-
5. View cluster autoscaler warning events on CLI
253+
2. View cluster autoscaler warning events on CLI
253254
```bash
254255
kubectl get events --field-selector source=cluster-autoscaler,type=Warning
255256
```
256-
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:
257+
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:
257258
258259
```bash
259260
kubectl get configmap -n kube-system cluster-autoscaler-status -o yaml
260261
```
262+
#### Metrics
263+
1. You can enable [control plane metrics (Preview)](https://learn.microsoft.com/azure/aks/monitor-control-plane-metrics) to see the logs and operations from the cluster autoscaler with the Azure Monitor managed service for Prometheus add-on
264+
261265
262266
### [Azure portal](#tab/azure-portal)
263267

0 commit comments

Comments
 (0)