filter: add ratelimit log#17902
filter: add ratelimit log#17902mattklein123 merged 1 commit intoenvoyproxy:mainfrom zirain:ratelimit-tracelog
Conversation
|
Hi @zirain, welcome and thank you for your contribution. We will try to review your Pull Request as quickly as possible. In the meantime, please take a look at the contribution guidelines if you have not done so already. |
|
Please add signature for every commit by |
wbpcode
left a comment
There was a problem hiding this comment.
Thanks. We do need some logs to help us to debug rate limit filter.
I add some initial comments to help us to complete this.
davinci26
left a comment
There was a problem hiding this comment.
thanks! Got a small question. Please take a look at the format and DCO
|
/wait |
do we still wait something else? |
|
Is the CI is passing the DCO and the format check? |
|
You will need to apply the DCO on the first commit (follow the instructions here) which would require rewritting the git history of your PR. Also take a look at https://dev.azure.com/cncf/envoy/_build/results?buildId=87580&view=logs&j=55bc2ab9-36c1-5ab8-58a6-8c258728eeff&t=33b57bf9-ef13-58c8-bc2b-f804aeb16d39 which indicates that you have some format errors |
These are the remaining problems. |
All checks have passed. |
davinci26
left a comment
There was a problem hiding this comment.
Thanks, LGTM @envoyproxy/senior-maintainers for a second review
wbpcode
left a comment
There was a problem hiding this comment.
Thanks. And waiting senior-maintainers to merge it.
mattklein123
left a comment
There was a problem hiding this comment.
Thanks, small comment.
/wait
There was a problem hiding this comment.
This will log spam at high volume if the upstream RL server is having issues which I don't think is what we want. I would switch this to debug. There should already be a failure stat. If not we can add one?
There was a problem hiding this comment.
there's nothing record right now when the upstream RL server is having issues, I think 'warn' is suitable in this scenario
There was a problem hiding this comment.
As I said it's not suitable for log spamming reasons. If there is no other stat, you can also potentially use ENVOY_LOG_EVERY_POW_2 or similar.
Signed-off-by: zirain <zirain2009@hotmail.com>
@mattklein123 please check the code again |
Commit Message: add ratelimt log
Additional Description:
add some log to help debug ratelimt filter, in following cases specially:
Risk Level: Low
Testing: manual testing
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]