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
feat: logging customization #2961
Merged
Merged
Changes from 8 commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
a7e71d0
implement logging configuration
jiewpeng a98f9e5
add docs
jiewpeng d7028e2
docs: fix wrong name for example neural net (#2959)
ssun-g 2eec1fd
docs: fix bentoml containerize command help message (#2957)
aarnphm 4b6a5d8
Merge branch 'main' into feat/logging-customization
jiewpeng 16c8e20
chore(cli): remove unused `--no-trunc` (#2965)
benjamintanweihao 24d1f7f
remove options to configure logging format and datefmt
jiewpeng 8ddf3c7
Merge branch 'main' into feat/logging-customization
jiewpeng 66f9c74
use eager imports
jiewpeng 6e7d2a3
standardise naming
jiewpeng cef08c4
Merge branch 'main' into feat/logging-customization
jiewpeng f0ec881
docs: update wrong paths for disabling logs (#2974)
creativedutchmen 098daa2
feat: track serve update for start subcommands (#2976)
ssheng 7e40042
add docs
jiewpeng 021495c
Merge branch 'main' into feat/logging-customization
jiewpeng File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
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.
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 prefer to make this
logging_formatting
to be consistent with the config level.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 could change it, but would there be a use case for someone to have one trace id format for the api server and a different format for the runner? When I requested for this feature, the premise was that I would want the trace id format to be consistent across my applications, so I don't really see a use case where a user would want different formats.
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.
Oh I was saying just to change the naming to make it consistent