-
Notifications
You must be signed in to change notification settings - Fork 340
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
switch from warning to debug when upstream labels are empty #724
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #724 +/- ##
=====================================
Coverage 3.87% 3.87%
=====================================
Files 5 5
Lines 1316 1316
=====================================
Hits 51 51
Misses 1265 1265 ☔ View full report in Codecov by Sentry. |
da248e4
to
af8953b
Compare
9b0ea5e
to
b64d93e
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
@pdabelf5 @oseoin @j1m-ryan this issue is still not resolved and we are getting level=debug ts=2024-06-17T07:28:09.172Z caller=nginx_plus.go:849 msg="wrong number of labels for upstream peer, empty labels will be used instead" upstream=tritonExternalSelfHosted-dev peer expected=1 got=0 can you please look into this at earliest since this is serious performance degradation for nginx-plus users . |
Proposed changes
Turn down logging when upstream labels are empty.
Checklist
Before creating a PR, run through this checklist and mark each as complete.
guide