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/azure-monitor/insights/container-insights-analyze.md
+26-26Lines changed: 26 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Viewing the performance of your Azure Kubernetes Service (AKS) clusters can be o
22
22
23
23
This article will help you understand the experience between the two perspectives and how to quickly assess, investigate, and resolve issues detected.
24
24
25
-
For information about enabling Azure Monitor for containers, see [Onboard Azure Monitor for containers](monitoring-container-insights-onboard.md).
25
+
For information about enabling Azure Monitor for containers, see [Onboard Azure Monitor for containers](container-insights-onboard.md).
26
26
27
27
Azure Monitor provides a multi-cluster view showing the health status of all monitored AKS clusters deployed across resource groups in your subscriptions, and AKS clusters not monitored by the solution. Immediately, you can understand cluster health and from here you can drill down to the node and controller performance page, or you can navigate to the see the performance charts for the cluster. For AKS clusters discovered and identified as unmonitored, you can chose to enable monitoring for that cluster at any time.
28
28
@@ -32,7 +32,7 @@ Sign in to the [Azure portal](https://portal.azure.com).
32
32
## Multi-cluster view from Azure Monitor
33
33
To view the health status of all AKS clusters deployed, select **Monitor** from the left-hand pane in the Azure portal. Under the **Insights** section select **Containers (preview)**.
On the **Monitored clusters** tab, you are able to learn the following:
38
38
@@ -80,7 +80,7 @@ Access to Azure Monitor for containers is available directly from an AKS cluster
80
80
81
81
The default page opened when you click on **Insights (preview)** is **Cluster**, and it includes four line performance charts displaying key performance metrics of your cluster.
82
82
83
-
83
+
84
84
85
85
The performance chart displays four performance metrics:
86
86
@@ -91,35 +91,35 @@ The performance chart displays four performance metrics:
91
91
92
92
When you switch to **Nodes**, **Controllers**, and **Containers** tab, automatically displayed on the right-side of the page is the property pane. It shows the properties of the item selected, including labels you define to organize Kubernetes objects. Click on the **>>** link in the pane to view\hide the pane.
As you expand the objects in the hierarchy, the properties pane updates based on the object selected. From the pane you can also view Kubernetes events with pre-defined log searches by clicking on the **View Kubernetes event logs** link at the top of the pane. For additional information about viewing Kubernetes log data, see [Search logs to analyze data](#search-logs-to-analyze-data).
97
97
98
98
Use the **+ Add Filter** option from the top of the page to filter the results for the view by **Service**, **Node**, or **Namespace** and after selecting the filter scope, you then select the from one of the values shown in the **Select value(s)** field. After the filter is configured it is applied globally while viewing any perspective of the AKS cluster. The formula only supports the equal sign. You can add additional filters on top of the first one to further narrow your results. For example, if you specified a filter by **Node**, your second filter would only allow you to select **Service** or **Namespace**.
99
99
100
-
100
+
101
101
102
102
Specifying a filter in one tab continues to be applied when you select another and it is deleted after you click the **x** symbol next to the specified filter.
103
103
104
104
Switch to the **Nodes** tab and the row hierarchy follows the Kubernetes object model, starting with a node in your cluster. Expand the node and you can view one or more pods running on the node. If more than one container is grouped to a pod, they are displayed as the last row in the hierarchy. You can also view how many non-pod related workloads are running on the host if the host has processor or memory pressure.
105
105
106
-
106
+
107
107
108
108
From an expanded node, you can drill-down from the pod or container running on the node to the controller to view performance data filtered for that controller. Click on the value under the **Controller** column for the specific node.
109
109
110
-
110
+
111
111
112
112
You can select controllers or containers at the top of the page and review the status and resource utilization for those objects. If instead you want to review memory utilization, in the **Metric** drop-down list, select **Memory RSS** or **Memory working set**. **Memory RSS** is supported only for Kubernetes version 1.8 and later. Otherwise, you view values for **Min %** as *NaN %*, which is a numeric data type value that represents an undefined or unrepresentable value.
By default, Performance data is based on the last six hours, but you can change the window by using the **TimeRange** option at the upper left. You can also filter the results within the time range by selecting **Avg**, **Min**, **Max**, **50th**, **90th**, and **95th** in the percentile selector.
117
117
118
-
118
+
119
119
120
120
In the following example, note for node *aks-nodepool1-*, the value for **Containers** is 14, which is a roll-up of the total number of containers deployed.
121
121
122
-
122
+
123
123
124
124
It can help you quickly identify whether you have a proper balance of containers between nodes in your cluster.
125
125
@@ -138,15 +138,15 @@ The information that's presented when you view Nodes is described in the followi
The row hierarchy starts with a controller and when you expand a controller, you view one or more pods. Expand pod, and the last row displays the container grouped to the pod. From an expanded controller, you can drill-down to the node it is running on to view performance data filtered for that node. Click on the value under the **Node** column for the specific controller.
148
148
149
-
149
+
150
150
151
151
The information that's displayed when you view controllers is described in the following table:
152
152
@@ -166,24 +166,24 @@ The icons in the status field indicate the online status of the containers:
166
166
167
167
| Icon | Status |
168
168
|--------|-------------|
169
-
|| Running (Ready)|
170
-
|| Waiting or Paused|
171
-
|| Last reported running but hasn't responded more than 30 minutes|
172
-
|| Successfully stopped or failed to stop|
169
+
|| Running (Ready)|
170
+
|| Waiting or Paused|
171
+
|| Last reported running but hasn't responded more than 30 minutes|
172
+
|| Successfully stopped or failed to stop|
173
173
174
174
The status icon displays a count based on what the pod provides. It shows the worst two states, and when you hover over the status, it displays a roll-up status from all pods in the container. If there isn't a ready state, the status value displays **(0)**.
From a container, you can drill-down to a pod or node to view performance data filtered for that object. Click on the value under the **Pod** or **Node** column for the specific container.
185
185
186
-
186
+
187
187
188
188
The information that's displayed when you view containers is described in the following table:
189
189
@@ -203,11 +203,11 @@ The icons in the status field indicate the online statuses of pods, as described
203
203
204
204
| Icon | Status |
205
205
|--------|-------------|
206
-
|| Running (Ready)|
207
-
|| Waiting or Paused|
208
-
|| Last reported running but hasn't responded in more than 30 minutes|
209
-
|| Successfully stopped or failed to stop|
210
-
|| Failed state |
206
+
|| Running (Ready)|
207
+
|| Waiting or Paused|
208
+
|| Last reported running but hasn't responded in more than 30 minutes|
209
+
|| Successfully stopped or failed to stop|
210
+
|| Failed state |
211
211
212
212
## Container data-collection details
213
213
Container Insights collects various performance metrics and log data from container hosts and containers. Data is collected every three minutes.
@@ -237,7 +237,7 @@ Log Analytics can help you look for trends, diagnose bottlenecks, forecast, or c
237
237
238
238
You can perform interactive analysis of data in the workspace by selecting the **View Kubernetes event logs** or **View container logs** option in the preview pane. The **Log Search** page appears to the right of the Azure portal page that you were on.
239
239
240
-
240
+
241
241
242
242
The container logs output that's forwarded to Log Analytics are STDOUT and STDERR. Because Azure Monitor is monitoring Azure-managed Kubernetes (AKS), Kube-system is not collected today because of the large volume of generated data.
0 commit comments