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/monitor-aks-reference.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Monitoring AKS data reference
3
3
description: Important reference material needed when you monitor AKS
4
4
ms.service: container-service
5
5
ms.custom: subject-monitoring
6
-
ms.date: 07/29/2021
6
+
ms.date: 07/18/2022
7
7
ms.topic: reference
8
8
---
9
9
@@ -52,29 +52,29 @@ For reference, see a list of [all resource logs category types supported in Azur
52
52
53
53
| Category | Description |
54
54
|:---|:---|
55
-
| cluster-autoscaler | Understand why the AKS cluster is scaling up or down, which may not be expected. This information is also useful to correlate time intervals where something interesting may have happened in the cluster. |
56
-
| guard | Managed Azure Active Directory and Azure RBAC audits. For managed Azure AD, this includes token in and user info out. For Azure RBAC, this includes access reviews in and out. |
57
55
| kube-apiserver | Logs from the API server. |
58
56
| kube-audit | Audit log data for every audit event including get, list, create, update, delete, patch, and post. |
59
57
| kube-audit-admin | Subset of the kube-audit log category. Significantly reduces the number of logs by excluding the get and list audit events from the log. |
60
58
| kube-controller-manager | Gain deeper visibility of issues that may arise between Kubernetes and the Azure control plane. A typical example is the AKS cluster having a lack of permissions to interact with Azure. |
61
59
| kube-scheduler | Logs from the scheduler. |
60
+
| cluster-autoscaler | Understand why the AKS cluster is scaling up or down, which may not be expected. This information is also useful to correlate time intervals where something interesting may have happened in the cluster. |
61
+
| cloud-controller-manager | Logs from the cloud-node-manager component of the Kubernetes cloud controller manager.|
62
+
| guard | Managed Azure Active Directory and Azure RBAC audits. For managed Azure AD, this includes token in and user info out. For Azure RBAC, this includes access reviews in and out. |
63
+
| csi-azuredisk-controller | Logs from the Azure Disk CSI storage driver. |
64
+
| csi-azurefile-controller | Logs from the Azure Files CSI storage driver. |
65
+
| csi-snapshot-controller | Logs from the Azure CSI driver snapshot controller. |
62
66
| AllMetrics | Includes all platform metrics. Sends these values to Log Analytics workspace where it can be evaluated with other data using log queries. |
63
67
64
68
## Azure Monitor Logs tables
65
69
66
-
This section refers to all of the Azure Monitor Logs tables relevant to AKS and available for query by Log Analytics.
67
-
68
-
70
+
This section refers to all of the Azure Monitor Logs tables relevant to AKS and available for query by Log Analytics.
69
71
70
72
|Resource Type | Notes |
71
73
|-------|-----|
72
74
|[Kubernetes services](/azure/azure-monitor/reference/tables/tables-resourcetype#kubernetes-services)| Follow this link for a list of all tables used by AKS and a description of their structure. |
73
75
74
-
75
76
For a reference of all Azure Monitor Logs / Log Analytics tables, see the [Azure Monitor Log Table Reference](/azure/azure-monitor/reference/tables/tables-resourcetype).
76
77
77
-
78
78
## Activity log
79
79
80
80
The following table lists a few example operations related to AKS that may be created in the [Activity log](../azure-monitor/essentials/activity-log.md). Use the Activity log to track information such as when a cluster is created or had its configuration change. You can either view this information in the portal or create an Activity log alert to be proactively notified when an event occurs.
0 commit comments