Fix log level configuration not applied early enough to capture startup messages #6964
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…up messages Apply log level configuration at application startup to ensure early initialization messages are captured. Previously, the log level was only applied via a scheduled job, which ran too late to capture messages from classes like AbstractSqlRegistryStorage during database initialization. Added a startup observer method that applies the initial log level configuration when the application starts, while maintaining the scheduled job for dynamic runtime updates. Also adjusted some log levels in DynamicConfigSource to reduce noise (trace instead of debug) and improve signal (warn instead of debug when storage is not present). Fixes #6963
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
@Observes StartupEventDynamicConfigSourceto reduce noise and improve signalProblem
Early initialization log messages (such as those in
AbstractSqlRegistryStorage.initialize()) were not showing up in the console output because the configured log level was only applied via a scheduled job that ran too late.Solution
Added a startup observer method to
DynamicLogConfigurationServicethat applies the initial log level configuration when the application starts. This ensures the configured log level is applied early enough to capture all initialization and startup log messages.Test plan
apicurio.log.level=INFOenvironment variable setAbstractSqlRegistryStorageappear in console outputFixes #6963