Skip to content
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

fix: log level for client-side throttling #11393

Conversation

Jack-R-lantern
Copy link
Contributor

@Jack-R-lantern Jack-R-lantern commented Jul 19, 2023

Expresses when throttling occurs on the
client side by setting the log message level to Warn.

Fixes #11387

Motivation

Modifications

Verification

Expresses when throttling occurs on the
client side by setting the log message level to Warn.

fixes: argoproj#11387

Signed-off-by: Jack-R-lantern <[email protected]>
@@ -17,7 +17,7 @@ func (m k8sLogRoundTripper) RoundTrip(r *http.Request) (*http.Response, error) {
x, err := m.roundTripper.RoundTrip(r)
if x != nil {
verb, kind := k8s.ParseRequest(r)
log.Debugf("%s %s %d", verb, kind, x.StatusCode)
log.Warnf("%s %s %d", verb, kind, x.StatusCode)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the motivation?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it should be kept at debug, this log is very expensive!

@Jack-R-lantern Jack-R-lantern force-pushed the ISSUE-11387/Better-exposure-for-client-side-throttling branch from b05339e to 824c736 Compare July 19, 2023 04:49
@@ -17,7 +17,7 @@ func (m k8sLogRoundTripper) RoundTrip(r *http.Request) (*http.Response, error) {
x, err := m.roundTripper.RoundTrip(r)
if x != nil {
verb, kind := k8s.ParseRequest(r)
log.Debugf("%s %s %d", verb, kind, x.StatusCode)
log.Warnf("%s %s %d", verb, kind, x.StatusCode)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it should be kept at debug, this log is very expensive!

@Jack-R-lantern
Copy link
Contributor Author

Sorry about that. I'll think about it a bit more and submit a PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Better exposure for client-side throttling
3 participants