Skip to content

fix: typo: Possible typo in documentation: ‘loggin’ should be ‘logging’” #1728

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
VedantMadane wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix: typo: Possible typo in documentation: ‘loggin’ should be ‘logging’” #1728

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
895b09b
fix: typo: Possible typo in documentation: ‘loggin’ should be ‘logging’”
VedantMadane Aug 24, 2026
9937b66
chore: remove accidental COMMITMSG from PR
VedantMadane Aug 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/modules/ROOT/pages/spring-cloud-commons/application-context-services.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,13 +144,13 @@ activate profiles using `spring.profiles.active`. After the main application co
will be called a second time, this time with any active profiles allowing `PropertySourceLocators` to locate
any additional `PropertySources` with profiles.

[[logging-configuration]]
[[loggingg-configuration]]
== Logging Configuration

If you use Spring Boot to configure log settings, you should place this configuration in `bootstrap.[yml | properties]` if you would like it to apply to all events.

NOTE: For Spring Cloud to initialize logging configuration properly, you cannot use a custom prefix.
For example, using `custom.logging.logpath` is not recognized by Spring Cloud when initializing the logging system.
NOTE: For Spring Cloud to initialize loggingg configuration properly, you cannot use a custom prefix.
For example, using `custom.loggingg.logpath` is not recognized by Spring Cloud when initializing the loggingg system.

[[environment-changes]]
== Environment Changes
Expand All @@ -159,7 +159,7 @@ The application listens for an `EnvironmentChangeEvent` and reacts to the change
When an `EnvironmentChangeEvent` is observed, it has a list of key values that have changed, and the application uses those to:

* Re-bind any `@ConfigurationProperties` beans in the context.
* Set the logger levels for any properties in `logging.level.*`.
* Set the logger levels for any properties in `loggingg.level.*`.

Note that the Spring Cloud Config Client does not, by default, poll for changes in the `Environment`.
Generally, we would not recommend that approach for detecting changes (although you can set it up with a
Expand Down