Skip to content

Commit 0a8475b

Browse files
committed
update docs
1 parent 8584939 commit 0a8475b

File tree

2 files changed

+6
-10
lines changed

2 files changed

+6
-10
lines changed

articles/container-apps/container-console.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,9 @@ ms.author: v-wellsjason
1515

1616
Connecting to a container's console is useful when you want to troubleshoot your application inside a container. Azure Container Apps allows you to connect to a container's console using the Azure portal or Azure CLI.
1717

18+
> [!NOTE]
19+
> Azure Container Apps platform offers [Debug Console](container-debug-console.md) to help you troubleshoot your applications if your applications use distroless image.
20+
1821
## Azure portal
1922

2023
To connect to a container's console in the Azure portal, follow these steps.

articles/container-apps/container-debug-console.md

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -19,21 +19,14 @@ Azure Container Apps platform offers debug console to help you troubleshoot your
1919
- If you only install JRE in the runtime image, there are no JDK troubleshooting tools like jcmd, jstack pre-installed in the image.
2020
- When encounter networking issues, your image do not have debugging utilities to investigate them.
2121

22-
You can connect to debug console using the Azure portal or Azure CLI.
22+
You can connect to debug console using the Azure CLI.
2323

2424

2525
> [!NOTE]
2626
> Debug Console will create a separate container, which will share underlying resource with connected container(If the debug console container already exists when you try to connect to, we will reuse the existing one instead of creating a new one. At most 1 debug console container will be created per replicae). If you do not need to use a existing debug console container any more, please make sure to enter **exit** or use **Ctrl-D** to explicitly exit.
2727
28-
## Azure portal
29-
30-
To connect to a container's debug console in the Azure portal, follow these steps.
31-
32-
1. In the Azure portal, select **Console** in the **Monitoring** menu group from your container app page.
33-
1. Select the revision, replica, and container you want to connect to.
34-
1. Select **Debug** tab, then click the Connect button.
35-
36-
:::image type="content" source="media/observability/debug-console.png" alt-text="Screenshot of Azure Container Apps Debug Console page.":::
28+
> [!NOTE]
29+
> If you encounter input missing in debug console, you can try to use **Ctrl-D** to exit and re-connect to debug console again.
3730
3831
## Azure CLI
3932

0 commit comments

Comments
 (0)