-
Notifications
You must be signed in to change notification settings - Fork 334
feat: add --log-level support for manager and scheduler #4146
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
Conversation
d63b92e
to
f4b92e1
Compare
@gaius-qi Please help to review. |
e7bbf58
to
00df44c
Compare
00df44c
to
cd84667
Compare
Signed-off-by: Aaron Wang <aaron.wang@maiscrm.com>
cd84667
to
54e04bb
Compare
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.
LGTM
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.
lgtm
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4146 +/- ##
==========================================
- Coverage 32.96% 32.94% -0.03%
==========================================
Files 346 346
Lines 40922 40949 +27
==========================================
- Hits 13490 13489 -1
- Misses 26538 26566 +28
Partials 894 894
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Now client is maintained in https://github.com/dragonflyoss/client. |
Description
This change adds
--log-level
option for manager and scheduler, with empty string as default value, so it won't affect existing depoyments. When specify--log-level
and--verbose
at the same time,--log-level
will take precedence.Note that since cmd and log functionality use shared code, so dfcahe and dfget are also affected.
Config files containing
verbose: true
have been updated, but not those undertestdata/
.Related Issue
#2670
Motivation and Context
We see a lot of logs in our environment, it would be nice to be able to control log level of manager and scheduler so we can ignore not important logs and reduce log storage cost.
Also, the
peer fsm event failed: event Leave inappropriate because previous transition did not complete
log is too frequent, better to change its level to INFO so it can be ignored.Screenshots (if appropriate)
Types of changes
Checklist