Skip to content

Commit 05ad85b

Browse files
Merge pull request #264755 from bwren/update-container-insights-reports
update container-insights-reports
2 parents 067e0ae + db97385 commit 05ad85b

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/azure-monitor/containers/container-insights-reports.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,10 @@ The **event anomaly** analyzer groups similar events together for easier analysi
3636
### Container optimizer
3737
The **container optimizer** analyzer shows containers with excessive cpu and memory limits and requests. Each tile can represent multiple containers with the same spec. For example, if a deployment creates 100 identical pods each with a container C1 and C2, then there will be a single tile for all C1 containers and a single tile for all C2 containers. Containers with set limits and requests are color-coded in a gradient from green to red.
3838

39+
> [!IMPORTANT]
40+
> This view doesn't include containers in the **kube-system** namespace and doesn't support Windows Server nodes.
41+
>
42+
3943
The number on each tile represents how far the container limits/requests are from the optimal/suggested value. The closer the number is to 0 the better it is. Each tile has a color to indicate the following:
4044

4145
- green: well set limits and requests

0 commit comments

Comments
 (0)