使用Sentinel配置限流和熔断发现只要服务重启dashboard中的规则就会全部消失将配置持久化到Nacos服务启动自动同步规则到Sentinel。导入依赖dependencygroupIdcom.alibaba.cloud/groupIdartifactIdspring-cloud-starter-alibaba-sentinel/artifactId/dependencydependencygroupIdcom.alibaba.csp/groupIdartifactIdsentinel-datasource-nacos/artifactId/dependencydependencygroupIdcom.alibaba.cloud/groupIdartifactIdspring-cloud-starter-alibaba-nacos-discovery/artifactId/dependencyNacos创建配置一个类型的规则创建一个配置即可多的可以追加。限流配置[{resource:/user/login,limitApp:default,grade:1,count:2,strategy:0,controlBehavior:0}]resource资源名需要保护的接口limitApp流控针对的来源grade 阈值类型1表示QPScount阈值大小QPSstrategy流控模式0表示直接流控controlBehavior流控效果0表示快速失败熔断配置[{resource:/user/getNearUserPhotoById/{id},grade:0,count:0.05,timeWindow:5,minRequestAmount:5,statIntervalMs:10000,slowRatioThreshold:0.2}]resource资源名接口名grade熔断策略count阈值timeWindow熔断持续时间秒minRequestAmount最小请求数statIntervalMs统计时间窗口毫秒slowRatioThreshold慢调用比例阈值0~1yml文件中增加配置spring:cloud:sentinel:transport:dashboard:localhost:8866port:8719datasource:ds1:#添加nacos数据源的配置将sentinel配置持久化到nacos里面 nacos:server-addr:localhost:8848dataId:sentinel-limit groupId:sentinel data-type:json rule-type:flow ds2:nacos:server-addr:localhost:8848dataId:sentinel-breaker groupId:sentinel data-type:json rule-type:degrade nacos:discovery:server-addr:localhost:8848重启项目后请求接口发现规则同步成功
