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/containers/container-insights-overview.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,18 +27,18 @@ Monitoring your containers is critical, especially when you're running a product
27
27
Container insights gives you performance visibility by collecting memory and processor metrics from controllers, nodes, and containers that are available in Kubernetes through the Metrics API. After you enable monitoring from Kubernetes clusters, metrics and Container logs are automatically collected for you through a containerized version of the Log Analytics agent for Linux. Metrics are sent to the [metrics database in Azure Monitor](../essentials/data-platform-metrics.md). Log data is sent to your [Log Analytics workspace](../logs/log-analytics-workspace-overview.md).
28
28
29
29
:::image type="content" source="media/container-insights-overview/azmon-containers-architecture-01.png" lightbox="media/container-insights-overview/azmon-containers-architecture-01.png" alt-text="Overview diagram of Container insights" border="false":::
30
-
health of your Kubernetes cluster and container workloads. You can:
30
+
31
+
32
+
## Features of Container insights
33
+
34
+
Container insights deliver a comprehensive monitoring experience to understand the performance and health of your Kubernetes cluster and container workloads. You can:
31
35
32
36
- Identify resource bottlenecks by identifying AKS containers running on the node and their average processor and memory utilization.
33
37
- Identify processor and memory utilization of container groups and their containers hosted in Azure Container Instances.
34
38
- View the controller's or pod's overall performance by identifying where the container resides in a controller or a pod.
35
39
- Review the resource utilization of workloads running on the host that are unrelated to the standard processes that support the pod.
36
40
- Identify capacity needs and determine the maximum load that the cluster can sustain by understanding the behavior of the cluster under average and heaviest loads.
37
-
- Configure alerts to proactively notify you or record when CPU and memory utilization on n
38
-
39
-
## Features of Container insights
40
-
41
-
Container insights deliver a comprehensive monitoring experience to understand the performance andodes or containers exceed your thresholds, or when a health state change occurs in the cluster at the infrastructure or nodes health rollup.
41
+
- Configure alerts to proactively notify you or record when CPU and memory utilization on nodes or containers exceed your thresholds, or when a health state change occurs in the cluster at the infrastructure or nodes health rollup.
42
42
- Integrate with [Prometheus](https://prometheus.io/docs/introduction/overview/) to view application and workload metrics it collects from nodes and Kubernetes by using [queries](container-insights-log-query.md) to create custom alerts and dashboards and perform detailed analysis.
43
43
- Monitor container workloads [deployed to AKS Engine](https://github.com/Azure/aks-engine) on-premises and [AKS Engine on Azure Stack](/azure-stack/user/azure-stack-kubernetes-aks-engine-overview).
44
44
- Monitor container workloads [deployed to Azure Arc-enabled Kubernetes](../../azure-arc/kubernetes/overview.md).
:::image type="content" source="./media/containers/containers-diagram.png" alt-text="Diagram that shows the relationships between Azure Monitor and container hosts and agents located on Azure cloud, other clouds, and a local network." lightbox="media/containers/containers-diagram.png" border="false":::
40
40
41
41
## System requirements and supported platforms
42
42
@@ -104,10 +104,10 @@ Use the following information to install and configure the solution.
104
104
- If you have a Red Hat OpenShift environment, review Configure a Log Analytics agent for Red Hat OpenShift.
105
105
- If you have a Kubernetes cluster using the Azure Container Service:
106
106
- Review [Configure a Log Analytics Linux agent for Kubernetes](#configure-a-log-analytics-linux-agent-for-kubernetes).
107
-
- Review [Configure an Log Analytics Windows agent for Kubernetes](#configure-a-log-analytics-windows-agent-for-kubernetes).
107
+
- Review [Configure a Log Analytics Windows agent for Kubernetes](#configure-a-log-analytics-windows-agent-for-kubernetes).
108
108
- Review Use Helm to deploy Log Analytics agent on Linux Kubernetes.
109
109
- If you have an Azure Container Service DC/OS cluster, learn more at [Monitor an Azure Container Service DC/OS cluster with Azure Monitor](/previous-versions/azure/container-service/dcos-swarm/container-service-monitoring-oms).
110
-
- If you have a Docker Swarm mode environment, learn more at Configure an Log Analytics agent for Docker Swarm.
110
+
- If you have a Docker Swarm mode environment, learn more at Configure a Log Analytics agent for Docker Swarm.
111
111
- If you have a Service Fabric cluster, learn more at [Monitor containers with Azure Monitor](../../service-fabric/service-fabric-diagnostics-oms-containers.md).
112
112
113
113
Review the [Docker Engine on Windows](/virtualization/windowscontainers/manage-docker/configure-docker-daemon) article for additional information about how to install and configure your Docker Engines on computers running Windows.
@@ -551,7 +551,7 @@ Labels appended to *PodLabel* data types are your own custom labels. The appende
551
551
## Monitor containers
552
552
After you have the solution enabled in the Azure portal, the **Containers** tile shows summary information about your container hosts and the containers running in hosts.
:::image type="content" source="./media/containers/containers-title.png" alt-text="Screenshot that shows the Containers tile, which includes summary information about containers presented as a pie chart." border="false" lightbox="media/containers/containers-title.png":::
555
555
556
556
The tile shows an overview of how many containers you have in the environment and whether they're failed, running, or stopped.
557
557
@@ -575,15 +575,15 @@ Each area of the dashboard is a visual representation of a search that is run on
575
575
576
576
:::image type="content" source="./media/containers/containers-dash01.png" alt-text="Screenshot that shows a dashboard to view the collected data." lightbox="media/containers/containers-dash01.png" border="false":::
:::image type="content" source="./media/containers/containers-dash02.png" alt-text="Screenshot that shows a dashboard to view the collected data, which includes the status, process, performance, and images inventory of containers." lightbox="media/containers/containers-dash02.png" border="false":::
579
579
580
580
In the **Container Status** area, click the top area, as shown below.
:::image type="content" source="./media/containers/containers-status.png" alt-text="Screenshot that shows the Container Status area of the Containers dashboard, which includes container status information presented as a pie chart." lightbox="media/containers/containers-status.png" border="false":::
583
583
584
584
Log Analytics opens, displaying information about the state of your containers.
585
585
586
-
:::image type="content" source="./media/containers/containers-log-search.png" alt-text="Log Analytics for containers" border="false" lightbox="media/containers/containers-log-search.png":::
586
+
:::image type="content" source="./media/containers/containers-log-search.png" alt-text="Screenshot that shows Log Analytics with a query for the state of containers and the search results." border="false" lightbox="media/containers/containers-log-search.png":::
587
587
588
588
From here, you can edit the search query to modify it to find the specific information you're interested in. For more information about log queries, see [Log queries in Azure Monitor](../logs/log-query-overview.md).
589
589
@@ -594,15 +594,15 @@ Log Analytics marks a container as **Failed** if it has exited with a non-zero e
:::image type="content" source="./media/containers/containers-status.png" alt-text="Screenshot that shows the Container Status area of the Containers dashboard, which includes container status information presented as a pie chart." border="false" lightbox="media/containers/containers-status.png":::
598
598
2. Log Analytics opens and displays the state of your containers, similar to the following.
:::image type="content" source="./media/containers/containers-log-search.png" alt-text="Screenshot that shows Log Analytics with a query for the state of containers and the search results." border="false" lightbox="media/containers/containers-log-search.png":::
600
600
3. Expand the Failed line and click + to add its criteria to the query. Then comment out the Summarize line in the query.
601
601
:::image type="content" source="./media/containers/containers-state-failed-select.png" alt-text="Screenshot that shows the line that should be commented out." border="false" lightbox="media/containers/containers-state-failed-select.png":::
602
602
1. Run the query and then expand a line in the results to view the image ID.
603
603
:::image type="content" source="./media/containers/containers-state-failed.png" alt-text="Screenshot that shows how to view the image ID." border="false" lightbox="media/containers/containers-state-failed.png":::
604
604
1. Type the following in the log query. `ContainerImageInventory | where ImageID == <ImageID>` to see details about the image such as image size and number of stopped and failed images.
:::image type="content" source="./media/containers/containers-failed04.png" alt-text="Screenshot that shows Log Analytics with a query for a container image and details about the image." border="false" lightbox="media/containers/containers-failed04.png":::
606
606
607
607
## Query logs for container data
608
608
@@ -620,15 +620,15 @@ When you're troubleshooting a specific error, it can help to see where it is occ
620
620
### To query logs for container data
621
621
622
622
* Choose an image that you know has failed recently and find the error logs for it. Start by finding a container name that is running that image with a **ContainerInventory** search. For example, search for `ContainerInventory | where Image == "ubuntu" and ContainerState == "Failed"`
623
-
:::image type="content" source="./media/containers/search-ubuntu.png" alt-text="Search for Ubuntu containers" lightbox="media/containers/search-ubuntu.png" border="false":::
623
+
:::image type="content" source="./media/containers/search-ubuntu.png" alt-text="Screenshot that shows a search for failed Ubuntu containers and the search results." lightbox="media/containers/search-ubuntu.png" border="false":::
624
624
625
625
Expand any row in the results to view details for that container.
626
626
627
627
## Example log queries
628
628
629
629
It's often useful to build queries starting with an example or two and then modifying them to fit your environment. As a starting point, you can experiment with the **SAMPLE QUERIES** area on the far right of the solution page, to help you build more advanced queries.
:::image type="content" source="./media/containers/containers-queries.png" alt-text="Screenshot that shows the Sample Queries area with example log queries." border="false" lightbox="media/containers/containers-queries.png":::
0 commit comments