You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/container-apps/java-dynamic-log-level.md
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,9 @@ az containerapp update --enable-java-agent \
39
39
40
40
## Change runtime logger levels
41
41
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.
43
45
44
46
Use the following command to adjust log levels for a specific logger:
45
47
@@ -50,11 +52,6 @@ az containerapp java logger update \
50
52
--environment <ENVIRONMENT_NAME> \
51
53
--resource-group <RESOURCE_GROUP> \
52
54
--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).
0 commit comments