Qiao-yq opened a new pull request, #3324:
URL: https://github.com/apache/dubbo-go/pull/3324

   ### Description
   Summary
   Standardize log format across common/ and config/ packages by adding 
consistent component prefixes and adopting structured key-value formatting.
   
   Motivation
   Log messages across the codebase used inconsistent formatting — some with 
component tags, some without, and many using free-form text interpolation. This 
makes log filtering/searching difficult in production environments. This PR 
unifies the log style following the pattern established in 
[#3311](https://github.com/apache/dubbo-go/pull/3311) (cluster logger format).
   
   Changes
   common/ package
   Added [GracefulShutdown], [Trace], [ProxyFactory], [RegistryDir], 
[RPCService] prefixes
   Converted free-form log messages to structured key=value format (e.g., 
name=%s err=%v)
   Fixed missing error variables in log output (e.g., host_util.go was 
discarding err)
   Cleaned up import block grouping
   config/ package
   Added [Config Center], [ConfigLoader], [ConfigResolver], [Consumer], 
[GracefulShutdown], [Metadata Service], [OTel], [Provider], [Reference], 
[Registry], [Service] prefixes
   Unified log levels and message style (lowercase start, no trailing 
punctuation)
   Replaced %#v and %w format verbs with %v for cleaner error output
   Removed unused imports (fmt in provider_config.go)
   Consolidated multi-line log calls into single-line structured format
   
   Fixes #3295 
   
   ### Checklist
   - [x] I confirm the target branch is `develop`
   - [x] Code has passed local testing
   - [x] I have added tests that prove my fix is effective or that my feature 
works
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to