Skip to content

Commit 2a314ef

Browse files
Update articles/container-apps/java-dynamic-log-level.md
1 parent 139a254 commit 2a314ef

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

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

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,9 @@ az containerapp update --enable-java-agent \
3939

4040
## Change runtime logger levels
4141

42-
After enabling JVM diagnostics, you can change runtime log levels for specific loggers in your running Java app without the need to restart it.
42+
After enabling JVM diagnostics, you can change runtime log levels for specific loggers in your running Java app without the need to restart your application.
43+
44+
The following sample uses the logger name `org.springframework.boot` with the log level `info`. Make sure to change these values to match your own logger name and level.
4345

4446
Use the following command to adjust log levels for a specific logger:
4547

@@ -50,11 +52,6 @@ az containerapp java logger update \
5052
--environment <ENVIRONMENT_NAME> \
5153
--resource-group <RESOURCE_GROUP> \
5254
--name <CONTAINER_APP_NAME>
53-
```
54-
55-
In this sample logger name is `"org.springframework.boot"` and desired log level is `"info"`. Change these to your own logger name and log level to help troubleshoot your Java app.
56-
57-
It may take up to two minutes for the logger level change to take effect. Once complete, you can check the application logs from [log streams](log-streaming.md) or other [log options](log-options.md).
5855
5956
## Supported Java logging frameworks
6057

0 commit comments

Comments
 (0)