For Spring Cloud Alibaba Sentinel, you may submit an issue in https://github.com/alibaba/spring-cloud-alibaba/issues

For Spring Cloud Alibaba Sentinel, you may submit an issue in https://github.com/alibaba/spring-cloud-alibaba/issues

OK，I'll ask the issue to go there

Keep track on alibaba/spring-cloud-alibaba#2894

I found this might be a sentinel problem. My test codes as below:

@GetMapping("/rt")
public String rt() {
      return restTemplate.getForObject("https://httpbin.org/delay/1", String.class);
 }
# degrade rule
{
    "resource": "/rt",
    "count": 1,
    "grade": 0,
    "timeWindow": 30000
  }

In sentinel 1.7.1, request will be degraded. But in sentinel 1.8.1, rule won't be degraded.

Hello, is there a version to solve this problem?

I tried to introduce Sentinel-core instead of spring-cloud-alibaba, and found that the 1.8.6 slow call ratio of Sentinel-core is not effective. If this version is changed to 1.6.4, it can be effective. Is there anything done by Sentinel that causes the fuse to fail to take effect? Is there any concern about this problem

I tried the 1.7.2 version of Sentinel-core. The fuse can take effect. The upgrade to 1.8.0 does not take effect. It should not take effect after 1.8.0

@sczyh30 Hello, can you help me look at this first?

I found this might be a sentinel problem. My test codes as below:

@GetMapping("/rt")
public String rt() {
      return restTemplate.getForObject("https://httpbin.org/delay/1", String.class);
 }
# degrade rule
{
    "resource": "/rt",
    "count": 1,
    "grade": 0,
    "timeWindow": 30000
  }

In sentinel 1.7.1, request will be degraded. But in sentinel 1.8.1, rule won't be degraded.

This code doesn't seem to have anything to do with @SentinelRestTemplate .