-
Notifications
You must be signed in to change notification settings - Fork 78
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
Using global variable to control bpf log level #1206
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Zhonghu Xu <[email protected]>
Signed-off-by: Zhonghu Xu <[email protected]>
Signed-off-by: Zhonghu Xu <[email protected]>
Signed-off-by: Zhonghu Xu <[email protected]>
Signed-off-by: Zhonghu Xu <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
config.BpfLogLevel = uint32(level) | ||
if err := bpf.UpdateKmeshConfigMap(s.kmeshConfigMap, config); err != nil { | ||
http.Error(w, fmt.Sprintf("update log level error: %v", err), http.StatusBadRequest) | ||
if err := s.bpfLogLevel.Set(uint32(level)); err != nil { |
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.
So is it now not necessary for KmeshConfigmap to pass the log_level?
Signed-off-by: Zhonghu Xu <[email protected]>
05db8eb
to
e94e27d
Compare
Signed-off-by: Zhonghu Xu <[email protected]>
/lgtm |
/retest |
What type of PR is this?
What this PR does / why we need it:
Using global variable to control bpf log level
Should be after #1205
Which issue(s) this PR fixes:
Fixes #
Special notes for you're reviewer:
Does this PR introduce a user-facing change?: