Skip to content

Commit 5084381

Browse files
authored
Merge pull request #94284 from MicrosoftDocs/release-ignite-azmon-containerinsights
Ignite
2 parents de608bd + a1a486b commit 5084381

File tree

57 files changed

+1114
-351
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

57 files changed

+1114
-351
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43634,6 +43634,11 @@
4363443634
"source_path": "articles/active-directory/develop/msal-acquire-token-interactively.md",
4363543635
"redirect_url": "/azure/active-directory/develop/msal-acquire-cache-tokens",
4363643636
"redirect_document_id": true
43637+
},
43638+
{
43639+
"source_path": "articles/azure-monitor/insights/container-insights-live-logs.md",
43640+
"redirect_url": "/azure/azure-monitor/insights/container-insights-livedata-overview",
43641+
"redirect_document_id": false
4363743642
}
4363843643
]
4363943644
}

articles/aks/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -227,8 +227,8 @@
227227
href: view-master-logs.md
228228
- name: View the kubelet logs
229229
href: kubelet-logs.md
230-
- name: View real-time container logs (preview)
231-
href: ../azure-monitor/insights/container-insights-live-logs.md
230+
- name: View container data real-time
231+
href: ../azure-monitor/insights/container-insights-livedata-overview.md
232232
maintainContext: true
233233
- name: Use Windows Server containers (preview)
234234
items:

articles/azure-monitor/insights/container-insights-agent-config.md

Lines changed: 22 additions & 158 deletions
Large diffs are not rendered by default.

articles/azure-monitor/insights/container-insights-analyze.md

Lines changed: 28 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,23 @@
11
---
2-
title: Monitor AKS cluster performance with Azure Monitor for containers | Microsoft Docs
2+
title: Monitor Kubernetes cluster performance with Azure Monitor for containers | Microsoft Docs
33
description: This article describes how you can view and analyze the performance and log data with Azure Monitor for containers.
44
ms.service: azure-monitor
55
ms.subservice:
66
ms.topic: conceptual
77
author: mgoedtel
88
ms.author: magoedte
9-
ms.date: 09/17/2019
10-
9+
ms.date: 10/15/2019
1110
---
1211

13-
# Understand AKS cluster performance with Azure Monitor for containers
14-
With Azure Monitor for containers, you can use the performance charts and health status to monitor the workload of your Azure Kubernetes Service (AKS) clusters from two perspectives. You can monitor directly from an AKS cluster, or you can monitor all AKS clusters in a subscription from Azure Monitor. Viewing Azure Container Instances is also possible when you monitor a specific AKS cluster.
12+
# Understand Kubernetes cluster performance with Azure Monitor for containers
13+
14+
With Azure Monitor for containers, you can use the performance charts and health status to monitor the workload of Kubernetes clusters hosted on Azure Kubernetes Service (AKS), Azure Stack, or other environment from two perspectives. You can monitor directly from the cluster, or you can view all clusters in a subscription from Azure Monitor. Viewing Azure Container Instances is also possible when monitoring a specific AKS cluster.
1515

1616
This article helps you understand the two perspectives, and how Azure Monitor helps you quickly assess, investigate, and resolve detected issues.
1717

1818
For information about how to enable Azure Monitor for containers, see [Onboard Azure Monitor for containers](container-insights-onboard.md).
1919

20-
Azure Monitor provides a multi-cluster view that shows the health status of all monitored AKS clusters running Linux and Windows Server 2019 deployed across resource groups in your subscriptions. It shows AKS clusters discovered that aren't monitored by the solution. You can immediately understand cluster health, and from here, you can drill down to the node and controller performance page or navigate to see performance charts for the cluster. For AKS clusters that were discovered and identified as unmonitored, you can enable monitoring for them at any time.
20+
Azure Monitor provides a multi-cluster view that shows the health status of all monitored Kubernetes clusters running Linux and Windows Server 2019 deployed across resource groups in your subscriptions. It shows clusters discovered across all environments that aren't monitored by the solution. You can immediately understand cluster health, and from here, you can drill down to the node and controller performance page or navigate to see performance charts for the cluster. For AKS clusters that were discovered and identified as unmonitored, you can enable monitoring for them at any time.
2121

2222
The main differences in monitoring a Windows Server cluster with Azure Monitor for containers compared to a Linux cluster are the following:
2323

@@ -33,13 +33,24 @@ Sign in to the [Azure portal](https://portal.azure.com).
3333

3434
## Multi-cluster view from Azure Monitor
3535

36-
To view the health status of all AKS clusters deployed, select **Monitor** from the left pane in the Azure portal. Under the **Insights** section, select **Containers**.
36+
To view the health status of all Kubernetes clusters deployed, select **Monitor** from the left pane in the Azure portal. Under the **Insights** section, select **Containers**.
3737

3838
![Azure Monitor multi-cluster dashboard example](./media/container-insights-analyze/azmon-containers-multiview.png)
3939

40+
You can scope the results presented in the grid to show clusters that are:
41+
42+
* **Azure** - AKS and AKS-Engine clusters hosted in Azure Kubernetes Service
43+
* **Azure Stack (Preview)** - AKS-Engine clusters hosted on Azure Stack
44+
* **Non-Azure (Preview)** - Kubernetes clusters hosted on-premises
45+
* **All** - View all the Kubernetes clusters hosted in Azure, Azure Stack, and on-premises environments that are onboarded to Azure Monitor for containers
46+
47+
To view clusters from a specific environment, select it from the **Environments** pill on the top-left corner of the page.
48+
49+
![Environment pill selector example](./media/container-insights-analyze/clusters-multiview-environment-pill.png)
50+
4051
On the **Monitored clusters** tab, you learn the following:
4152

42-
- How many clusters are in a Critical or unhealthy state, versus how many are Healthy or not reporting (referred to as an Unknown state).
53+
- How many clusters are in a critical or unhealthy state, versus how many are healthy or not reporting (referred to as an Unknown state).
4354
- Whether all of the [Azure Kubernetes Engine (AKS-engine)](https://github.com/Azure/aks-engine) deployments are healthy.
4455
- How many nodes and user and system pods are deployed per cluster.
4556
- How much disk space is available and if there's a capacity issue.
@@ -78,18 +89,21 @@ The following table provides a breakdown of the calculation that controls the he
7889
| |Critical |<60% |
7990
| |Unknown |If not reported in last 30 minutes |
8091

81-
From the list of clusters, you can drill down to the **Cluster** page by selecting the name of the cluster. Then go to the **Nodes** performance page by selecting the rollup of nodes in the **Nodes** column for that specific cluster. Or, you can drill down to the **Controllers** performance page by selecting the rollup of the **User pods** or **System pods** column.
92+
From the list of clusters, you can drill down to the **Cluster** page by selecting the name of the cluster. Then go to the **Nodes** performance page by selecting the rollup of nodes in the **Nodes** column for that specific cluster. Or, you can drill down to the **Controllers** performance page by selecting the rollup of the **User pods** or **System pods** column.
8293

83-
## View performance directly from an AKS cluster
94+
## View performance directly from a cluster
8495

85-
Access to Azure Monitor for containers is available directly from an AKS cluster by selecting **Insights** from the left pane. Information about your AKS cluster is organized into four perspectives:
96+
Access to Azure Monitor for containers is available directly from an AKS cluster by selecting **Insights** > **Cluster** from the left pane, or when you selected a cluster from the multi-cluster view. Information about your cluster is organized into four perspectives:
8697

8798
- Cluster
8899
- Nodes
89100
- Controllers
90101
- Containers
91102

92-
The default page opens when you select **Insights** > **Cluster**. Four line performance charts display key performance metrics of your cluster.
103+
>[!NOTE]
104+
>The experience described in the remainder of this article are also applicable for viewing performance and health status of your Kubernetes clusters hosted on Azure Stack or other environment when selected from the multi-cluster view.
105+
106+
The default page opens and displays four line performance charts that show key performance metrics of your cluster.
93107

94108
![Example performance charts on the Cluster tab](./media/container-insights-analyze/containers-cluster-perfview.png)
95109

@@ -132,14 +146,10 @@ You can [split](../platform/metrics-charts.md#apply-splitting-to-a-chart) a metr
132146

133147
When you switch to the **Nodes**, **Controllers**, and **Containers** tabs, a property pane automatically displays on the right side of the page. It shows the properties of the item selected, which includes the labels you defined to organize Kubernetes objects. When a Linux node is selected, the **Local Disk Capacity** section also shows the available disk space and the percentage used for each disk presented to the node. Select the **>>** link in the pane to view or hide the pane.
134148

135-
![Example Kubernetes perspectives properties panes](./media/container-insights-analyze/perspectives-preview-pane-01.png)
136-
137-
As you expand the objects in the hierarchy, the properties pane updates based on the object selected. From the pane, you also can view Kubernetes events with predefined log searches by selecting the **View Kubernetes event logs** link at the top of the pane. For more information about how to view Kubernetes log data, see [Search logs to analyze data](container-insights-log-search.md). While you review cluster resources, you can see container logs and events in real time. For more information about this feature and the configuration required to grant and control access, see [View logs in real time with Azure Monitor for containers](container-insights-live-logs.md).
149+
As you expand the objects in the hierarchy, the properties pane updates based on the object selected. From the pane, you also can view Kubernetes container logs (stdout/stderror), events, and pod metrics by selecting the **View live data (preview)** link at the top of the pane. For more information about the configuration required to grant and control access to view this data, see [Setup the Live Data (preview)](container-insights-livedata-setup.md). While you review cluster resources, you can see this data from the container in real-time. For more information about this feature, see [How to view Kubernetes logs, events, and pod metrics in real time](container-insights-livedata-overview.md). To view Kubernetes log data stored in your workspace based on pre-defined log searches, select **View container logs** from the **View in analytics** drop-down list. For additional information about this topic, see [Search logs to analyze data](container-insights-log-search.md#search-logs-to-analyze-data).
138150

139151
Use the **+ Add Filter** option at the top of the page to filter the results for the view by **Service**, **Node**, **Namespace**, or **Node Pool**. After you select the filter scope, select one of the values shown in the **Select value(s)** field. After the filter is configured, it's 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 specify a filter by **Node**, you can only select **Service** or **Namespace** for the second filter.
140152

141-
![Example using the filter to narrow down results](./media/container-insights-analyze/add-filter-option-01.png)
142-
143153
Specifying a filter in one tab continues to be applied when you select another. It's deleted after you select the **x** symbol next to the specified filter.
144154

145155
Switch to the **Nodes** tab and the row hierarchy follows the Kubernetes object model, which starts with a node in your cluster. Expand the node to view one or more pods running on the node. If more than one container is grouped to a pod, they're displayed as the last row in the hierarchy. You also can view how many non-pod-related workloads are running on the host if the host has processor or memory pressure.
@@ -303,4 +313,5 @@ You access these workbooks by selecting each one from the **View Workbooks** dro
303313
## Next steps
304314

305315
- Review [Create performance alerts with Azure Monitor for containers](container-insights-alerts.md) to learn how to create alerts for high CPU and memory utilization to support your DevOps or operational processes and procedures.
316+
306317
- View [log query examples](container-insights-log-search.md#search-logs-to-analyze-data) to see predefined queries and examples to evaluate or customize to alert, visualize, or analyze your clusters.

articles/azure-monitor/insights/container-insights-enable-existing-clusters.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ provisioningState : Succeeded
4343

4444
If you would rather integrate with an existing workspace, perform the following steps to first identify the full resource ID of your Log Analytics workspace required for the `--workspace-resource-id` parameter, and then run the command to enable the monitoring add-on against the specified workspace.
4545

46-
1. List all the subscriptions which you have access using the following command:
46+
1. List all the subscriptions that you have access to using the following command:
4747

4848
```azurecli
4949
az account list --all -o table
@@ -367,4 +367,6 @@ After a few minutes, the command completes and returns JSON-formatted informatio
367367

368368
* If you experience issues while attempting to onboard the solution, review the [troubleshooting guide](container-insights-troubleshoot.md)
369369

370-
* With monitoring enabled to capture health metrics for both the AKS cluster nodes and pods, these health metrics are available in the Azure portal. To learn how to use Azure Monitor for containers, see [View Azure Kubernetes Service health](container-insights-analyze.md).
370+
* With monitoring enabled to collect health and resource utilization of your AKS cluster and workloads running on them, learn [how to use](container-insights-analyze.md) Azure Monitor for containers.
371+
372+

articles/azure-monitor/insights/container-insights-enable-new-cluster.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -117,4 +117,4 @@ After a few minutes, the command completes and returns JSON-formatted informatio
117117

118118
* If you experience issues while attempting to onboard the solution, review the [troubleshooting guide](container-insights-troubleshoot.md)
119119

120-
* With monitoring enabled to capture health metrics for both the AKS cluster nodes and pods, these health metrics are available in the Azure portal. To learn how to use Azure Monitor for containers, see [View Azure Kubernetes Service health](container-insights-analyze.md).
120+
* With monitoring enabled to collect health and resource utilization of your AKS cluster and workloads running on them, learn [how to use](container-insights-analyze.md) Azure Monitor for containers.

articles/azure-monitor/insights/container-insights-faq.md

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,17 @@ ms.subservice:
66
ms.topic: conceptual
77
author: mgoedtel
88
ms.author: magoedte
9-
ms.date: 08/14/2019
10-
9+
ms.date: 10/15/2019
1110
---
1211

1312
# Azure Monitor for containers Frequently Asked Questions
1413

1514
This Microsoft FAQ is a list of commonly asked questions about Azure Monitor for containers. If you have any additional questions about the solution, go to the [discussion forum](https://feedback.azure.com/forums/34192--general-feedback) and post your questions. When a question is frequently asked, we add it to this article so that it can be found quickly and easily.
1615

16+
## Can I view metrics collected in Grafana?
17+
18+
Azure Monitor for containers supports viewing metrics stored in your Log Analytics workspace in Grafana dashboards. We have provided a template that you can download from Grafana's [dashboard repository](https://grafana.com/grafana/dashboards?dataSource=grafana-azure-monitor-datasource&category=docker) to get you started and reference to help you learn how to query additional data from your monitored clusters to visualize in custom Grafana dashbaords.
19+
1720
## Can I monitor my AKS-engine cluster with Azure Monitor for containers?
1821

1922
Azure Monitor for containers supports monitoring container workloads deployed to AKS-engine (formerly known as ACS-engine) cluster(s) hosted on Azure. For further details and an overview of steps required to enable monitoring for this scenario, see [Using Azure Monitor for containers for AKS-engine](https://github.com/microsoft/OMS-docker/tree/aks-engine).
@@ -68,20 +71,15 @@ For a detailed look at the issue, review the following [GitHub link](https://git
6871

6972
## How do I resolve Azure AD errors when I enable live logs?
7073

71-
You may see the following error: **The reply url specified in the request does not match the reply urls configured for the application: '<application ID\>'**. The solution to solve it can be found in the article [How to view container logs real time with Azure Monitor for containers](container-insights-live-logs.md#configure-aks-with-azure-active-directory).
74+
You may see the following error: **The reply url specified in the request does not match the reply urls configured for the application: '<application ID\>'**. The solution to solve it can be found in the article [How to view container data in real time with Azure Monitor for containers](container-insights-livedata-setup.md#configure-ad-integrated-authentication).
7275

7376
## Why can't I upgrade cluster after onboarding?
7477

7578
If after you enable Azure Monitor for containers for an AKS cluster, you delete the Log Analytics workspace the cluster was sending its data to, when attempting to upgrade the cluster it will fail. To work around this, you will have to disable monitoring and then re-enable it referencing a different valid workspace in your subscription. When you try to perform the cluster upgrade again, it should process and complete successfully.
7679

7780
## Which ports and domains do I need to open/whitelist for the agent?
78-
- *.ods.opinsights.azure.com 443
79-
- *.oms.opinsights.azure.com 443
80-
- *.blob.core.windows.net 443
81-
- dc.services.visualstudio.com 443
82-
- *.microsoftonline.com 443
83-
- *.monitoring.azure.com 443
84-
- login.microsoftonline.com 443
81+
82+
See the [Network firewall requirements](container-insights-onboard.md#network-firewall-requirements) for the proxy and firewall configuration information required for the containerized agent with Azure, Azure US Government, and Azure China clouds.
8583

8684
## Next steps
8785

0 commit comments

Comments
 (0)