-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Ability to separately disable access log in http and stream contexts #5348
Ability to separately disable access log in http and stream contexts #5348
Conversation
Welcome @Antiarchitect! |
Hi @Antiarchitect. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I prefer to find out the reason of that output than disabling logs completely. |
@aledbf I'm using stable/nginx-ingress helm chart 1.34.3 which is using quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.30.0 internally.
It would be nice to have the ability to turn off Stream access log entirely but leave HTTP access log as I need it. For now, I've turned off both using |
@ElvinEfendi @cmluciano Any progress on this? |
This looks good to me, but I'd like to see some tests. @Antiarchitect any chance you can include e2e test to cover this new functionality? You can check the tests in |
@ElvinEfendi I'm bad at Go, but will try to add tests in a few days or so. Still thinking this change is more than trivial. |
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.
/ok-to-test
adding label so that tests will kick in once pushed
Two new configuration options: `disable-http-access-log` `disable-stream-access-log` Should resolve issue with enormous amount of `TCP 200` useless entries in logs Signed-off-by: Andrey Voronkov <voronkovaa@gmail.com>
Signed-off-by: Andrey Voronkov <voronkovaa@gmail.com>
baebda7
to
96d8699
Compare
/retest |
Codecov Report
@@ Coverage Diff @@
## master #5348 +/- ##
==========================================
+ Coverage 58.56% 58.57% +0.01%
==========================================
Files 88 88
Lines 6948 6950 +2
==========================================
+ Hits 4069 4071 +2
Misses 2431 2431
Partials 448 448
Continue to review full report at Codecov.
|
@ElvinEfendi @cmluciano Sorry for the delay guys. I've just added tests, but do not know how to make them better and test that access_log off appears in specific blocks. If you have any ideas of how to improve - you're welcome :) |
@ElvinEfendi @cmluciano Any news guys? |
@ElvinEfendi @cmluciano Bump |
Can we change this to enable-http-access-log and enable-stream-access-log, just to be clear, Note: I know we have used |
@aledbf All three? It would be backward incompatible. In case we change only two annotations it would be awkward and even ambiguous. |
Guys, should I expect this will be resolved somehow? |
@ElvinEfendi @cmluciano Is there any resolution on this? |
/lgtm |
@Antiarchitect thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aledbf, Antiarchitect The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Two new configuration options:
disable-http-access-log
disable-stream-access-log
Should resolve issue with enormous amount of
TCP 200
useless entries in logsTypes of changes
Which issue/s this PR fixes
How Has This Been Tested?
No time to test. Changes are trivial. Having millions of useless TCP 200 in my logs and my Elasticsearch is going to explode soon
Checklist: