-
Notifications
You must be signed in to change notification settings - Fork 5
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.
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
feature: add use_local_time_encoder and show_caller config #59
base: master
Are you sure you want to change the base?
Changes from all commits
ecfe574
6d265f2
583814d
2583ed9
07267aa
bb8c385
29bc270
0e06e7a
c1430a7
1305a3f
5c738a0
cf91fbf
9b65581
25d29ba
48d6db1
d8a4101
e322c8c
5b64a6a
b952530
571f8b6
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -21,5 +21,7 @@ http: | |
logs: | ||
mode: development | ||
level: debug | ||
use_local_time: true | ||
show_caller: true | ||
Comment on lines
+24
to
+25
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 💡 Codebase verification Documentation needed for new logging configuration options The new configuration options
🔗 Analysis chainLGTM! Well-structured configuration. The new logging options are correctly placed under the Let's verify the configuration schema documentation: 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Check if these new options are documented in the schema or docs
# Expected: Find references to these new config options in documentation
# Look for schema definitions or documentation
rg -g '*.{md,json,yaml}' -i "use.*local.*time|show.*caller"
Length of output: 174 Script: #!/bin/bash
# Let's check for any documentation or schema files that might define logger configuration
fd -e md -e yaml -e json . | grep -i "schema\|config\|logger" | xargs cat 2>/dev/null | grep -i "logger\|log"
Length of output: 2239 |
||
file_logger_options: | ||
log_output: "test.log" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if I understand this. The caller is the line where your log is. How is that difficult to find where you send this log?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When developing custom plugins, although logs show what happened, pinpointing the exact source of a log entry in complex plugin code can be challenging without caller information. By enabling show_caller, we can immediately see which file and line generated the log, significantly improving debugging efficiency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can it be complex? It is just ctrl+f (or / for vim) -> enter log message -> here you are.