@@ -370,6 +370,7 @@ On your application classpath (for example, inside your jar) you can have an `ap
370
370
When running in a new environment, an `application.properties` file can be provided outside of your jar that overrides the `name`.
371
371
For one-off testing, you can launch with a specific command line switch (for example, `java -jar app.jar --name="Spring"`).
372
372
373
+ [[boot-features-external-config-application-json]]
373
374
[TIP]
374
375
====
375
376
The `SPRING_APPLICATION_JSON` properties can be supplied on the command line with an environment variable.
@@ -1513,11 +1514,18 @@ The following example shows potential logging settings in `application.propertie
1513
1514
1514
1515
[source,properties,indent=0,subs="verbatim,quotes,attributes"]
1515
1516
----
1516
- logging.level.root=WARN
1517
- logging.level.org.springframework.web=DEBUG
1518
- logging.level.org.hibernate=ERROR
1517
+ logging.level.root=warn
1518
+ logging.level.org.springframework.web=debug
1519
+ logging.level.org.hibernate=error
1519
1520
----
1520
1521
1522
+ It's also possible to set logging levels using environment variables.
1523
+ For example, `LOGGING_LEVEL_ORG_SPRINGFRAMEWORK_WEB=DEBUG` will set `org.springframework.web` to `DEBUG`.
1524
+
1525
+ NOTE: The above approach will only work for package level logging.
1526
+ Since relaxed binding always converts environment variables to lowercase, it's not possible to configure logging for an individual class in this way.
1527
+ If you need to configure logging for a class, you can use <<boot-features-external-config-application-json, the APPLICATION_JSON>> variable.
1528
+
1521
1529
1522
1530
1523
1531
[[boot-features-custom-log-groups]]
0 commit comments