限流问题

[silent-night-no-trace]

我们鼓励使用英文，如果不能直接使用，可以使用翻译软件，您仍旧可以保留中文原文。另外请按照如下要求提交相关信息节省社区维护同学的理解成本，否则该讨论极有可能直接被忽视或关闭。
We recommend using English. If you are non-native English speaker, you can use the translation software. We recommend using English. If you are non-native English speaker, you can use the translation software. In addition, please submit relevant information according to the following requirements to save the understanding cost of community maintenances, otherwise the discussion is very likely to be ignored or closed directly.

Which Component
eg. Nacos Discovery, Sentinel
Sentinel

Describe what problem you have encountered
A clear and concise description of what you want to do.

I use gateway to integrate sentinel for gateway current limiting. On the sentinel dashboard, I find that the triggered current limiting is the same as the current limiting threshold I configured. However, when I check the NGINX log in sls, I find that the qps of the same interface is much higher. What is the problem?

Describe what information you have read
eg. I have read the reference doc of Sentinel
I checked the console of sentinel's dashboard. The interface current limiting graph is the same as the current limiting threshold I set.

[silent-night-no-trace]

The current limiting threshold I set on the sentinel dashboard is 100 qps. The threshold on the console results in 100 and the current limiting is correct. But when I checked the NGINX log in sls, the qps of the interface was 300 (much greater than 100). What is the problem?

[yuluo-yx]

抓下包看看流量是哪里打过来的