Integrate GORM Logger with Zerolog and Add Configuration Options for Logging and Performance #2040
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.
This PR integrates the GORM logger with zerolog to detect database-related bottlenecks. With this integration, the log level now follows the level set in zerolog (e.g., debug.level), ensuring consistent and detailed logging for database operations.
To activate database debugging, make sure to set
log.level
todebug
anddatabase.debug
totrue
.Additionally, custom configuration options for GORM have been added. Example configurations can be found in config-example.yaml. The available options include:
Options:
config-example.yaml
1. Log Options:
2. Statement Preparation Option:
These options support existing GORM settings and allow for flexible configuration tailored to different environments and needs.
Summary of Changes
Example
Reference