@@ -388,6 +388,7 @@ On your application classpath (for example, inside your jar) you can have an `ap
388
388
When running in a new environment, an `application.properties` file can be provided outside of your jar that overrides the `name`.
389
389
For one-off testing, you can launch with a specific command line switch (for example, `java -jar app.jar --name="Spring"`).
390
390
391
+ [[boot-features-external-config-application-json]]
391
392
[TIP]
392
393
====
393
394
The `SPRING_APPLICATION_JSON` properties can be supplied on the command line with an environment variable.
@@ -1627,11 +1628,18 @@ The following example shows potential logging settings in `application.propertie
1627
1628
1628
1629
[source,properties,indent=0,subs="verbatim,quotes,attributes"]
1629
1630
----
1630
- logging.level.root=WARN
1631
- logging.level.org.springframework.web=DEBUG
1632
- logging.level.org.hibernate=ERROR
1631
+ logging.level.root=warn
1632
+ logging.level.org.springframework.web=debug
1633
+ logging.level.org.hibernate=error
1633
1634
----
1634
1635
1636
+ It's also possible to set logging levels using environment variables.
1637
+ For example, `LOGGING_LEVEL_ORG_SPRINGFRAMEWORK_WEB=DEBUG` will set `org.springframework.web` to `DEBUG`.
1638
+
1639
+ NOTE: The above approach will only work for package level logging.
1640
+ Since relaxed binding always converts environment variables to lowercase, it's not possible to configure logging for an individual class in this way.
1641
+ If you need to configure logging for a class, you can use <<boot-features-external-config-application-json, the APPLICATION_JSON>> variable.
1642
+
1635
1643
1636
1644
1637
1645
[[boot-features-custom-log-groups]]
0 commit comments