sentinel1.8.0 网关配置降级规则(异常数，异常比例) 不能降级
- Dominant language
- Java
- Stars
- 23.1k
- Forks
- 8.1k
- PR merge metrics
- No merged PRs in 30d
Description
## Issue Description
在全局异常中 Tracer.trace()
通过springcloud gateway 调用后端服务 抛出异常
用jmeter 执行不能触发熔断降级
Type: *bug report* or *feature request*
### Describe what happened (or what feature you want)
### Describe what you expected to happen
### How to reproduce it (as minimally and precisely as possible)
1.
2.
3.
### Tell us your environment
### Anything else we need to know?
Contributor guide
Research direction
Start at the global-exception Tracer.trace() path and reproduce the behavior through Spring Cloud Gateway using the configured exception-count and exception-ratio rules, then compare it with the JMeter scenario shown. Done means a backend exception reliably triggers the expected Sentinel downgrade under both rule types, with a focused regression test if the relevant test location can be identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100