Skip to content

Commit 3a8ee8c

Browse files
authored
Update java-dynamic-log-level.md
1 parent a7b8779 commit 3a8ee8c

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

articles/container-apps/java-dynamic-log-level.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,11 @@ ms.author: cshoe
1313

1414
Azure Container Apps platform offers a built-in diagnostics tool exclusively for Java developers to help them debug and troubleshoot their Java applications running on Azure Container Apps more easily and efficiently. One of the key features is a dynamic logger level change, which allows you to access log details that are hidden by default. When enabled, log information is collected without code modifications or forcing you to restart your app when changing log levels.
1515

16+
Before getting started, you need to upgrade Azure Container Apps Extension in your Azure CLI to version **0.3.51** or higher to use this functionality.
17+
```azurecli
18+
az extension update --name containerapp
19+
```
20+
1621
## Enable JVM diagnostics for your Java applications
1722

1823
Before using the Java diagnostics tool, you need to first enable Java Virtual Machine (JVM) diagnostics for your Azure Container Apps. This step enables Java diagnostics functionality by injecting an advanced diagnostics agent into your app. Your app might restart during this process.
@@ -46,7 +51,7 @@ The following sample uses the logger name `org.springframework.boot` with the lo
4651
Use the following command to adjust log levels for a specific logger:
4752

4853
```azurecli
49-
az containerapp java logger update \
54+
az containerapp java logger set \
5055
--logger-name "org.springframework.boot" \
5156
--level "info"
5257
--environment <ENVIRONMENT_NAME> \

0 commit comments

Comments
 (0)