Skip to content

Typo in new Logs Analytics table name - should be ContainerNetworkLogs #340

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
anders-ove wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Typo in new Logs Analytics table name - should be ContainerNetworkLogs #340

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a57473d
Typo in new Logs Analytics table name - should be ContainerNetworkLogs
anders-ove Nov 26, 2025
a81e506
Update how-to-configure-container-network-logs.md
anders-ove Nov 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions articles/aks/container-network-observability-logs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ ms.date: 11/11/2025
>
> - **CRD**: `RetinaNetworkFlowLogs` → `ContainerNetworkLog`
> - **CLI flag**: `--enable-retinanetworkflowlog` → `--enable-container-network-logs`
> - **Log Analytics table**: `RetinaNetworkFlowLogs` → `ContainerNetworkLog`
> - **Log Analytics table**: `RetinaNetworkFlowLogs` → `ContainerNetworkLogs`
>
> Action items for existing users to enable new naming
>
Expand Down Expand Up @@ -60,7 +60,7 @@ ms.date: 11/11/2025
>
> [!NOTE]
> - Previously collected data stays in your workspace in old table RetinaNetworkFlowLogs.
> - After re-enabling, allow a short delay before new data appears in new table ContainerNetworkLog.
> - After re-enabling, allow a short delay before new data appears in new table ContainerNetworkLogs.

Container network logs in [Advanced Container Networking Services](advanced-container-networking-services-overview.md) for Azure Kubernetes Service (AKS) provide comprehensive, context-rich visibility into every network flow within your cluster. While metrics tell you *what* is happening in your network (such as bandwidth usage or error rates), container network logs tell you *why* by capturing the complete story of each connection—including who initiated it, what protocols were used, and whether the traffic was allowed or blocked.

Expand Down
4 changes: 2 additions & 2 deletions articles/aks/how-to-configure-container-network-logs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ ms.custom: template-how-to-pattern, devx-track-azurecli
>
> - **CRD**: `RetinaNetworkFlowLogs` → `ContainerNetworkLog`
> - **CLI flag**: `--enable-retinanetworkflowlog` → `--enable-container-network-logs`
> - **Log Analytics table**: `RetinaNetworkFlowLogs` → `ContainerNetworkLog`
> - **Log Analytics table**: `RetinaNetworkFlowLogs` → `ContainerNetworkLogs`
>
> Action items for existing users to enable new naming
>
Expand Down Expand Up @@ -61,7 +61,7 @@ ms.custom: template-how-to-pattern, devx-track-azurecli
>
> [!NOTE]
> - Previously collected data stays in your workspace in old table RetinaNetworkFlowLogs.
> - After re-enabling, allow a short delay before new data appears in new table ContainerNetworkLog.
> - After re-enabling, allow a short delay before new data appears in new table ContainerNetworkLogs.

In this article, you complete the steps to configure and use the container network logs feature in Advanced Container Networking Services for Azure Kubernetes Service (AKS). These logs offer persistent network flow monitoring tailored to enhance visibility in containerized environments.

Expand Down