+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**id**|String|False| |plugin id|
+|**name**|String|True| |plugin name|
+|**config**|String|False| |plugin configuration (Json format)|
+|**role**|String|False| |plugin role |
+|**enabled**|Boolean|False| |whether to turn on|
+
+##### Example
+
+POST body
+
+```
+{"id":3,"name":"divide","enabled":"true"}
+
+```
+
+### CleanAll
+
+Clear all data (plugins, selectors, rules)
+
+##### Request Method
+
+GET
+
+##### Path
+
+/cleanAll
+
+### Clean Plugin
+
+Clear plugin data（selector, rule）
+
+##### Request Method
+
+GET
+
+##### Path
+
+/cleanPlugin?name = xxxx
+
+##### RequestParam
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**name**|String|true| |plugin name |
+
+### Delete plugin
+
+Remove plugin data (not included, the selectors and rules data)
+
+##### Request Method
+
+GET
+
+##### Path
+
+/plugin/delete?name = xxxx
+
+##### RequestParam
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**name**|String|true| |plugin name |
+
+### Delete All Plugin
+
+Remove all plugin data (not included, the selectors and rules data)
+
+##### Request Method
+
+GET
+
+##### Path
+
+/plugin/deleteAll
+
+### Find plugin by name
+
+Find plugin by name
+
+##### Request Method
+
+GET
+
+##### Path
+
+/plugin/findByName?name=xxxx
+
+##### RequestParam
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**name**|String|true| |plugin name |
+
+### Save or Update Selector
+
+Save or Update Selector
+
+##### Request Method
+
+POST
+
+##### Path
+
+/plugin/selector/saveOrUpdate
+
+##### RequestParam
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**SelectorData**|[SelectorData](#SelectorData)|True| |Selector object (pass Json object inside Body)|
+
+#####
SelectorData
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**id**|String|False| |selector id|
+|**pluginName**|String|True| |plugin name|
+|**name**|String|False| |Selector name (default is plugin:selector+random number if not filled)|
+|**matchMode**|Integer|False| |Matching mode (0:and;1:or), not filled with the default generation And mode|
+|**type**|Integer|False| |Traffic type（0: full traffic; 1: custom traffic) do not fill in the default generation of full traffic|
+|**sort**|Integer|False| |Sort by, not filled by default generate 10|
+|**enabled**|Boolean|False| |Whether to turn on, not fill in the default generation true|
+|**logged**|Boolean|False| |Whether or not to print the log, do not fill in the default generated into false|
+|**handle**|String|False| |Selector handler (Json objects, depending on each plug-in, different objects are passed)|
+|**conditionList**|[Condition](#Condition)|False| |Conditional collection, custom traffic needs to be passed, full traffic does not need to be passed (Json List object)|
+
+#####
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**pluginName**|String|True| |plugin name|
+|**selectorName**|String|False| |Selector name (if not filled in, it is generated by default plugin:selector+random number)|
+|**matchMode**|Integer|False| |Matching mode (0:and;1:or), not filled with the default generation And mode|
+|**selectorHandler**|String|False| |Selector handler (Json objects, depending on each plug-in, different objects are passed)|
+|**conditionList**|[ConditionData](#ConditionData)|True| |Selector condition collection (Json List object)|
+|**ruleDataList**|[RuleLocalData](#RuleLocalData)|True| |Rule condition collection (Json List object)|
+
+#####
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**paramType**|String|True| |param type（post，uri，query，host，header，cookie，req_method，domain）|
+|**operator**|String|True| |operator （match，=，regex，>，<，contains，SpEL，Groovy，TimeBefore，TimeAfter）|
+|**paramName**|String|False| |param mame（The uri parameter type can be passed without）|
+|**paramValue**|Integer|False| |param value|
+
+##### Example
+
+POST body
+
+```
+{
+ "pluginName": "divide",
+ "selectorHandler": "[{\"upstreamUrl\":\"127.0.0.1:8089\"}]",
+ "conditionDataList": [{
+ "paramType": "uri",
+ "operator": "match",
+ "paramValue": "/http/**"
+ }],
+ "ruleDataList": [{
+ "ruleHandler": "{\"loadBalance\":\"random\"}",
+ "conditionDataList": [{
+ "paramType": "uri",
+ "operator": "=",
+ "paramValue": "/http/test/payment"
+ }]
+ }, {
+ "ruleHandler": "{\"loadBalance\":\"random\"}",
+ "conditionDataList": [{
+ "paramType": "uri",
+ "operator": "=",
+ "paramValue": "/http/order/save"
+ }]
+ }]
+}
+
+```
+
+### Delete Selector
+
+Delete selectors based on selector id and plugin name
+
+##### Request Method
+
+GET
+
+##### Path
+
+/plugin/selector/delete?pluginName=xxxx&&id=xxxx
+
+##### RequestParam
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**pluginName**|String|true| |plugin name |
+|**id**|String|true| |selector id |
+
+### Find All Selector
+
+Get all selectors by plugin name
+
+##### Request Method
+
+GET
+
+##### Path
+
+/plugin/selector/findList?pluginName=xxxx
+
+##### RequestParam
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**pluginName**|String|true| |plugin name |
+
+### Save or Update Rule Data
+
+Save or Update Rule Data
+
+##### Request Method
+
+POST
+
+##### Path
+
+/plugin/rule/saveOrUpdate
+
+##### RequestParam
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**RuleData**|[RuleData](#RuleData)|True| |Rule object (pass Json object inside Body)|
+
+#####
RuleData
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**id**|String|False| |rule id|
+|**pluginName**|String|True| |plugin name|
+|**name**|String|False| |Rule name (default generation if not filled plugin:rule+random number)|
+|**selectorId**|String|True| |Selector id|
+|**matchMode**|Integer|False| |Matching mode (0:and;1:or), not filled with the default generation And mode|
+|**sort**|Integer|False| |Sort by , not filled by default generate 10|
+|**enabled**|Boolean|False| |Whether to turn on, not fill in the default generation true|
+|**logged**|Boolean|False| |Whether or not to print the log, do not fill in the default generated into false|
+|**handle**|String|False| |Rule handler (Json objects, depending on each plug-in, different objects are passed)|
+|**conditionList**|[ConditionData](#ConditionData)|False| |Conditional collections (Json List objects)|
+
+#####
conditionList
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**paramType**|String|True| |param type（post，uri，query，host，header，cookie，req_method，domain）|
+|**operator**|String|True| |operator （match，=，regex，>，<，contains，SpEL，Groovy，TimeBefore，TimeAfter）|
+|**paramName**|String|False| |param mame（The uri parameter type can be passed without）|
+|**paramValue**|Integer|False| |param value|
+
+##### Example
+
+POST body
+
+```
+{
+ "pluginName": "divide",
+ "selectorId": 123456,
+ "handle": "{\"loadBalance\":\"random\"}",
+ "conditionDataList": [{
+ "paramType": "uri",
+ "operator": "=",
+ "paramValue": "/test"
+ }]
+}
+
+```
+
+##### Result
+
+Is rule id
+
+```
+xxxxx
+```
+
+### Delete rule data
+
+Delete rules based on selector id and rule id
+
+##### Request Method
+
+GET
+
+##### Path
+
+/plugin/rule/delete?selectorId=xxxx&&id=xxxx
+
+##### RequestParam
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**selectorId**|String|true| |selector ID |
+|**id**|String|true| |rule ID |
+
+### Find Rule data List
+
+Get all rules by selector ID
+
+##### Request Method
+
+GET
+
+##### Path
+
+/plugin/rule/findList?selectorId=xxxx
+
+##### RequestParam
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**selectorId**|String|true| |selector id |
+
+## Meta data
+
+### Save Or Update
+
+Save Or Update Meta data
+
+##### Request Method
+
+POST
+
+##### Path
+
+/meta/saveOrUpdate
+
+##### RequestParam
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**MetaData**|[MetaData](#MetaData)|True| |Metadata object (pass Json object inside Body)|
+
+#####
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**appKey**|String|True| |app key|
+|**appSecret**|String|True| |app secret|
+|**enabled**|Boolean|False| |Whether to turn on|
+|**open**|Boolean|False| |is open|
+|**paramDataList**|[AuthParamData](#AuthParamData)|false| |Parameter set, open is true when you need to pass (Json list object)|
+|**AuthPathData**|[AuthPathData](#AuthPathData)|false| |Path collection, open is true when you need to pass (Json list object)|
+
+#####
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**appName**|String|True| |app name|
+|**path**|String|True| |path|
+|**enabled**|Boolean|False| |Whether to turn on|
+
+### Delete
+
+Delete App Sign Data
+
+##### Request Method
+
+GET
+
+##### Path
+
+/auth/delete?appKey=xxxx
+
+##### RequestParam
+
+|Name|Type|Required|Default|Description|
+|---|---|---|---|---|
+|**appKey**|String|true| |app key |
diff --git a/versioned_docs/version-2.6.1/developer/notice-alert.md b/versioned_docs/version-2.6.1/developer/notice-alert.md
new file mode 100644
index 00000000000..500b8ed7ec5
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/notice-alert.md
@@ -0,0 +1,83 @@
+---
+title: Alarm Notice
+keywords: ["alarm"]
+description: Alarm message dispatch and notice
+---
+
+## Description
+
+* This doc gives a brief description for send alarm notice message using `Apache ShenYu API`.
+
+## Enable Alert in ShenYu Gateway
+
+* Config the gateway `application.yml`
+
+```yaml
+shenyu:
+ alert:
+ enabled: true
+ # the shenyu admin servers, if admin cluster, config like 127.0.0.1:9095,192.3.4.2:9095
+ admins: localhost:9095
+```
+
+## Send Alarm Message
+
+* We can send custom alarm message in plugin using `AlarmSender.alarm()`
+
+Refer below:
+
+```java
+public class ParamMappingPlugin extends AbstractShenyuPlugin {
+
+ @Override
+ public Mono doExecute(final ServerWebExchange exchange, final ShenyuPluginChain chain, final SelectorData selector, final RuleData rule) {
+ ParamMappingRuleHandle paramMappingRuleHandle = ParamMappingPluginDataHandler.CACHED_HANDLE.get().obtainHandle(CacheKeyUtils.INST.getKey(rule));
+
+ if(some condition) {
+ Map labels = new HashMap<>(8);
+ labels.put("plugin", "http-redirect");
+ labels.put("component", "http");
+ AlarmSender.alarmHighEmergency("alarm-title", "alarm-content", labels);
+ AlarmSender.alarmMediumCritical("alarm-title", "alarm-content", labels);
+ AlarmSender.alarmLowWarning("alarm-title", "alarm-content", labels);
+ AlarmSender.alarm((byte) 0, "alarm-title", "alarm-content");
+ }
+
+ HttpHeaders headers = exchange.getRequest().getHeaders();
+ MediaType contentType = headers.getContentType();
+ return match(contentType).apply(exchange, chain, paramMappingRuleHandle);
+ }
+}
+```
+
+## Dispatch Alarm Notice
+
+* In the previous step, we send custom alarm message in plugin.
+* Now we configure how these messages are sent to whom(tom,lili...) by which type(email,DingDing...)
+* Config this in ShenYu Admin Dashboard.
+
+
+
+Have fun!
+
+## Attention
+
+1. If you use the email notice, you should config your email send server in ShenYu Admin `application.yml`
+
+```yaml
+spring:
+ mail:
+ # Attention: this is mail server address.
+ host: smtp.qq.com
+ username: shenyu@apache.com
+ # Attention: this is not email account password, this requires an email authorization code
+ password: your-password
+ port: 465
+ default-encoding: UTF-8
+ properties:
+ mail:
+ smtp:
+ socketFactoryClass: javax.net.ssl.SSLSocketFactory
+ ssl:
+ enable: true
+```
diff --git a/versioned_docs/version-2.6.1/developer/shenyu-optimize.md b/versioned_docs/version-2.6.1/developer/shenyu-optimize.md
new file mode 100644
index 00000000000..0c35a713ef6
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/shenyu-optimize.md
@@ -0,0 +1,44 @@
+---
+title: ShenYu Optimize
+keywords: ["Optimize"]
+description: performance optimization for Apache ShenYu
+---
+
+## Description
+
+* This doc shows how to do performance optimization for Apache ShenYu.
+
+## Time Consumption
+
+* Apache ShenYu is JVM driven and processing time for a single request is nearly between `1-3` ms.
+
+## Netty Optimization
+
+* `spring-webflux` is one of dependencies of ShenYu, and it uses Netty in lower layer.
+* The demo down below demonstrates tuning ShenYu by customizing params in Netty.
+
+```java
+@Bean
+ public NettyReactiveWebServerFactory nettyReactiveWebServerFactory() {
+ NettyReactiveWebServerFactory webServerFactory = new NettyReactiveWebServerFactory();
+ webServerFactory.addServerCustomizers(new EventLoopNettyCustomizer());
+ return webServerFactory;
+ }
+
+private static class EventLoopNettyCustomizer implements NettyServerCustomizer {
+
+ @Override
+ public HttpServer apply(final HttpServer httpServer) {
+ return httpServer
+ .tcpConfiguration(tcpServer -> tcpServer
+ .runOn(LoopResources.create("shenyu-netty", 1, DEFAULT_IO_WORKER_COUNT, true), false)
+ .selectorOption(ChannelOption.SO_REUSEADDR, true)
+ .selectorOption(ChannelOption.ALLOCATOR, PooledByteBufAllocator.DEFAULT)
+ .option(ChannelOption.TCP_NODELAY, true)
+ .option(ChannelOption.ALLOCATOR, PooledByteBufAllocator.DEFAULT));
+ }
+}
+```
+
+* The `shenyu-bootstrap` module offers this class, you may modify it when benchmarking your app if necessary.
+* You can get references of business thread model from [thread model](./thread-model)
diff --git a/versioned_docs/version-2.6.1/developer/spi/_category_.json b/versioned_docs/version-2.6.1/developer/spi/_category_.json
new file mode 100644
index 00000000000..149cee92bf3
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/spi/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "SPI",
+ "position": 1
+}
diff --git a/versioned_docs/version-2.6.1/developer/spi/custom-load-balance.md b/versioned_docs/version-2.6.1/developer/spi/custom-load-balance.md
new file mode 100644
index 00000000000..f4ea3ecb2b8
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/spi/custom-load-balance.md
@@ -0,0 +1,65 @@
+---
+title: Custom Load Balancer
+keywords: ["LoadBalance"]
+description: Custom Load Balance
+---
+
+* This paper describes how to customize the extension of `org.apache.shenyu.loadbalancer.spi.LoadBalancer`.
+
+* Create a new project and introduce the following dependencies:
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-plugin-base
+ ${project.version}
+
+
+```
+
+* Create a new class `CustomLoadBalancer`, extends `org.apache.shenyu.loadbalancer.spi.AbstractLoadBalancer`.
+
+```java
+public class CustomLoadBalancer extends AbstractLoadBalancer {
+
+ @Override
+ public Upstream doSelect(final List upstreamList, final String ip) {
+ // custom load balancer
+ }
+}
+```
+
+* In the project's META-INF/services directory, create key-value as following in `org.apache.shenyu.loadbalancer.spi.LoadBalancer` file.
+
+```shell title="script"
+${spi name}=${custom class path}
+```
+
+`${spi name}` represents the name of `spi` and `${custom class path}` represents the fully qualified name of the class. Such as:
+
+```shell title="script"
+custom=xxx.xxx.xxx.CustomLoadBalancer
+```
+
+* Package the project and copy it to the `lib` or `ext-lib` directory of the gateway (bootstrap-bin).
+
+* In the `Apache ShenYu` gateway management system --> BasicConfig --> Dictionary, find the dictionary code as `LOAD_BALANCE`, add a new piece of data, pay attention to the dictionary name: `${spi name}`.
+
+
+
+> DictionaryType: `loadBalance`;
+>
+> DictionaryCode: `LOAD_BALANCE`;
+>
+> DictionaryName: `${spi name}`, input your custom spi name;
+>
+> DictionaryValue: When used, the value of the drop-down box, do not repeat with the existing;
+>
+> DictionaryDescribe: desc your custom match strategy;
+>
+> Sort: to sort;
+
+* When adding selectors or rules, you can use custom MatchType:
+
+
diff --git a/versioned_docs/version-2.6.1/developer/spi/custom-match-mode.md b/versioned_docs/version-2.6.1/developer/spi/custom-match-mode.md
new file mode 100644
index 00000000000..3539e3e54ff
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/spi/custom-match-mode.md
@@ -0,0 +1,72 @@
+---
+title: Custom Match Mode
+keywords: ["MatchStrategy"]
+description: custom match mode
+---
+
+
+* This paper describes how to customize the extension of `org.apache.shenyu.plugin.base.condition.strategy.MatchStrategy`.
+
+* Create a new project and introduce the following dependencies:
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-plugin-base
+ ${project.version}
+
+
+```
+
+* Create a new class `CustomMatchStrategy`, extends `org.apache.shenyu.plugin.base.condition.strategy.AbstractMatchStrategy`, implements `org.apache.shenyu.plugin.base.condition.strategy.MatchStrategy`, add annotation `org.apache.shenyu.spi.Join`.
+
+```java
+/**
+ * This is custom match strategy.
+ */
+@Join
+public class CustomMatchStrategy extends AbstractMatchStrategy implements MatchStrategy {
+
+ @Override
+ public Boolean match(final List conditionDataList, final ServerWebExchange exchange) {
+ // custom match strategy
+ }
+}
+```
+
+* In the project's META-INF/services directory, create `org.apache.shenyu.plugin.base.condition.strategy.MatchStrategy` file.
+
+```shell title="script"
+${spi name} = ${custom class path}
+```
+
+`${spi name}` represents the name of `spi` and `${custom class path}` represents the fully qualified name of the class. Such as:
+
+```shell title="script"
+custom = xxx.xxx.xxx.CustomMatchStrategy
+```
+
+* Package the project and copy it to the `lib` or `ext-lib` directory of the gateway (bootstrap-bin).
+
+* In the `Apache ShenYu` gateway management system --> BasicConfig --> Dictionary, find the dictionary code as `MATCH_MODE`, add a new piece of data, pay attention to the dictionary name: `${spi name}`.
+
+
+
+> DictionaryType: `matchMode`;
+>
+> DictionaryCode: `MATCH_MODE`;
+>
+> DictionaryName: `${spi name}`, input your custom spi name;
+>
+> DictionaryValue: When used, the value of the drop-down box, do not repeat with the existing;
+>
+> DictionaryDescribe: desc your custom match strategy;
+>
+> Sort: to sort;
+>
+> Status: open or close.
+
+* When adding selectors or rules, you can use custom MatchType:
+
+
diff --git a/versioned_docs/version-2.6.1/developer/spi/custom-metrics-monitor.md b/versioned_docs/version-2.6.1/developer/spi/custom-metrics-monitor.md
new file mode 100644
index 00000000000..c8bf88e78c4
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/spi/custom-metrics-monitor.md
@@ -0,0 +1,63 @@
+---
+title: Custom Metrics Monitor
+keywords: ["MetricsMonitor"]
+description: custom Metrics Monitor
+---
+
+
+## Explanation
+
+* Before custom development, please customize and build the gateway environment first, please refer to: [custom deployment](../deployment-custom)
+
+* This article describes how to customize the extension of `org.apache.shenyu.plugin.metrics.spi.MetricsService`.
+
+## Extension
+
+* Create a new project and introduce the following dependencies:
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-plugin-base
+ ${project.version}
+
+
+```
+
+* Create a new class `${you class}`，implements `org.apache.shenyu.plugin.metrics.spi.MetricsService`
+
+```
+public class ${you class} implements MetricsService {
+
+ /**
+ * Start metrics tracker.
+ *
+ * @param metricsConfig metrics config
+ * @param metricsRegister the metrics register
+ */
+ public void start(MetricsConfig metricsConfig, MetricsRegister metricsRegister){
+ //your code
+ }
+
+ /**
+ * Stop metrics tracker.
+ */
+ public void stop() {
+ //your code
+ }
+}
+```
+
+* In the project `resources` directory，Create a new `META-INF/shenyu` directory， and the new file name is : `org.apache.shenyu.plugin.metrics.spi.MetricsService`.
+add `${you spi name}` = `${you class path}`:
+
+```
+${you spi name} = ${you class path}
+```
+
+* Package the project and copy it to the `lib` or `ext-lib` directory of the gateway (bootstrap-bin).
+
+* In the `Admin` service ---> BasicConfig ---> Plugin , Find the `Monitor` plugin, edit config, pay attention to the `metricsName` name: `${you spi name}`.
+
+
diff --git a/versioned_docs/version-2.6.1/developer/spi/custom-mock-generator.md b/versioned_docs/version-2.6.1/developer/spi/custom-mock-generator.md
new file mode 100644
index 00000000000..618fb42b5ea
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/spi/custom-mock-generator.md
@@ -0,0 +1,77 @@
+---
+title: Custom Mock Data Generator
+keywords: ["Mock"]
+description: custom mock data generator
+---
+## Explanation
+
+1. This article describes how to make custom extensions to `org.apache.shenyu.plugin.mock.generator.Generator`.
+2. The mock data generation expression needs to satisfy the format of `${name|param1|param2|...}`
+
+## Extension
+
+* Create a new project and introduce the following dependencies:
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-plugin-mock
+ ${project.version}
+
+
+```
+
+* Create a new class `CustomerGenerator`，implements `org.apache.shenyu.plugin.mock.generator.Generator`。
+
+```java
+@Join
+public class CustomGenerator implements Generator {
+ @Override
+ public String getName() {
+ // The name of the generator, i.e. the content before the first | of the expression
+ }
+
+ @Override
+ public String generate() {
+ // Implement the logic of data generation
+ }
+
+ @Override
+ public int getParamSize() {
+ // The number of required parameters of the expression
+ }
+
+ @Override
+ public void initParam(List params, String rule) {
+ // params is the contents except the name after the expression is split according to |
+ // rule is the content of the original expression , if there is a custom parameter processing logic, you can use this parameter
+ }
+
+ @Override
+ public boolean match(String rule) {
+ // Check if the current expression is valid
+ }
+
+ @Override
+ public String[] getPrefixAndSuffix() {
+ // Return the prefix and suffix added after the generated content, please return a string array with two elements
+ // 0th element is the prefix, 1st element is the suffix
+ }
+}
+```
+
+* In the project `resources` directory，Create a new `META-INF/shenyu` directory， and the new file name is : `org.apache.shenyu.plugin.mock.generator.Generator`.
+ add `${you spi name}` = `${you class path}`:
+
+```shell title="script"
+${spi name}=${custom class path}
+```
+
+`${spi name}` represents the name of `spi`, `${spi name }` needs to be consistent with the definition of the getName() method in the Generator implementation class, `${custom class path}` represents the fully qualified name of the class. for example:
+
+```shell title="script"
+custom=xxx.xxx.xxx.CustomGenerator
+```
+
+* Package the project and copy it to the `lib` or `ext-lib` directory of the gateway (bootstrap-bin).
diff --git a/versioned_docs/version-2.6.1/developer/spi/custom-parameter-data.md b/versioned_docs/version-2.6.1/developer/spi/custom-parameter-data.md
new file mode 100644
index 00000000000..bff80ece761
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/spi/custom-parameter-data.md
@@ -0,0 +1,71 @@
+---
+title: Custom Parameter Data
+keywords: ["ParameterData"]
+description: Custom Parameter Data
+---
+
+This paper describes how to customize the extension of `org.apache.shenyu.plugin.base.condition.data.ParameterData`.
+
+* Create a new project and introduce the following dependencies:
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-plugin-base
+ ${project.version}
+
+
+```
+
+* Create a new class `CustomParameterData`, implements `org.apache.shenyu.plugin.base.condition.data.ParameterData`, add annotation `org.apache.shenyu.spi.Join`.
+
+```java
+/**
+ * This is custom parameter data.
+ */
+@Join
+public class CustomParameterData implements ParameterData {
+
+ @Override
+ public String builder(final String paramName, final ServerWebExchange exchange) {
+ // custom parameter data
+ }
+}
+```
+
+* In the project's META-INF/services directory, create `org.apache.shenyu.plugin.base.condition.data.ParameterData` file, add key-value as following:
+
+```shell title="script"
+${spi name} = ${custom class path}
+```
+
+`${spi name}` represents the name of `spi` and `${custom class path}` represents the fully qualified name of the class. Such as:
+
+```shell title="script"
+custom=xxx.xxx.xxx.CustomParameterData
+```
+
+* Package the project and copy it to the `lib` or `ext-lib` directory of the gateway (bootstrap-bin).
+
+* In the `Apache ShenYu` gateway management system --> BasicConfig --> Dictionary, find the dictionary code as `PARAM_TYPE`, add a new piece of data, pay attention to the dictionary name: `${spi name}`.
+
+
+
+> DictionaryType: `paramType`;
+>
+> DictionaryCode: `PARAM_TYPE`;
+>
+> DictionaryName: `${spi name}`, input your custom spi name;
+>
+> DictionaryValue: When used, the value of the drop-down box, do not repeat with the existing;
+>
+> DictionaryDescribe: desc your custom match strategy;
+>
+> Sort: to sort;
+>
+> Status: open or close.
+
+* When adding selectors or rules, you can use custom parameter data:
+
+
diff --git a/versioned_docs/version-2.6.1/developer/spi/custom-predicate-judge.md b/versioned_docs/version-2.6.1/developer/spi/custom-predicate-judge.md
new file mode 100644
index 00000000000..6b1640d5b89
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/spi/custom-predicate-judge.md
@@ -0,0 +1,121 @@
+---
+title: Custom Predicate Judge
+keywords: ["PredicateJudge"]
+description: Custom Predicate Judge
+---
+
+## Introduction
+
+* This paper describes how to customize the extension of `org.apache.shenyu.plugin.base.condition.judge.PredicateJudge`.
+* The conditional predicate is the bridge between data and rules in the selector and serves to filter out requests that match the conditions.
+* There are already seven conditional predicates including match, =, regex, contains, TimeBefore, TimeAfter, exclude.
+* Please refer to [judge](https://github.com/apache/shenyu/tree/master/shenyu-plugin/shenyu-plugin-base/src/main/java/org/apache/shenyu/plugin/base/condition/judge) module, add your own conditional predicates, or submit `pr` to the official website if you have a good common plugin.
+
+## Extension
+
+* Create a new project and introduce the following dependencies:
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-plugin-base
+ ${project.version}
+
+
+```
+
+* Create a new class `CustomPredicateJudge`, implements `org.apache.shenyu.plugin.base.condition.judge.PredicateJudge`, add annotation `org.apache.shenyu.spi.Join`.
+
+```java
+/**
+ * custom predicate judge.
+ */
+@Join
+public class CustomPredicateJudge implements PredicateJudge {
+
+ @Override
+ public Boolean judge(final ConditionData conditionData, final String realData) {
+ // Custom Predicate Judge
+ }
+}
+
+```
+
+* In the project's META-INF/services directory, create `org.apache.shenyu.plugin.base.condition.judge.PredicateJudge` file, add key-value as following:
+
+```shell title="script"
+${spi name} = ${custom class path}
+```
+
+`${spi name}` represents the name of `spi` and `${custom class path}` represents the fully qualified name of the class. Such as:
+
+```shell title="script"
+custom=xxx.xxx.xxx.CustomPredicateJudge
+```
+
+* Package the project and copy it to the `lib` or `ext-lib` directory of the gateway (bootstrap-bin).
+
+* In the `Apache ShenYu` gateway management system --> BasicConfig --> Dictionary, find the dictionary code as `OPERATOR`, add a new piece of data, pay attention to the dictionary name: `${spi name}`.
+
+
+
+> DictionaryType: `operator`;
+>
+> DictionaryCode: `OPERATOR`;
+>
+> DictionaryName: `${spi name}`, input your custom spi name;
+>
+> DictionaryValue: When used, the value of the drop-down box, do not repeat with the existing;
+>
+> DictionaryDescribe: desc your custom match strategy;
+>
+> Sort: to sort;
+>
+> Status: open or close.
+
+* When adding selectors or rules, you can use custom predicate judge:
+
+
+
+## Example
+
+* Add `GroovyPredicateJudge` and `SpELPredicateJudge` extension.
+
+```java
+/**
+ * Groovy predicate judge.
+ */
+@Join
+public class GroovyPredicateJudge implements PredicateJudge {
+
+ @Override
+ public Boolean judge(final ConditionData conditionData, final String realData) {
+ return (Boolean) Eval.me(conditionData.getParamName(), realData, conditionData.getParamValue());
+ }
+}
+```
+
+```java
+/**
+ * SpEL predicate judge.
+ */
+@Join
+public class SpELPredicateJudge implements PredicateJudge {
+
+ private static final ExpressionParser EXPRESSION_PARSER = new SpelExpressionParser();
+
+ @Override
+ public Boolean judge(final ConditionData conditionData, final String realData) {
+ Expression expression = EXPRESSION_PARSER.parseExpression(conditionData.getParamValue().replace('#' + conditionData.getParamName(), realData));
+ return expression.getValue(Boolean.class);
+ }
+}
+```
+
+* Update `org.apache.shenyu.plugin.base.condition.judge.PredicateJudge`:
+
+```shell title="script"
+Groovy=xxx.xxx.xxx.GroovyPredicateJudge
+SpEL=xxx.xxx.xxx.SpELPredicateJudge
+```
diff --git a/versioned_docs/version-2.6.1/developer/spi/custom-rate-limiter.md b/versioned_docs/version-2.6.1/developer/spi/custom-rate-limiter.md
new file mode 100644
index 00000000000..4d2bebdbc65
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/spi/custom-rate-limiter.md
@@ -0,0 +1,104 @@
+---
+title: Custom Rate Limiter
+keywords: ["RateLimiter"]
+description: Custom Rate Limiter
+---
+
+## Explanation
+
+* Before custom development, please customize and build the gateway environment first, please refer to: [custom deployment](../deployment-custom).
+
+* This article describes how to customize the extension of `org.apache.shenyu.plugin.ratelimiter.algorithm.RateLimiterAlgorithm` .
+
+## Extension
+
+* Create a new project and introduce the following dependencies:
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-plugin-base
+ ${project.version}
+
+
+```
+
+* Create a new class `${you class}`, implements `org.apache.shenyu.plugin.ratelimiter.algorithm.RateLimiterAlgorithm`
+
+```java
+public class ${you class} implements RateLimiterAlgorithm {
+
+ /**
+ * Gets script.
+ *
+ * @return the script
+ */
+ public RedisScript getScript() {
+ //coding and return
+ }
+
+ /**
+ * Gets keys.
+ *
+ * @param id the id
+ * @return the keys
+ */
+ public List getKeys(String id) {
+ //coding and return
+ }
+
+ /**
+ * Callback string.
+ *
+ * @param script the script
+ * @param keys the keys
+ * @param scriptArgs the script args
+ */
+ public void callback(final RedisScript script, final List keys, final List scriptArgs) {
+ //coding and return
+ }
+}
+```
+
+* In the project `resources` directory，Create a new `META-INF/shenyu` directory， and the new file name is : `org.apache.shenyu.plugin.ratelimiter.algorithm.RateLimiterAlgorithm`.
+add `${you spi name}` = `${you class path}`:
+
+```
+${you spi name} = ${you class path}
+```
+
+* Package the project and copy it to the `lib` or `ext-lib` directory of the gateway (bootstrap-bin).
+
+* In the `Admin` service ---> BasicConfig ---> Dictionary , Find the dictionary code as `ALGORITHM_*`, add a new piece of data, pay attention to the dictionary name: `${you spi name}`.
+
+
+
+* Or execute the following custom `SQL` statement：
+
+```sql
+INSERT IGNORE INTO `shenyu_dict` (
+ `id`,
+ `type`,
+ `dict_code`,
+ `dict_name`,
+ `dict_value`,
+ `desc`,
+ `sort`,
+ `enabled`,
+ `date_created`,
+ `date_updated`
+ )
+VALUES (
+ 'you id',
+ 'matchMode',
+ 'MATCH_MODE',
+ 'you spi name',
+ 'you value',
+ 'you spi name',
+ 0,
+ 1,
+ '2021-08-30 19:29:10',
+ '2021-08-30 20:15:23'
+ );
+```
diff --git a/versioned_docs/version-2.6.1/developer/thread-model.md b/versioned_docs/version-2.6.1/developer/thread-model.md
new file mode 100644
index 00000000000..cee61af2ec3
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/thread-model.md
@@ -0,0 +1,30 @@
+---
+title: Thread Model
+keywords: ["Thread"]
+description: thread model
+---
+
+## Description
+
+* This article gives an introduction to thread models in ShenYu and usage in various scenarios.
+
+## IO And Work Thread
+
+* `spring-webflux` is one of dependencies of ShenYu, and it uses Netty thread model in lower layer.
+
+## Business Thread
+
+* Use scheduling thread to execute by default.
+* A fixed thread pool manages business threads, the number of threads is count in this formula: cpu * 2 + 1.
+
+
+## Type Switching
+
+* `reactor.core.scheduler.Schedulers`.
+* `-Dshenyu.scheduler.type=fixed` is a default config. If set to other value, a flexible thread pool will take place it.`Schedulers.elastic()`.
+* `-Dshenyu.work.threads = xx` is for configuring number of threads, the default value calculates in following formula `cpu * 2 + 1` with a minimum of 16 threads.
+
+
+
+
+
diff --git a/versioned_docs/version-2.6.1/index.md b/versioned_docs/version-2.6.1/index.md
new file mode 100644
index 00000000000..6ed8b63106b
--- /dev/null
+++ b/versioned_docs/version-2.6.1/index.md
@@ -0,0 +1,179 @@
+---
+sidebar_position: 1
+title: Overview
+keywords: ["Apache shenyu"]
+description: This is an asynchronous, high-performance, cross-language, responsive API gateway.
+aliases: "/shenyu/docs/Home"
+---
+
+# Architecture
+
+ 
+
+# What is the Apache ShenYu?
+
+This is an asynchronous, high-performance, cross-language, responsive API gateway.
+
+# Why named Apache ShenYu
+
+ShenYu (神禹) is the honorific name of Chinese ancient monarch Xia Yu (also known in later times as Da Yu), who left behind the touching story of the three times he crossed the Yellow River for the benefit of the people and successfully managed the flooding of the river. He is known as one of the three greatest kings of ancient China, along with Yao and Shun.
+
+* Firstly, the name ShenYu is to promote the traditional virtues of our Chinese civilisation.
+* Secondly, the most important thing about the gateway is the governance of the traffic.
+* Finally, the community will do things in a fair, just, open and meritocratic way, paying tribute to ShenYu while also conforming to the Apache Way.
+
+---
+
+# Features
+
+* Proxy: Support for Apache® Dubbo™, Spring Cloud, gRPC, Motan, SOFA, TARS, WebSocket, MQTT
+* Security: Sign, OAuth 2.0, JSON Web Tokens, WAF plugin
+* API governance: Request, response, parameter mapping, Hystrix, RateLimiter plugin
+* Observability: Tracing, metrics, logging plugin
+* Dashboard: Dynamic traffic control, visual backend for user menu permissions
+* Extensions: Plugin hot-swapping, dynamic loading
+* Cluster: NGINX, Docker, Kubernetes
+* Language: provides .NET, Python, Go, Java client for API register
+
+---
+
+# Mind map
+
+ 
+
+ ---
+
+# Quick Start (docker)
+
+### Run Apache ShenYu Admin
+
+```
+docker pull apache/shenyu-admin
+docker network create shenyu
+docker run -d -p 9095:9095 --net shenyu apache/shenyu-admin
+```
+
+Default account: **admin**
+
+Default password: **123456**
+
+### Run Apache ShenYu Bootstrap
+
+```
+docker pull apache/shenyu-bootstrap
+docker run -d -p 9195:9195 -e "shenyu.local.enabled=true" --net shenyu apache/shenyu-bootstrap
+```
+
+### Set router
+
+* Real requests ：,
+
+```json
+{
+ "name" : "Shenyu",
+ "data" : "hello world"
+}
+```
+
+* Set routing rules (Standalone)
+
+Add `localKey: 123456` to Headers. If you need to customize the localKey, you can use the sha512 tool to generate the key based on plaintext and update the `shenyu.local.sha512Key` property.
+
+```
+curl --location --request POST 'http://localhost:9195/shenyu/plugin/selectorAndRules' \
+--header 'Content-Type: application/json' \
+--header 'localKey: 123456' \
+--data-raw '{
+ "pluginName": "divide",
+ "selectorHandler": "[{\"upstreamUrl\":\"127.0.0.1:8080\"}]",
+ "conditionDataList": [{
+ "paramType": "uri",
+ "operator": "match",
+ "paramValue": "/**"
+ }],
+ "ruleDataList": [{
+ "ruleHandler": "{\"loadBalance\":\"random\"}",
+ "conditionDataList": [{
+ "paramType": "uri",
+ "operator": "match",
+ "paramValue": "/**"
+ }]
+ }]
+}'
+```
+
+* Proxy request ：
+
+```json
+{
+ "name" : "Shenyu",
+ "data" : "hello world"
+}
+```
+
+---
+
+# Plugin
+
+ Whenever a request comes in, Apache ShenYu will execute it by all enabled plugins through the chain of responsibility.
+
+ As the heart of Apache ShenYu, plugins are extensible and hot-pluggable.
+
+ Different plugins do different things.
+
+ Of course, users can also customize plugins to meet their own needs.
+
+ If you want to customize, see [custom-plugin](https://shenyu.apache.org/docs/developer/custom-plugin/) .
+
+---
+
+# Selector & Rule
+
+ According to your HTTP request headers, selectors and rules are used to route your requests.
+
+ Selector is your first route, It is coarser grained, for example, at the module level.
+
+ Rule is your second route and what do you think your request should do. For example a method level in a module.
+
+ The selector and the rule match only once, and the match is returned. So the coarsest granularity should be sorted last.
+
+---
+
+# Data Caching & Data Sync
+
+ Since all data have been cached using ConcurrentHashMap in the JVM, it's very fast.
+
+ Apache ShenYu dynamically updates the cache by listening to the ZooKeeper node (or WebSocket push, HTTP long polling) when the user changes configuration information in the background management.
+
+ 
+
+ 
+
+---
+
+# Prerequisite
+
+* JDK 1.8+
+
+---
+
+# Stargazers over time
+
+
+
+---
+
+# Contributor and Support
+
+* [How to Contribute](https://shenyu.apache.org/community/contributor-guide)
+* [Mailing Lists](mailto:dev@shenyu.apache.org)
+
+---
+
+# Known Users
+
+In order of registration, More access companies are welcome to register at [https://github.com/apache/shenyu/issues/68](https://github.com/apache/shenyu/issues/68) (For open source users only) .
+
+All Users : [Known Users](https://shenyu.apache.org/community/user-registration)
+
+---
diff --git a/versioned_docs/version-2.6.1/plugin-center/_category_.json b/versioned_docs/version-2.6.1/plugin-center/_category_.json
new file mode 100644
index 00000000000..5831affdd38
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Plugin Center",
+ "position": 6
+}
diff --git a/versioned_docs/version-2.6.1/plugin-center/cache/_category_.json b/versioned_docs/version-2.6.1/plugin-center/cache/_category_.json
new file mode 100644
index 00000000000..8768a0fab5a
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/cache/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Cache",
+ "position": 7
+}
diff --git a/versioned_docs/version-2.6.1/plugin-center/cache/cache-plugin.md b/versioned_docs/version-2.6.1/plugin-center/cache/cache-plugin.md
new file mode 100644
index 00000000000..10675c44589
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/cache/cache-plugin.md
@@ -0,0 +1,152 @@
+---
+title: Cache Plugin
+keywords: ["Cache"]
+description: Cache Plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Cache Plugin
+
+## 1.2 Appropriate Scenario
+
+* Situation where data is not updated frequently and a large number of calls are required.
+
+* For Situation where data consistency is not required.
+
+## 1.3 Plugin functionality
+
+* The `Cache` plugin is able to cache the results of the target service, allowing the user to configure the expiration
+ time of the cached results.
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-cache-handler`.
+* Core Module `shenyu-plugin-cache-redis`.
+* Core Module `shenyu-plugin-cache-memory`.
+
+* Core Class `org.apache.shenyu.plugin.cache.CachePlugin`
+* Core Class `org.apache.shenyu.plugin.cache.redis.RedisCache`
+* Core Class `org.apache.shenyu.plugin.cache.memory.MemoryCache`
+
+## 1.5 Added Since Which shenyu version
+
+* Since 2.4.3
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+* Import cache plugin dependency in `ShenYu Bootstrap`.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-cache
+ ${project.version}
+
+
+```
+
+## 2.3 Enable plugin
+
+- In shenyu-admin --> BasicConfig --> Plugin --> `cache` set Status enabled.
+
+## 2.4 Config plugin
+
+### 2.4.1 Plugin Config
+
+
+
+* `cacheType`: Cache currently supports two modes of caching data.
+
+* memory：local memory mode
+
+* redis：redis mode
+
+The current default is `local memory mode`, the results of the target service are stored in the local memory, if the
+gateway is deployed by way of cluster, it is not recommended to use `local memory mode`, it is recommended to
+use `redis mode`, the data of the target service are cached in redis.
+
+If you are using `local memory mode`, you only need to select memory in cacheType, no other configuration is needed.
+
+If you are using `redis mode`, select redis in cacheType, and the parameters are as follows
+
+* `database`: which database the cache results are stored in, the default is index database 0.
+
+* `master`: default is master.
+
+* `mode`: the working mode of redis, the default is single-point mode: `standalone`, in addition to cluster
+ mode: `cluster`, sentinel mode: `sentinel`.
+
+* `url`: configure the IP and port of the redis database, configured by colon connection, example: `192.168.1.1:6379`.
+
+* `password`: the password of the redis database, if not, you can not configure.
+
+* `maxldle`: the maximum free connections in the connection pool
+
+* `minldle`: minimum idle connections in the connection pool
+
+* `maxActive`: the maximum number of connections in the connection pool
+
+* `maxWait`: the maximum blocking wait time for the connection pool (use negative values to indicate no limit) default -1
+
+### 2.4.2 Selector Config
+
+* Selectors and rules, please refer to: [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule) .
+
+### 2.4.3 Rule Config
+
+
+
+* Only matching requests will be cached by the Cache plugin for the results of the target service.
+
+`timeoutSecods`: the value is the target service result data cache time, the default is 60, in `seconds`.
+
+Notice: The current version of the Cache plugin uses the url as a unique key to identify the same request.
+
+## 2.5 Examples
+
+### 2.5.1 Use redis cache request result
+
+#### 2.5.1.1 Plugin Config
+
+
+
+select redis cache type, config redis database, url, mode, password
+
+#### 2.5.1.2 Selector Config
+
+
+
+#### 2.5.1.3 Rule Config
+
+
+
+#### 2.5.1.4 Send Request
+
+* send http request to cache result.
+
+```http title="request"
+### shengyu getway proxy orderSave
+GET http://localhost:9195/http/order/findById?id=123
+Accept: application/json
+Content-Type: application/json
+```
+
+#### 2.5.1.5 Check Result
+
+
+
+
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `cache` set Status disable.
diff --git a/versioned_docs/version-2.6.1/plugin-center/common/_category_.json b/versioned_docs/version-2.6.1/plugin-center/common/_category_.json
new file mode 100644
index 00000000000..88b377b2c49
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/common/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Common",
+ "position": 6
+}
diff --git a/versioned_docs/version-2.6.1/plugin-center/common/general-context-plugin.md b/versioned_docs/version-2.6.1/plugin-center/common/general-context-plugin.md
new file mode 100644
index 00000000000..b8d6453151a
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/common/general-context-plugin.md
@@ -0,0 +1,36 @@
+---
+title: GeneralContext Plugin
+keywords: ["generalContext"]
+description: generalContext plugin
+---
+
+## Description
+
+* When making invokes to the target service, Apache ShenYu gateway also allows users to use the `generalContext` plugin to pass the service context parameters by reading the header in this request.
+
+## Plugin Setting
+
+* In `shenyu-admin` --> BasicConfig --> Plugin --> `generalContext`, set to enable.
+* If the user don't use, please disable the plugin in the background.
+
+
+
+* Introduce `generalContext` support in the pox.xml file of the gateway.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-general-context
+ ${project.version}
+
+
+```
+
+* Selectors and rules, please refer to: [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule).
+* Only those matched requests can print the information about this request.
+
+## Situation
+
+* The parameters in the request header need to be passed to the proxy server.
+* Need to replace a key in the request header and pass it to the proxy server.
diff --git a/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/_category_.json b/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/_category_.json
new file mode 100644
index 00000000000..b02214033d8
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Fault Tolerance",
+ "position": 3
+}
diff --git a/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/hystrix-plugin.md b/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/hystrix-plugin.md
new file mode 100644
index 00000000000..7e740e802c8
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/hystrix-plugin.md
@@ -0,0 +1,144 @@
+---
+title: Hystrix Plugin
+keywords: ["Hystrix"]
+description: hystrix plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Hystrix Plugin
+
+## 1.2 Appropriate Scenario
+
+* The backend service is unstable, use hystrix for protection
+
+## 1.3 Plugin functionality
+
+* Fusing the flow
+* Protect the application behind ShenYu Gateway
+* Isolation mode supports `thread` and `semaphore`.
+
+## 1.4 Plugin code
+
+* Core Module: `shenyu-plugin-hystrix`
+
+* Core Class: `org.apache.shenyu.plugin.hystrix.HystrixPlugin`
+
+## 1.5 Added Since Which shenyu version
+
+* Since ShenYu 2.4.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+* Add `hystrix` dependency in the `pom.xml` file of the gateway.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-hystrix
+ ${project.version}
+
+
+```
+
+## 2.3 Enable plugin
+
+* In `shenyu-admin`--> BasicConfig --> Plugin --> `hystrix` set to enable.
+
+## 2.4 Config plugin
+
+### 2.4.1 Plugin Config
+
+* No Config, but you should open hystrix plugin.
+
+### 2.4.2 Selector Config
+
+It is used to filter traffic for the first time and does not require handle fields.
+
+For more information on selectors and rules configuration, see [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule) , only some of the fields are covered here.
+
+
+
+### 2.4.3 Rule Config
+
+* For the final filtering of traffic, there is a rule handler logic, isolation mode supports `thread` and `semaphore`.
+
+
+
+* Hystrix handler details:
+
+ * `MinimumRequests`: the minimum number of requests required to trigger a circuit breaker.
+
+ * `ErrorThresholdPercentage`: percentage of exception occurring during that time.
+
+ * `Timeout`(ms): execution timeout.
+
+ * `MaxConcurrentRequests`: max concurrent requests.
+
+ * `Sleep`(ms): The recovery time after the circuit breaker.
+
+ * `GroupKey`: It is generally set to: `contextPath`.
+
+ * `CallBackUrl`: default url `/fallback/hystrix`.
+
+ * `CommandKey`: generally, it is set to a specific path interface.
+
+## 2.5 Examples
+
+### 2.5.1 use hystrix protect application
+
+#### 2.5.1.1 Preparation
+
+- Start ShenYu Admin
+- Start ShenYu Bootstrap
+- Start a backend service
+
+#### 2.5.1.2 Selector Config
+
+
+
+#### 2.5.1.3 Rule Config
+
+* The rules in the pictures below are test examples, actual environment depends on the specific situation.
+
+
+
+* test example
+
+```java
+@RestController
+@RequestMapping("/test")
+@ShenyuSpringMvcClient("/test/**")
+public class HttpTestController {
+ @PostMapping("/testHystrix")
+ public ResultBean ok() {
+ Random random = new Random();
+ int num = random.nextInt(100);
+ if (num > 20) {
+ throw new RuntimeException();
+ }
+ return new ResultBean(200, "ok", null);
+ }
+}
+```
+
+#### 2.5.1.4 Send Request With `Apache Jmeter`
+
+
+
+#### 2.5.1.5 Check Result
+
+
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `hystrix` set Status disable.
diff --git a/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/rate-limiter-plugin.md b/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/rate-limiter-plugin.md
new file mode 100644
index 00000000000..0f1c2a7794b
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/rate-limiter-plugin.md
@@ -0,0 +1,193 @@
+---
+title: RateLimiter Plugin
+keywords: ["rateLimiter"]
+description: rateLimiter plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* RateLimiter Plugin
+
+## 1.2 Appropriate Scenario
+
+* traffic control in gateway cluster environment
+* rate limiting according to specific rules
+* You can set to the interface level, or the parameter level. How to use it depends on your traffic configuration.
+
+## 1.3 Plugin functionality
+
+* use redis to control gateway traffic
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-ratelimiter`.
+
+* Core Class `org.apache.shenyu.plugin.ratelimiter.RateLimiterPlugin`
+* Core Class `org.apache.shenyu.plugin.ratelimiter.executor.RedisRateLimiter`
+
+## 1.5 Added Since Which shenyu version
+
+* Since ShenYu 2.4.0
+
+## 1.6 Technical Solution
+
+### 1.6.1 Using redis token bucket algorithm to limit traffic.
+
+- The system generates the token at a constant rate, and then puts the token into the token bucket.
+- The token bucket's capacity. When the bucket is full, the token put into it will be discarded.
+- Each time requests come, you need to obtain a token from the token bucket. If there are tokens, the service will be provided; if there are no tokens, the service will be rejected.
+
+* Flow Diagram：
+ 
+
+
+### 1.6.2 Using redis leaky bucket algorithm to limit traffic.
+
+- water (request) go to the leaky bucket first. The leaky bucket goes out at a fixed speed. When the flow speed is too fast, it will overflow directly (reject service)
+
+* Flow Diagram：
+ 
+
+
+### 1.6.3 Using redis sliding time window algorithm to limit traffic.
+
+- The sliding time window maintains the count value of unit time. Whenever a requests pass, the count value will be increased by 1. When the count value exceeds the preset threshold, other requests in unit time will be rejected. If the unit time has ended, clear the counter to zero and start the next round counting.
+
+* Flow Diagram：
+ 
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure
+
+
+
+## 2.2 Import pom
+
+* Add `rateLimiter` dependency in `pom.xml` file of the gateway.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-ratelimiter
+ ${project.version}
+
+
+```
+
+## 2.3 Enable plugin
+
+* In `shenyu-admin`--> BasicConfig --> Plugin --> `rateLimiter` set to enable.
+
+## 2.4 Config plugin
+
+### 2.4.1 Plugin Config
+
+
+
+* `mode`: the working mode of redis, the default is single-point mode: `standalone`, in addition to cluster
+ mode: `cluster`, sentinel mode: `sentinel`.
+
+* `master`: default is master.
+
+* `url`: configure the IP and port of the redis database, configured by colon connection, example: `192.168.1.1:6379`.
+
+* `password`: the password of the redis database, if not, you can not configure.
+
+### 2.4.2 Selector Config
+
+* Selectors and rules, please refer to: [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule)
+
+### 2.4.3 Rule Config
+
+
+
+* TokenBucket/Concurrent
+
+ * `algorithmName`: `tokenBucket`/`concurrent`.
+
+ * `replenishRate`: It is how many requests you allow users to execute per second, while not discarding any requests. This is the filling rate of token bucket.
+
+ * `burstCapacity`: it is the maximum number of requests that users are allowed to execute in one second. This is token bucket can save the number of token.
+
+ * `keyResolverName`: `whole` indicates that the traffic is limited by gateway per second, and `remoteAddress` indicates that the traffic is limited by IP per second.
+
+* LeakyBucket
+
+ * `algorithmName`: `leakyBucket`.
+
+ * `replenishRate`: The rate at which requests are executed per unit time, and the rate at which water droplets leak out of the leaky bucket.
+
+ * `burstCapacity`: The maximum number of requests that users are allowed to execute in one second. This is the amount of water in the bucket.
+
+ * `keyResolverName`: `whole` indicates that the traffic is limited by gateway per second, and `remoteAddress` indicates that the traffic is limited by IP per second.
+
+* SlidingWindow
+
+ * `algorithmName`: `slidingWindow`.
+
+ * `replenishRate`: The rate of requests per unit time, used to calculate the size of the time window.
+
+ * `burstCapacity`: The maximum number of requests in the time window (per unit time).
+
+ * `keyResolverName`: `whole` indicates that the traffic is limited by gateway per second, and `remoteAddress` indicates that the traffic is limited by IP per second.
+
+## 2.5 Examples
+
+### 2.5.1 Limit traffic with `RateLimiter` plugin in gateway cluster environment
+
+#### 2.5.1.1 Preparation
+
+- Start ShenYu Admin on `10.10.10.10:9095`
+- Start two ShenYu Bootstrap on `10.10.10.20:9195` and `10.10.10.30:9195`, and config data sync center on `10.10.10.10:9095`
+- config nginx, for example:
+
+```nginx
+upstream shenyu_gateway_cluster {
+ ip_hash;
+ server 10.1.1.1:9195 max_fails=3 fail_timeout=10s weight=50;
+ server 10.1.1.2:9195 max_fails=3 fail_timeout=10s weight=50;
+}
+
+server {
+ location / {
+ proxy_pass http://shenyu_gateway_cluster;
+ proxy_set_header HOST $host;
+ proxy_read_timeout 10s;
+ proxy_connect_timeout 10s;
+ }
+}
+```
+
+#### 2.5.1.2 Plugin/Selector/Rule Configuration
+
+- config redis configuration with ratelimiter plugin
+
+- config selector
+
+- config rule
+
+
+
+replenishRate is 3, burstCapacity is 10
+
+#### 2.5.1.3 Send Request to `Ngin`x by `Apache Jmeter`
+
+* jmeter thread group configuration
+
+
+
+* jmeter http request configuration
+
+
+
+#### 2.5.1.4 Check Result
+
+
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `rateLimiter` set Status disable.
diff --git a/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/resilience4j-plugin.md b/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/resilience4j-plugin.md
new file mode 100644
index 00000000000..f58c00b30c4
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/resilience4j-plugin.md
@@ -0,0 +1,81 @@
+---
+title: Resilience4j Plugin
+keywords: ["Resilience4j"]
+description: resilience4j plugin
+---
+
+## Description
+
+* `Resilience4j` is one of the options that supports flow control and circuit breaking.
+* `Resilience4j` supports flow control and circuit breaking functions for gateway.
+
+## Plugin Setting
+
+Select a mode to start shenyu-admin. For details, see deployment. For example, with [Local Deployment](../../deployment/deployment-local) starts the `Apache ShenYu` background management system.
+
+* In BasicConfig --> Plugin --> resilience4j, set to enable.
+* If the user don't use, please disable the plugin in the background.
+
+
+
+
+
+## Add resilience4j plugin dependency
+
+* Add `resilience4j` dependency in the `pom.xml` file of the gateway.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-resilience4j
+ ${project.version}
+
+
+```
+
+## Resilience4j Config
+
+For more information on selectors and rules configuration, see [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule) , only some of the fields are covered here.
+
+#### Selector Config
+
+It is used to filter traffic for the first time and does not require handle fields.
+
+
+
+
+#### Rule Config
+
+For the final filtering of traffic, there is a rule handler logic.
+
+
+
+* Resilience4j Processing Details
+
+ * `limitForPeriod` ：Configures the number of permissions available during one limit refresh period,default value:`50`.
+
+ * `limitRefreshPeriod` ：Configures the period of a limit refresh. After each period the rate limiter sets its permissions count back to the limitForPeriod value,default value:`500`.
+
+ * `timeoutDurationRate` ：Configures wait time(ms) a thread waits for a permission,default value:`5000`.
+
+ * `circuitEnable` ：Configures circuitBreaker enable, `0`:OFF ,`1`:ON ,default value:`0`.
+
+ * `failureRateThreshold` ：Configures the failure rate threshold in percentage,When the failure rate is equal or greater than the threshold the CircuitBreaker transitions to open and starts short-circuiting calls,default value:`50`.
+
+ * `fallbackUri` ：Configures the fallback uri.
+
+ * `minimumNumberOfCalls` ：Configures the minimum number of calls which are required (per sliding window period) before the CircuitBreaker can calculate the error rate or slow call rate,default value:`100`.
+
+ * `bufferSizeInHalfOpen`：Configures the number of permitted calls when the CircuitBreaker is half open,default value:`10`.
+
+ * `slidingWindowSize` ：Configures the size of the sliding window which is used to record the outcome of calls when the CircuitBreaker is closed,default value:`100`.
+
+ * `slidingWindowType` ：Configures the type of the sliding window which is used to record the outcome of calls when the CircuitBreaker is closed,
+ Sliding window can either be `0`:count-based or `1`:time-based.,default value:`0`.
+
+ * `timeoutDuration` ：Configures request CircuitBreaker timeout(ms),default value:`30000`.
+
+ * `waitIntervalInOpen` ：Configures the circuitBreaker time(ms) of duration,default value:`10`.
+
+ * `automaticTransitionFromOpenToHalfOpenEnabled` ：Configures automatically transition from open state to half open state,`true`:ON, `false`:OFF, default value:`false`.
diff --git a/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/sentinel-plugin.md b/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/sentinel-plugin.md
new file mode 100644
index 00000000000..9c7919098ba
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/sentinel-plugin.md
@@ -0,0 +1,215 @@
+---
+title: Sentinel Plugin
+keywords: ["Sentinel"]
+description: sentinel plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Sentinel Plugin
+
+## 1.2 Appropriate Scenario
+
+* `Sentinel` is one of the options that supports flow control and circuit breaking.
+* `Sentinel` supports flow control and circuit breaking functions for gateway.
+
+## 1.3 Plugin functionality
+
+* flow control
+* request circuit breaker and service degrade
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-sentinel`.
+
+* Core Class `org.apache.shenyu.plugin.sentinel.SentinelPlugin`
+
+## 1.5 Added Since Which shenyu version
+
+* Since 2.4.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+* Add `sentinel` dependency in the `pom.xml` file of the gateway(shenyu-bootstrap).
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-sentinel
+ ${project.version}
+
+
+```
+
+## 2.3 Enable plugin
+
+* In `shenyu-admin`--> BasicConfig --> Plugin --> `sentinel` set to enable.
+
+## 2.4 Config plugin
+
+### 2.4.1 Plugin configuration
+
+### 2.4.2 Selector configuration
+
+It is used to filter traffic for the first time and does not require `handle` fields.
+
+
+
+### 2.4.3 Rule configuration
+
+For the final filtering of traffic, there is a rule handler logic.
+
+
+
+| field | default value | field type | desc |
+|-----------------------------------------------------|--------------------|------------|----------------------------------------------------------------------------------------------------------------------------|
+| degradeRuleCount | | Doule | degrade threshold |
+| degradeRuleEnable | 1(enabled) | Integer | whether enable circuit breaking function of `sentinel` |
+| degradeRuleGrade | 0(slow call ratio) | Integer | circuit breaker strategy, support RT of seconds level/ Error Ratio of seconds level/ Error Count of minutes level strategy |
+| degradeRuleMinRequestAmount | 5 | Integer | circuit breaker min request amount |
+| degradeRuleSlowRatioThreshold | 1.0d | Double | slow ratio threshold of degrading |
+| degradeRuleStatIntervals | 1 | Integer | status intervals of degrade |
+| degradeRuleTimeWindow | | Integer | time of degrading(unit: second) |
+| flowRuleControlBehavior | 0(direact reject) | Integer | effect(reject directly/ queue/ slow start up), it do not support flow control by invocation relation. |
+ | flowRuleControlBehavior-direct rejection by default | | | |
+| flowRuleControlBehavior-warm up | | | |
+| flowRuleControlBehavior-constant speed queuing | | | |
+| flowRuleControlBehavior-preheating uniformly queued | | | |
+| flowRuleMaxQueueingTimeMs | 500ms | Integer | Maximum queuing time (valid in "preheating uniformly queued", "constant speed queuing" mode) |
+| flowRuleWarmUpPeriodSec | 10 | Integer | Cold start warm-up time (seconds) (valid in "preheating uniformly queued" "warm up" mode) |
+| flowRuleCount | | Integer | sentinel flow control count |
+| flowRuleEnable | 1(enabled) | Integer | whether enable sentinel flow control function. |
+| flowRuleGrade | 1(QPS) | Integer | type of current limit threshold(QPS or Thread Count)。 |
+| fallbackUri | | String | degraded uri after circuit breaking. |
+
+## 2.5 Examples
+
+### 2.5.1 Using sentinel for flow control
+
+#### 2.5.1.1 Plugin configuration
+
+For more information on selectors and rules configuration, see [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule) , only some of the fields are covered here.
+
+* In `shenyu-admin`--> BasicConfig --> Plugin --> `sentinel` set to enable.
+
+#### 2.5.1.2 Selector configuration
+
+
+
+#### 2.5.1.3 Rule configuration
+
+
+
+just use qps flow control strategy, and qps is 10, reject strategy is directly reject.
+
+the code is as follows:
+
+```java
+@RestController
+@RequestMapping("/order")
+@ShenyuSpringMvcClient("/order")
+public class OrderController {
+
+ /**
+ * Save order dto.
+ *
+ * @param orderDTO the order dto
+ * @return the order dto
+ */
+ @PostMapping("/save")
+ @ShenyuSpringMvcClient("/save")
+ public OrderDTO save(@RequestBody final OrderDTO orderDTO) {
+ orderDTO.setName("hello world save order");
+ return orderDTO;
+ }
+}
+```
+
+#### 2.5.1.4 request by `Apache Jmeter`
+
+* Jmeter thead group config
+
+
+
+* Jmeter http request config
+
+
+
+#### 2.5.1.5 Check result
+
+
+
+### 2.5.2 Using sentinel for request circuit breaker
+
+#### 2.5.2.1 Plugin configuration
+
+* In `shenyu-admin`--> BasicConfig --> Plugin --> `sentinel` set to enable.
+
+#### 2.5.2.2 Selector configuration
+
+
+
+#### 2.5.2.3 Rule configuration
+
+
+
+when degrade strategy is `exception number`, `degradeRuleSlowRatioThreshold` is not effective. When the minimum number of requests per unit of time is 5, and the request happens exception great than 3, it will trigger the circuit breaker.
+
+when degrade strategy is `slow call ratio`, `degradeRuleSlowRatioThreshold` is effective, `degradeRuleCount` means RT(e.g. 200).
+
+the code is as follows:
+
+```java
+@RestController
+@RequestMapping("/order")
+@ShenyuSpringMvcClient("/order")
+public class OrderController {
+
+ /**
+ * Save order dto.
+ *
+ * @param orderDTO the order dto
+ * @return the order dto
+ */
+ @PostMapping("/save")
+ @ShenyuSpringMvcClient("/save")
+ public OrderDTO save(@RequestBody final OrderDTO orderDTO) {
+
+ Random random = new Random();
+ int num = random.nextInt(100);
+ if (num > 40) {
+ throw new RuntimeException("num great than 20");
+ }
+ orderDTO.setName("hello world save order");
+ return orderDTO;
+ }
+
+}
+```
+
+#### 2.5.2.4 request by `Apache Jmeter`
+
+* Jmeter thead group config
+
+
+
+* Jmeter http request config
+
+
+
+#### 2.5.2.5 Check result
+
+
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `sentinel` set Status disable.
diff --git a/versioned_docs/version-2.6.1/plugin-center/http-process/_category_.json b/versioned_docs/version-2.6.1/plugin-center/http-process/_category_.json
new file mode 100644
index 00000000000..77ac2bace2f
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/http-process/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Http Process",
+ "position": 1
+}
diff --git a/versioned_docs/version-2.6.1/plugin-center/http-process/contextpath-plugin.md b/versioned_docs/version-2.6.1/plugin-center/http-process/contextpath-plugin.md
new file mode 100644
index 00000000000..8a05fe6c1fb
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/http-process/contextpath-plugin.md
@@ -0,0 +1,127 @@
+---
+title: ContextPath Plugin
+keywords: ["contextPath"]
+description: contextPath plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* ContextPath Plugin
+
+## 1.2 Appropriate Scenario
+
+* Different services can do traffic governance of services by setting different context paths.
+
+## 1.3 Plugin functionality
+
+* Set the context path for service.
+* When the interface is called, the plug-in uniformly prefixes the interface address of the service.
+
+## 1.4 Plugin Code
+
+* Core module ```shenyu-plugin-context-path```
+* Core class ```org.apache.shenyu.plugin.context.path.ContextPathPlugin```
+
+## 1.5 Added since which shenyu version
+
+* 2.3.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+- import maven config in shenyu-bootstrap project's `pom.xml` file.
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-gateway
+ ${project.version}
+
+```
+
+## 2.3 Enable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `contextPath` set Status enable.
+
+
+
+## 2.4 Config plugin
+
+- Set client project's contextPath.
+
+
+
+- Selector and rule config, please refer: [Selector and rule config](../../user-guide/admin-usage/selector-and-rule).
+- shenyu-admin contextPath plugin config, config contextPath and addPrefix, contextPath defines the value of contextPath,
+- and addPrefix defines the prefix that needs to be automatically added when the interface is called.
+
+
+
+## 2.5 Examples
+
+### 2.5.1 Example set service context path
+
+#### 2.5.1.1 Refer [Local Deployment](https://shenyu.apache.org/docs/deployment/deployment-local/) to start admin and bootstrap.
+
+#### 2.5.1.2 Refer 2.2 to import pom and restart bootstrap.
+
+#### 2.5.1.3 Refer 2.3 to enable plugin.
+
+#### 2.5.1.4 Client project config contextPath.
+
+Client project can directly use [shenyu-examples-http](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http), and config contextPath in application.yml.
+
+
+
+- After the configuration is completed, and start client project, you can see that there is an additional context selector and rule configuration in shenyu-admin.
+
+
+
+#### 2.5.1.5 Call Interface
+
+
+
+### 2.5.2 Example add prefix
+
+#### 2.5.2.1 Refer [Local Deployment](https://shenyu.apache.org/docs/deployment/deployment-local/) to start admin and bootstrap.
+
+#### 2.5.2.2 Refer 2.2 to import pom and restart bootstrap.
+
+#### 2.5.2.3 Refer 2.3 to enable plugin.
+
+#### 2.5.2.4 Client project config contextPath.
+
+For client project we can directly use [shenyu-examples-http](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http), and config contextPath in application.yml.
+
+
+
+- After the configuration is completed, start client project, you can see that there is an additional context selector and rule configuration in shenyu-admin.
+
+
+
+#### 2.5.2.5 Config addPrefix
+
+
+
+#### 2.5.2.6 Modify the value of uri in the selector and condition configuration to delete the addPrefix part.
+
+Since this example uses the service of the http protocol, we need to modify the divide plugin.
+
+
+
+#### 2.5.2.5 Call Interface
+
+
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `contextPath` set Status disable.
+
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/http-process/modifyresponse-plugin.md b/versioned_docs/version-2.6.1/plugin-center/http-process/modifyresponse-plugin.md
new file mode 100644
index 00000000000..06dd2d0bdf5
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/http-process/modifyresponse-plugin.md
@@ -0,0 +1,146 @@
+---
+title: ModifyResponse Plugin
+keywords: ["modifyResponse"]
+description: modifyResponse plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* ModifyResponse Plugin
+
+## 1.2 Appropriate Scenario
+
+* This plugin is used for modifying HTTP response status code, response headers or response body parameters.
+
+## 1.3 Plugin functionality
+
+* Reset HTTP response status code
+* Add, set, replace or remove HTTP response headers.
+* Add, replace or remove HTTP response body(JSON) parameters.
+
+## 1.4 Plugin Code
+
+* Core module ```shenyu-plugin-modify-response```
+* Core class ```org.apache.shenyu.plugin.modify.response.ModifyResponsePlugin```
+
+## 1.5 Added since which shenyu version
+
+* 2.4.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+- import maven config in shenyu-bootstrap project's `pom.xml` file.
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-gateway
+ ${project.version}
+
+```
+
+## 2.3 Enable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `modifyResponse` set Status enable.
+-
+
+
+## 2.4 Config plugin
+
+* Selector and rule config, please refer: [Selector and rule config](../../user-guide/admin-usage/selector-and-rule).
+* In `shenyu-admin` --> `PluginList` --> `HttpProcess` --> `modifyResponse`, add selector config first，then add rule config：
+ * Add selector config
+ 
+ * Add rule config
+ 
+
+## 2.5 Examples
+
+Here is an example of client project [shenyu-examples-http](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http).
+
+### 2.5.1 Example reset HTTP response status code
+
+#### 2.5.1.1 Refer [Local Deployment](https://shenyu.apache.org/docs/deployment/deployment-local/) to start admin and bootstrap.
+
+#### 2.5.1.2 Refer 2.2 to import pom and restart bootstrap.
+
+#### 2.5.1.3 Refer 2.3 to enable plugin.
+
+#### 2.5.1.4 Refer 2.4 to add plugin config.
+
+Add plugin config:
+
+
+
+#### 2.5.1.5 Call Interface
+
+
+
+### 2.5.2 Example modify HTTP response headers
+
+#### 2.5.2.1 Refer [Local Deployment](https://shenyu.apache.org/docs/deployment/deployment-local/) to start admin and bootstrap.
+
+#### 2.5.2.2 Refer 2.2 to import pom and restart bootstrap.
+
+#### 2.5.2.3 Refer 2.3 to enable plugin.
+
+#### 2.5.2.4 Refer 2.4 to add plugin config.
+
+Add plugin config:
+
+
+
+#### 2.5.2.5 Call Interface
+
+
+
+### 2.5.3 Example modify HTTP response body
+
+#### 2.5.3.1 Refer [Local Deployment](https://shenyu.apache.org/docs/deployment/deployment-local/) to start admin and bootstrap.
+
+#### 2.5.3.2 Refer 2.2 to import pom and restart bootstrap.
+
+#### 2.5.3.3 Refer 2.3 to enable plugin.
+
+#### 2.5.3.4 Refer 2.4 to add plugin config.
+
+Add plugin config:
+
+
+
+#### 2.5.3.5 Call Interface
+
+
+
+## 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `modifyResponse` set Status disable.
+
+
+
+## 4. rule parameter list
+
+for modifying status code:
+
+* `statusCode`: reset response status code
+
+for modifying response headers:
+
+* `addHeaders`: add response headers, `k-v` format
+* `setHeaders`: set response headers, `k-v` format
+* `replaceHeaderKeys`: replace response headers，`key` is matching to the header key that should be replacing, value is target value after replacing
+* `removeHeaderKeys`: remove response headers，`key` is matching to the header key that should be removing
+
+for modifying response body:
+
+* `addBodyKeys`: add response body parameters
+* `replaceBodyKeys`: replace response body parameters，`key` is matching to the body(JSON) key that should be replacing, value is target value after replacing
+* `removeBodyKeys`: remove response body parameters，`key` is matching to the body(JSON) key that should be removing
diff --git a/versioned_docs/version-2.6.1/plugin-center/http-process/parammapping-plugin.md b/versioned_docs/version-2.6.1/plugin-center/http-process/parammapping-plugin.md
new file mode 100644
index 00000000000..caa04ab2722
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/http-process/parammapping-plugin.md
@@ -0,0 +1,109 @@
+---
+title: ParamMapping Plugin
+keywords: ["paramMapping-plugin"]
+description: paramMapping-plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* ParamMapping Plugin
+
+## 1.2 Appropriate Scenario
+
+* Add/remove/replace certain fixed parameters to the request
+
+## 1.3 Plugin functionality
+
+* `paramMapping` is used to edit your request parameters.
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-param-mapping`
+
+* Core Class `org.apache.shenyu.plugin.param.mapping.ParamMappingPlugin`
+
+## 1.5 Added Since Which shenyu version
+
+* Since ShenYu 2.4.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+* Introduce `paramMapping` dependency in the pom.xml file of the gateway.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-param-mapping
+ ${project.version}
+
+
+```
+
+## 2.3 Enable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `paramMapping` set Status enabled.
+
+## 2.4 Config plugin
+
+### 2.4.1 Plugin Config
+
+* you should open this plugin when using.
+
+### 2.4.2 Selector Config
+
+* Selectors and rules, please refer to:[Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule)。
+
+* Only those matched requests can be modified your request body.
+
+### 2.4.3 Rule Config
+
+
+* param details:
+ * `addParameterKeys`: add a new `key-value` on body
+ * `replaceParameterKeys`: replace request body's `key` ，`key` is the value to be replaced，`value` is the value after replacement
+ * `removeParameterKeys`: remove a body `key`
+
+* param_mapping modify the request body is achieved through `JSONPath` , `$.` represents the root directory.
+
+## 2.5 Examples
+
+### 2.5.1 Add parameters in request
+
+#### 2.5.1.1 Config Plugin
+
+* you should open the plugin when using.
+
+#### 2.5.1.2 Selector Config
+
+#### 2.5.1.3 Rule Config
+
+
+
+use the configuration，unopened the plugin，request body is:
+
+```json
+{"id":3,"data":{"value":"18","age":"36"}}
+```
+
+#### 2.5.1.4 Check Result
+
+open the plugin，the final request body is
+
+```json
+{"name":"shenyu","userId":3,"data":{"age":"36"}}
+```
+
+add a new key-value `name:shenyu`,replace the key `id` to `userId`, remove the key `data.value` .
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `paramMapping` set Status disable.
diff --git a/versioned_docs/version-2.6.1/plugin-center/http-process/redirect-plugin.md b/versioned_docs/version-2.6.1/plugin-center/http-process/redirect-plugin.md
new file mode 100644
index 00000000000..3e61f08f813
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/http-process/redirect-plugin.md
@@ -0,0 +1,94 @@
+---
+title: Redirect Plugin
+keywords: ["redirect"]
+description: redirect plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+ - Redirect Plugin
+
+## 1.2 Appropriate Scenario
+
+ - As the name suggests, the `redirect` plugin is to re-forward and redirect `uri`.
+
+## 1.3 Plugin functionality
+
+ - When the Apache ShenYu gateway makes proxy calls to the target service, it also allows users to use the `redirect` plugin to redirect requests.
+
+## 1.4 Plugin code
+
+ Core module ```shenyu-plugin-context-redirect```
+ Core class ```org.apache.shenyu.plugin.redirect.RedirectPlugin```
+
+## 1.5 Added Since Which shenyu version
+
+ before 2.2.0 .
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+ - import maven config in shenyu-bootstrap project's `pom.xml` file.
+
+ ```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-redirect
+ ${project.version}
+
+
+ ```
+
+## 2.3 Enable plugin
+
+ - In `shenyu-admin` --> BasicConfig --> Plugin --> `Redirect` set Status enable.
+
+
+
+## 2.4 Config plugin
+
+ - Selector and rule config, please refer: [Selector and rule config](../../user-guide/admin-usage/selector-and-rule).
+ - In `shenyu-admin` --> `PluginList` --> `HttpProcess` --> `Redirect`, add selector config first，then add rule config：
+ - Add selector config
+
+
+ - Add rule config
+
+
+
+## 2.5 Examples
+
+### 2.5.1 Redirect
+
+ - When we configure a custom path in `Rule`, it should be a reachable service path.
+ - When the request is matched, the `ShenYu Gateway` will perform the `308` service jump according to the customized path.
+ 1. Refer [Local Deployment](https://shenyu.apache.org/docs/deployment/deployment-local/) to start admin and bootstrap.
+ 2. Refer 2.2 to import pom and restart bootstrap.
+ 3. Refer 2.3 to enable plugin.
+ 4. Refer 2.4 and [Selector and rule config](../../user-guide/admin-usage/selector-and-rule).
+ 5. Invoke interface: [demo](http://localhost:9195/http)
+ - Invoke the interface declared by selectors and rules will redirect to the specified path.
+ - In this demo, it will jump to [ShenYu official website](https://shenyu.apache.org)
+
+
+
+### 2.5.2 Gateway's own interface forwarding
+
+ - When the matching rules are met, the service will use the `DispatcherHandler` internal interface for forwarding.
+ - To implement the gateway's own interface forwarding, we need to use `/` as the prefix in the configuration path. The specific configuration is as shown in the figure below.
+
+
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `Redirect` set Status disable.
+
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/http-process/request-plugin.md b/versioned_docs/version-2.6.1/plugin-center/http-process/request-plugin.md
new file mode 100644
index 00000000000..b3757c51204
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/http-process/request-plugin.md
@@ -0,0 +1,91 @@
+---
+title: Request Plugin
+keywords: ["request"]
+description: request plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Request Plugin
+
+## 1.2 Appropriate Scenario
+
+* The request plugin is able to make customized changes to the request parameters of `uri`.
+
+## 1.3 Plugin functionality
+
+* The `Apache ShenYu` gateway allows users to use the `request` plugin to add, modify, and remove request headers to request parameters, request headers, and `Cookie` when proxying a target service.
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-request`
+
+* Core Class `org.apache.shenyu.plugin.request.RequestPlugin`
+
+## 1.5 Added Since Which shenyu version
+
+* Since ShenYu 2.4.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+- Import maven config in shenyu-bootstrap project's `pom.xml` file, which is already added by default.
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-request
+ ${project.version}
+
+```
+
+## 2.3 Enable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `request` set Status enabled.
+
+ > If there is an option to configure a `ruleHandlePageType` on the page here, you can configure any string, e.g. `custom`, which has no effect on the request, and will be removed in later versions.
+
+
+
+
+## 2.4 Config plugin
+
+- selectors and rules, only requests that match are forwarded and redirected, see the [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule)
+- `shenyu-admin` Plugin --> `HttpProcess` --> `Request`. Add the selector first, then add the rule：
+- Add the selector:
+
+
+
+- Add the rule
+
+
+
+## 2.5 Examples
+
+### 2.5.1 Adding request parameters
+
+- When we configure a custom path in `Rules`, it should be a reachable service path.
+- When a request is matched, based on the customized path, the `Apache ShenYu` gateway performs a service hop.
+
+1. Refer to [Local Deployment](https://shenyu.apache.org/docs/deployment/deployment-local)启动 admin 和网关
+2. Refer to 2.2 importing pom and restarting the gateway.
+3. Refer to 2.3 enabling Plugin
+4. Start the project [shenyu-examples-http](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http)
+5. Refer to 2.4 and [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule), configuring plugin rules.
+6. Call interface：[http-test-api.http](https://github.com/apache/shenyu/blob/master/shenyu-examples/shenyu-examples-http/src/main/http/http-test-api.http)
+- Calling the interface declared by the selector and rule will see the request parameters configured in the request plugin.
+
+
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `request` set Status disable.
+-
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/http-process/rewrite-plugin.md b/versioned_docs/version-2.6.1/plugin-center/http-process/rewrite-plugin.md
new file mode 100644
index 00000000000..adc096f0299
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/http-process/rewrite-plugin.md
@@ -0,0 +1,103 @@
+---
+title: Rewrite Plugin
+keywords: ["rewrite"]
+description: rewrite plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Rewrite Plugin
+
+## 1.2 Appropriate Scenario
+
+* The request uri can be different from the target service by rewriting the path.
+
+## 1.3 Plugin functionality
+
+* This plugin is used to rewrite the request uri.
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-rewrite`
+
+* Core Class `org.apache.shenyu.plugin.rewrite.RewritePlugin`
+
+## 1.5 Added Since Which shenyu version
+
+* Since ShenYu 2.4.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+- Import maven config in shenyu-bootstrap project's `pom.xml` file..
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-rewrite
+ ${project.version}
+
+```
+
+## 2.3 Enable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `rewrite` set Status enabled.
+
+
+## 2.4 Config plugin
+
+### 2.4.1 Plugin Config
+
+* Enable the plugin before using.
+* Disable the plugin if don't use.
+
+### 2.4.2 Selector Config
+
+* Please refer to: [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule).
+
+### 2.4.3 Rule Config
+
+
+
+* Param details:
+ * `regex`: The regular expression that matches the part of uri to be rewrited.
+ * `replace`: The content of replacement.
+
+## 2.5 Examples
+
+### 2.5.1 Example for rewriting uri
+
+#### 2.5.1.1 Run the shenyu-examples-http project
+
+* Use [shenyu-examples-http](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http), please refer to [Run the shenyu-examples-http project](../../quick-start/quick-start-http#run-the-shenyu-examples-http-project)
+
+#### 2.5.1.1 Plugin Config
+
+* Refer to [2.4.1](#241-plugin-config) to configure plugin.
+
+#### 2.5.1.2 Selector Config
+
+* Refer to [2.4.2](#242-selector-config) to configure selector
+
+#### 2.5.1.3 Rule Config
+
+
+
+The request `/http/hello` would be rewritten to `/hi`
+
+#### 2.5.1.4 Check Result
+
+Use some tool (such as Postman) to make a request:
+
+
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `rewrite` set Status disable.
diff --git a/versioned_docs/version-2.6.1/plugin-center/mock/_category_.json b/versioned_docs/version-2.6.1/plugin-center/mock/_category_.json
new file mode 100644
index 00000000000..e4f13a148a9
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/mock/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Mock",
+ "position": 8
+}
diff --git a/versioned_docs/version-2.6.1/plugin-center/mock/mock-plugin.md b/versioned_docs/version-2.6.1/plugin-center/mock/mock-plugin.md
new file mode 100644
index 00000000000..9c1c55ef7c0
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/mock/mock-plugin.md
@@ -0,0 +1,178 @@
+---
+title: Mock Plugin
+keywords: ["mock"]
+description: mock plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Mock Plugin
+
+## 1.2 Appropriate Scenario
+
+* Specify the status code and response body for the request to facilitate testing.
+
+## 1.3 Plugin functionality
+
+* Set the status code and body of the request.
+* Support configuration `${}` placeholder to automatically generate data.
+
+* **Note:** In order to support a more flexible data generation method, the mock plug-in supports users to use SpEL expressions to generate mock data. Using SpEL expressions may lead to the risk of executing malicious scripts or applying destructive programs. We recommend that you be extra careful when using them, use them in a safe environment as much as possible, such as an intranet environment, and follow security best practices.
+
+## 1.4 Plugin Code
+
+* Core module ```shenyu-plugin-mock```
+* Core class ```org.apache.shenyu.plugin.mock.MockPlugin```
+
+## 1.5 Added since which shenyu version
+
+* 2.5.0
+
+# 2. How to use plugin
+
+## 2.1 Import pom
+
+- import maven config in shenyu-bootstrap project's `pom.xml` file.
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-mock
+ ${project.version}
+
+```
+
+## 2.2 Enable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `mock` set Status enable.
+
+
+
+## 2.3 Config plugin
+
+- Selector and rule config, please refer: [Selector and rule config](../../user-guide/admin-usage/selector-and-rule).
+- shenyu-admin mock plugin configuration, supports configuring httpStatusCode and responseContent
+ - httpStatusCode:the status code of the request.
+ - responseContent:the response body of the request,support configuring `${}` placeholders to generate random data.
+
+
+
+## 2.4 `${}` supported syntax
+
+**~~`${int|min-max}`~~**
+- **Description:** Generate random integers from `min` to `max`, inclusive of `min` and `max`.
+- **Example:** `${int|10-20}`
+
+**~~`${double|min-max|format}`~~**
+- **Description:** Generate random floating point numbers from `min` to `max`, formatted according to `format`.
+- **Example:** `${double|10-20}` , `${double|10-20.5|%.2f}`
+
+**~~`${email}`~~**
+- **Description:** Generate random email addresses.
+
+**~~`${phone}`~~**
+- **Description:** Generate random 13-digit mobile number.
+
+**~~`${zh|min-max}`~~**
+- **Description:** Generate random Chinese strings of length `min` to `max`.
+- **Example:** `${zh|10-20}`
+
+**~~`${en|min-max}`~~**
+- **Description:** Generate random English strings of length `min` to `max`.
+- **Example:** `${en|10-20}`
+
+**~~`${bool}`~~**
+- **Description:** Generate a random `boolean` value i.e. `true` or `false`.
+
+**~~`${list|[arg1,arg2...]}`~~**
+- **Description:** Randomly returns any value in a list as a string.
+- **Example:** `${list|[gril,boy]}` will return `boy` or `girl`
+
+**~~`${current|format}`~~**
+- **Description:** Returns the current time and uses `format` to format, `format` can be default, the default is `YYYY-MM-dd HH:mm:ss`.
+- **Example:** `${current}`，`${current|YYYY-MM-dd}`
+
+**~~`${array|item|length}`~~**
+- **Description:** According to the `item` format definition, an array of length `length` can be generated. All the above data generation rules can be nested in `item`, and the result will be automatically added with `[]`.
+- **Example:** `${array|{"name":"test"}|3}` result is `[{"name":"test"},{"name":"test"},{"name":"test"}]`，`${array|{"age":${int|18-65}}|3}`.
+
+**${expression|expression}**
+
+`Spel` expressions are currently supported with built-in functions and arguments, which fully replace the old ${} syntax
+
+- **`${expression|#int(min,max)}`**
+
+ - **Description:** Generate random integers from `min` to `max`, inclusive of `min` and `max`.
+
+ - **Example：** `${expression|#int(1,2)}`
+
+- **`${expression|#double(min,max)}`**
+
+ - **Description:** Generate random floating point numbers from `min` to `max`, formatted according to `format`.
+ - **Example:**`${expression|#double(10.5,12.0)}`,`${expression|#double(10.5,12.0,'￥%.2f')}`
+
+- **`${expression|#email()}`**
+
+ - **Description:** Generate random email addresses.
+
+- **`${expression|#phone()}`**
+
+ - **Description:** Generate random 13-digit mobile number.
+
+- **`${expression|zh(min,max)}`**
+
+ - **Description:** Generate random Chinese strings of length `min` to `max`.
+ - **Example：** `${expression|#zh(1,10)}`
+
+- **`${expression|#bool()}`**
+
+ - **Description:** Generate a random `boolean` value i.e. `true` or `false`.
+
+- **`${expression|#oneOf(arg1,arg2...)}`**
+
+ - **Description:** Randomly returns any value in a list.
+ - **Example：** `${expression|#oneOf('shenyu','number',1)}` will return `'shenyu'` or `'number'`or`1`
+
+- **`${expression|current()}`**
+
+ + **Description:** Returns the current time and uses `format` to format, `format` can be default, the default is `YYYY-MM-dd HH:mm:ss`.
+ + **Example：** `${expression|#current()}`，`${expression|#current('YYYY-MM-dd')}`
+
+- **`${expression|#array(item,length)}`**
+
+ - **Description:** According to the `item` format definition, an array of length `length` can be generated.
+
+ - **Example:** `expression|#array('shenyu',3)` would generate `["shenyu","shenyu","shenyu"]`.
+
+ You can use it nested like`${expression|#array(#bool(),2)}`or`${expression|#array(#array('shenyu',2),2)}`
+
+- **`${expression|#req}`**
+
+ - **Description:** Req is built-in request parameters ,which can generate response data based on request content
+ - **Example:**`${expression|#req.method}`、`${expression|#req.queries['query_name']}`、`${req.queries.query_name}`、`${expression|#req.uri}`。`jsonPath` is used when the request body is json . For example ,when the request body is `{"name":"shenyu"}`，`${expression|#req.json.name}`would return "shenyu"
++ **`${expression|spel}`**
+
+ + **Description**：Use Spel expressions directly to generate data
+ + **Example**：`${expression|T(java.time.LocalDate).now()}`、`${expression|1==1}`
+
+It is recommended to use the new '${}' syntax. The old syntax may be removed at an later date.
+
+Function replaceable table:
+
+| old | new |
+| :------------------------- | :---------------------------------- |
+| ${int\|min-max} | ${expression\|#int(min,max)} |
+| ${double\|min-max\|format} | ${expression\|#double(min,max)} |
+| ${email} | ${expression\|#email()} |
+| ${phone} | ${expression\|#phone()} |
+| ${zh\|min-max} | ${expression\|#zh(min,max)} |
+| ${en\|min-max} | ${expression\|#en(min,max)} |
+| ${list\|[arg1,arg2...]} | ${expression\|#oneOf(arg1,agr2...)} |
+| ${current\|format} | ${expression\|#current(format)} |
+| ${bool} | ${expression\|#bool()} |
+| ${array\|item\|length} | ${expression#array(item,length)} |
+
+**You do not need to use add `""` on both sides of `${}`, the generated content will be prefixed and suffixed according to the definition of generator**
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/observability/_category_.json b/versioned_docs/version-2.6.1/plugin-center/observability/_category_.json
new file mode 100644
index 00000000000..5a1e175c459
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/observability/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Observability",
+ "position": 5
+}
diff --git a/versioned_docs/version-2.6.1/plugin-center/observability/logging-aliyun-sls.md b/versioned_docs/version-2.6.1/plugin-center/observability/logging-aliyun-sls.md
new file mode 100644
index 00000000000..a4f8de782e0
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/observability/logging-aliyun-sls.md
@@ -0,0 +1,139 @@
+---
+title: Logging-Aliyun-Sls Plugin
+keywords: ["logging"]
+description: logging plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Logging-AliyunSls Plugin
+
+## 1.2 Appropriate Scenario
+
+* collect http request information to aliyun sls, analysis request information by aliyun sls platform.
+
+## 1.3 Plugin functionality
+
+* The gateway receives requests from the client, forwards them to the server, and returns the server results to the client. The gateway can record the details of each request，
+* the plugin records access logs and sends to aliyun sls platform.
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-logging-aliyun-sls`
+
+* Core Class `org.apache.shenyu.plugin.aliyun.sls.LoggingAliYunSlsPlugin`
+* Core Class `org.apache.shenyu.plugin.aliyun.sls.client.AliyunSlsLogCollectClient`
+
+## 1.5 Added Since Which shenyu version
+
+ShenYu 2.5.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+- import maven config in shenyu-bootstrap project's `pom.xml` file.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-logging-aliyun-sls
+ ${project.version}
+
+
+```
+
+## 2.3 Enable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `loggingAliyunSls` set Status enable.
+
+## 2.4 Config plugin
+
+### 2.4.1 Plugin configuration
+
+
+
+| config-item | type | description | remarks |
+| :-------------- | :------ | :----------------------------------------------------------- | :----------------- |
+| accessId | String | accessId | must |
+| accesskey | String | accesskey | must |
+| host | String | host name, example:cn-guangzhou.log.aliyuncs.com | must |
+| projectName | String | log project name | optional, default shenyu |
+| logStoreName | String | log store name | optional, default shenyu-logstore |
+| topic | String | aliyun sls log topic | optional, default shenyu-topic |
+| ttlInDay | Integer | ttl times in one day | optional, default 3 |
+| shardCount | Integer | aliyun sls log shard count | optional, default 10 |
+| sendThreadCount | Integer | send log to aliyun sls thread number | optional, default 1 |
+| ioThreadCount | Integer | io thread count | optional, default 1 |
+| sampleRate | String | sample consume rate | optional, default 1 |
+| maxRequestBody | Integer | max request body | optional, default 524288 |
+| maxResponseBody | Integer | max response body | optional, default 524288 |
+| bufferQueueSize | Integer | consume log queue size | optional, default 50000 |
+
+
+### 2.4.2 Configuration Selectors and Rules
+
+* Selector and rule Config. Please refer: [Selector and rule config](../../user-guide/admin-usage/selector-and-rule.md).
+
+## 2.5 Logging Info
+
+collect request info as follows
+
+| Field Name | Meaning | Description | Remarks |
+|:----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:------------------------------|:----|
+| clientIp | Client IP | | |
+| timeLocal | Request time string, format: yyyy-MM-dd HH:mm:ss.SSS | | |
+| method | request method (different rpc type is not the same, http class for: get, post wait, rpc class for the interface name) | | |
+| requestHeader | Request header (json format) | | |
+| responseHeader | Response header (json format) | | |
+| queryParams | Request query parameters | | |
+| requestBody | Request Body (body of binary type will not be captured) | | |
+| requestUri | Request uri | | |
+| responseBody | Response body | | |
+| responseContentLength | Response body size | | |
+| rpcType | rpc type | | |
+| status | response status | | |
+| upstreamIp | Upstream (program providing the service) IP | | |
+| upstreamResponseTime | Time taken by the upstream (program providing the service) to respond to the request (ms ms) | | |
+| userAgent | Requested user agent | | |
+| host | The requested host | | |
+| module | Requested modules | | |
+| path | The requested path | | |
+| traceId | Requested Link Tracking ID | Need to access link tracking plugins, such as skywalking,zipkin | |
+
+## 2.6 Examples
+
+### 2.6.1 Collect Http Log by aliyun sls platform
+
+#### 2.6.1.1 Plugin Configuration
+
+* Open the plugin and configure aliyun-sls, configure it as follows.
+
+
+
+#### 2.6.1.2 Selector Configuration
+
+
+
+#### 2.6.1.3 Rule Configuration
+
+
+
+#### 2.6.1.4 Send Request
+
+
+
+#### 2.6.1.5 Aliyun sls Platform Display
+
+
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `loggingAliyunSls` set Status disable.
diff --git a/versioned_docs/version-2.6.1/plugin-center/observability/logging-elasticsearch.md b/versioned_docs/version-2.6.1/plugin-center/observability/logging-elasticsearch.md
new file mode 100644
index 00000000000..8354a5b7006
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/observability/logging-elasticsearch.md
@@ -0,0 +1,183 @@
+---
+title: Logging-ElasticSearch Plugin
+keywords: ["Logging", "ElasticSearch"]
+description: Logging-ElasticSearch Plugin
+---
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Logging-ElasticSearch Plugin
+
+## 1.2 Appropriate Scenario
+
+* collect http request info to elasticsearch, query or display request info by another application(kibana).
+
+## 1.3 Plugin functionality
+
+>`Apache ShenYu` The gateway receives requests from the client, forwards them to the server, and returns the server results to the client. The gateway can record the details of each request，
+>The list includes: request time, request parameters, request path, response result, response status code, time consumption, upstream IP, exception information waiting.
+>Shenyu gateway can record access logs through logging-elasticsearch-plugin and send access logs to elasticsearch database.
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-logging-elasticsearch`
+
+* Core Class `org.apache.shenyu.plugin.logging.elasticsearch.LoggingElasticSearchPlugin`
+* Core Class `org.apache.shenyu.plugin.logging.elasticsearch.client.ElasticSearchLogCollectClient`
+
+## 1.5 Added Since Which shenyu version
+
+* Since 2.5.0
+
+## 1.6 Technical Solutions
+
+* Architecture Diagram
+
+
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+* Add the dependency of logging-elasticsearch to the Shenyu-bootstrap-module 's `pom.xml` file.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-logging-elasticsearch
+ ${project.version}
+
+
+```
+
+## 2.3 Enable plugin
+
+* In `shenyu-admin` --> Basic Configuration --> Plugin Management --> `loggingElasticSearch`, configure the ElasticSearch parameter and set it to on.
+
+## 2.4 Config plugin
+
+### 2.4.1 Open the plugin and configure elasticsearch, configure it as follows.
+
+
+
+- The individual configuration items are described as follows:
+
+| config-item | type | description | remarks |
+|:----------------| :------ | :----------------------------------------------------------- | :---------------------------------- |
+| host | String | host name | must |
+| port | String | port num | must |
+| sampleRate | String | Sampling rate, range 0~1, 0: off, 0.01: acquisition 1%, 1: acquisition 100% | Optional, default 1, all collection |
+| compressAlg | String | Compression algorithm, no compression by default, currently supports LZ4 compression | Optional, no compression by default |
+| maxResponseBody | Ingeter | Maximum response size, above the threshold no response will be collected | Optional, default 512KB |
+| maxRequestBody | Ingeter | Maximum request body size, above the threshold no request body will be collected | Optional, default 512KB |
+Except for host, port, all others are optional, in most cases only these 3 items need to be configured.
+
+### 2.4.2 Configuring Selectors and Rulers
+
+For detailed configuration of selectors and rules, please refer to: [Selector and rule management](../../user-guide/admin-usage/selector-and-rule)。
+In addition sometimes a large gateway cluster corresponds to multiple applications (business), different applications (business) corresponds to different topics, related to isolation,
+then you can configure different topics (optional) and sampling rate (optional) by selector, the meaning of the configuration items as shown in the table above.
+The operation is shown below:
+
+
+
+## 2.5 Logging information
+
+The fields of the captured access log are as follows.
+
+| Field Name | Meaning | Description | Remarks |
+| :-------------------- | :----------------------------------------------------------: | :----------------------------------------------------------- | :------ |
+| clientIp | Client IP | | |
+| timeLocal | Request time string, format: yyyy-MM-dd HH:mm:ss.SSS | | |
+| method | request method (different rpc type is not the same, http class for: get, post wait, rpc class for the interface name) | | |
+| requestHeader | Request header (json format) | | |
+| responseHeader | Response header (json format) | | |
+| queryParams | Request query parameters | | |
+| requestBody | Request Body (body of binary type will not be captured) | | |
+| requestUri | Request uri | | |
+| responseBody | Response body | | |
+| responseContentLength | Response body size | | |
+| rpcType | rpc type | | |
+| status | response status | | |
+| upstreamIp | Upstream (program providing the service) IP | | |
+| upstreamResponseTime | Time taken by the upstream (program providing the service) to respond to the request (ms ms) | | |
+| userAgent | Requested user agent | | |
+| host | The requested host | | |
+| module | Requested modules | | |
+| path | The requested path | | |
+| traceId | Requested Link Tracking ID | Need to access link tracking plugins, such as skywalking,zipkin | |
+
+
+## 2.6 Examples
+
+### 2.6.1 Collect Http Log by ElasticSearch
+
+#### 2.6.1.1 Install ElasticSearch
+
+Users need to deploy the `ElasticSearch` service to collect
+
+##### 2.6.1.1.1 Installing ElasticSearch under Windows Environment
+
+- To [download address](https://www.elastic.co/downloads/elasticsearch) Select Windows version to download
+- After downloading the installation package, unzip it, enter the `bin` directory, and double-click to execute `elasticsearch.bat` to start
+- The default startup port is `9200`. Access`http://localhost:9200`, verify success
+
+
+
+##### 2.6.1.1.2 Installing ElasticSearch in MacOS environment
+
+- To [download address](https://www.elastic.co/downloads/elasticsearch) Select Windows version to download
+- After downloading the installation package, unzip it, enter the `bin` directory and execute the startup command on the terminal: `./elasticsearch`
+- The default startup port is `9200`. Access `http://localhost:9200`, verify success
+
+
+
+#### 2.6.1.2 Install Kibana
+
+##### 2.6.1.2.1 Installing Kibana under Windows Environment
+
+- To [download address](https://www.elastic.co/cn/downloads/kibana) Select Windows version to download
+- After downloading the installation package, unzip it, enter the `bin` directory, and double-click to execute `kibana.bat` to start
+- The default startup port is `5601`. Access `http://localhost:5601`, verify success
+
+
+
+##### 2.6.1.2.2 Installing Kibana in MacOS environment
+
+- To [download address](https://www.elastic.co/cn/downloads/kibana) Select Windows version to download
+- After downloading the installation package, unzip it, enter the `bin` directory and execute the startup command on the terminal: `./kibana`
+- The default startup port is `5601`. Access `http://localhost:5601`, verify success
+
+
+
+#### 2.6.1.3 Plugin Configuration
+
+
+
+#### 2.6.1.4 Selector and Rule Configuration
+
+* For detailed configuration of selectors and rules, please refer to:[Selector and rule management](../../user-guide/admin-usage/selector-and-rule)。
+
+#### 2.6.1.5 Using postman to initiate a request
+
+
+
+#### 2.6.1.6 Querying data using kibana
+
+
+
+- The first time you use the plug-in, you will automatically create a `shenyu-access-logging` index
+
+
+
+- Using ES query statement, the requested log information can be queried
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `LoggingElasticSearch` set Status disable.
diff --git a/versioned_docs/version-2.6.1/plugin-center/observability/logging-huawei-lts.md b/versioned_docs/version-2.6.1/plugin-center/observability/logging-huawei-lts.md
new file mode 100644
index 00000000000..48a59f66173
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/observability/logging-huawei-lts.md
@@ -0,0 +1,172 @@
+---
+title: Logging-Huawei-Lts Plugin
+keywords: ["Logging"]
+description: logging plugin
+
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Logging-HuaweiLts Plugin
+
+## 1.2 Appropriate Scenario
+
+* collect http request information to huawei lts, analysis request information by huawei lts platform.
+
+## 1.3 Plugin functionality
+
+- The gateway receives requests from the client, forwards them to the server, and returns the server results to the client. The gateway can record the details of each request，
+
+* the plugin records access logs and sends to huawei lts platform.
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-logging-huawei-lts`
+
+* Core Class `org.apache.shenyu.plugin.huawei.lts.LoggingHuaweiLtsPlugin`
+* Core Class `org.apache.shenyu.plugin.huawei.lts.client.HuaweiLtsLogCollectClient`
+
+## 1.5 Added Since Which shenyu version
+
+ShenYu 2.6.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+- ## 2.2 Import pom
+
+ - import maven config in shenyu-bootstrap project's `pom.xml` file.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-logging-huawei-lts
+ ${project.version}
+
+
+```
+
+## 2.3 Enable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `loggingHuaweiLts` set Status enable.
+
+## 2.4 Config plugin
+
+### 2.4.1 Plugin configuration
+
+### 
+
+| config-item | description | type | remarks |
+| ------------------------- | ------------------------------------------------------------ | ------- | -------- |
+| projectId | The project ID of the HUAWEI CLOUD account（project id） | String | must |
+| accessKeyId | AK of the HUAWEI CLOUD account | String | must |
+| accessKeySecret | SK of HUAWEI CLOUD account | String | must |
+| regionName | Regions of Cloud Log Service | String | must |
+| logGroupId | The log group ID of the LTS | String | must |
+| logStreamId | The log stream ID of the LTS | String | must |
+| totalSizeInBytes | The upper limit of the log size that can be cached by a single producer instance | int | optional |
+| maxBlockMs | If the producer has insufficient free space, the caller's maximum block time on the send method, in milliseconds. The default is 60 seconds (60000 milliseconds), and 0 seconds is recommended. When the maxBlockMs value >= 0, it will block until the set time. If the blocking time is reached, the memory cannot be obtained, that is, an error will be reported and the log will be discarded. When the value of maxBlockMs=-1, it will be blocked until the sending is successful, and the log will not be discarded | long | optional |
+| ioThreadCount | The thread pool size for executing log sending tasks | int | optional |
+| batchSizeThresholdInBytes | When the cached log size in a ProducerBatch is greater than or equal to batchSizeThresholdInBytes, the batch will be sent | int | optional |
+| batchCountThreshold | When the number of cached logs in a ProducerBatch is greater than or equal to batchCountThreshold, the batch will be sent | int | optional |
+| lingerMs | The lingering time of a ProducerBatch from creation until it is sendable | int | optional |
+| retries | If a ProducerBatch fails to send for the first time, the number of times it can be retried is recommended to be 3 times. If retries is less than or equal to 0, the ProducerBatch will directly enter the failure queue after the first sending failure | int | optional |
+| baseRetryBackoffMs | The backoff time for the first retry | long | optional |
+| maxRetryBackoffMs | Maximum backoff time for retries | long | optional |
+| giveUpExtraLongSingleLog | For logs exceeding 1M, the data larger than 1M will be discarded after splitting | boolean | optional |
+| enableLocalTest | 是否开启跨云上报日志 | boolean | optional |
+
+- get `regionName`
+
+
+
+| **区域名称** | **RegionName** |
+| ------------ | -------------- |
+| 华北-北京二 | cn-north-2 |
+| 华北-北京四 | cn-north-4 |
+| 华北-北京一 | cn-north-1 |
+| 华东-上海二 | cn-east-2 |
+| 华东-上海一 | cn-east-3 |
+| 华南-广州 | cn-south-1 |
+| 华南-深圳 | cn-south-2 |
+| 西南-贵阳一 | cn-southwest-2 |
+
+- get `projectId`
+
+
+
+- get `accessKeyId` and `accessKeySecret`
+
+
+
+- get `logGroupId` and `logStreamId`
+
+
+
+
+
+### 2.4.2 Configuration Selectors and Rules
+
+* Selector and rule Config. Please refer: [Selector and rule config](../../user-guide/admin-usage/selector-and-rule.md).
+
+## 2.5 Logging Info
+
+collect request info as follows
+
+| Field Name | Meaning | Description | Remarks |
+| :-------------------- | :----------------------------------------------------------: | :----------------------------------------------------------- | :------ |
+| clientIp | Client IP | | |
+| timeLocal | Request time string, format: yyyy-MM-dd HH:mm:ss.SSS | | |
+| method | request method (different rpc type is not the same, http class for: get, post wait, rpc class for the interface name) | | |
+| requestHeader | Request header (json format) | | |
+| responseHeader | Response header (json format) | | |
+| queryParams | Request query parameters | | |
+| requestBody | Request Body (body of binary type will not be captured) | | |
+| requestUri | Request uri | | |
+| responseBody | Response body | | |
+| responseContentLength | Response body size | | |
+| rpcType | rpc type | | |
+| status | response status | | |
+| upstreamIp | Upstream (program providing the service) IP | | |
+| upstreamResponseTime | Time taken by the upstream (program providing the service) to respond to the request (ms ms) | | |
+| userAgent | Requested user agent | | |
+| host | The requested host | | |
+| module | Requested modules | | |
+| path | The requested path | | |
+| traceId | Requested Link Tracking ID | Need to access link tracking plugins, such as skywalking,zipkin | |
+
+## 2.6 Examples
+
+### 2.6.1 Collect Http Log by tencent cls platform
+
+#### 2.6.1.1 Plugin Configuration
+
+* Open the plugin and configure huawei lts, configure it as follows.
+
+
+
+#### 2.6.1.2 Selector Configuration
+
+
+
+#### 2.6.1.3 Rule Configuration
+
+
+
+#### 2.6.1.4 Send Request
+
+
+
+#### 2.6.1.5 Huawei lts Platform Display
+
+
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin -->`loggingHuaweiLts`set Status disable.
diff --git a/versioned_docs/version-2.6.1/plugin-center/observability/logging-kafka.md b/versioned_docs/version-2.6.1/plugin-center/observability/logging-kafka.md
new file mode 100644
index 00000000000..feb312c7e61
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/observability/logging-kafka.md
@@ -0,0 +1,162 @@
+---
+title: Logging-Kafka Plugin
+keywords: ["Logging", "kafka"]
+description: Logging-Kafka Plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Logging-Kafka Plugin
+
+## 1.2 Appropriate Scenario
+
+* collect http request log to Kafka, consume Kafka message to another application and analysis.
+
+## 1.3 Plugin functionality
+
+>`Apache ShenYu` The gateway receives requests from the client, forwards them to the server, and returns the server results to the client. The gateway can record the details of each request，
+> The list includes: request time, request parameters, request path, response result, response status code, time consumption, upstream IP, exception information waiting.
+> The Logging-Kafka plugin is a plugin that records access logs and sends them to the Kafka cluster.
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-logging-kafka`.
+
+* Core Class `org.apache.shenyu.plugin.logging.kafka.LoggingKafkaPlugin`
+* Core Claas `org.apache.shenyu.plugin.logging.kafka.client.KafkaLogCollectClient`
+
+## 1.5 Added Since Which shenyu version
+
+* Since ShenYu 2.5.0
+
+## 1.6 Technical Solutions
+
+* Architecture Diagram
+
+
+
+* Full asynchronous collection and delivery of `Logging` inside the `Apache ShenYu` gateway
+
+* Logging platform by consuming the logs in the `Kafka` cluster for repository, and then using `Grafana`, `Kibana` or other visualization platform to display
+
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+* Add the `Logging-Kafka` dependency to the gateway's `pom.xml` file.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-logging-kafka
+ ${project.version}
+
+
+```
+
+## 2.3 Enable plugin
+
+* In `shenyu-admin` --> Basic Configuration --> Plugin Management --> `loggingKafka`, configure the kafka parameter and set it to on.
+
+## 2.4 Config plugin
+
+### 2.4.1 Open the plugin and configure kafka, configure it as follows.
+
+
+
+* The individual configuration items are described as follows:
+
+| | | | |
+|:----------------------------------|:---------------------|:----------------------------------|:------------|
+| config-item | type | description | remarks |
+| topic | String | Message Queue Topics | must |
+| namesrvAddr | String | Message queue nameserver address | must |
+| sampleRate | String | Sampling rate, range 0~1, 0: off, 0.01: acquisition 1%, 1: acquisition 100% | Optional, default 1, all collection |
+| compressAlg | String | Compression algorithm, no compression by default, currently supports LZ4 compression | Optional, no compression by default |
+| maxResponseBody | Ingeter | Maximum response size, above the threshold no response will be collected | Optional, default 512KB |
+| maxRequestBody | Ingeter | Maximum request body size, above the threshold no request body will be collected | Optional, default 512KB |
+Except for topic, namesrvAddr, all others are optional, in most cases only these 3 items need to be configured. The default group id is "shenyu-access-logging"
+
+### 2.4.2 Configuring Selectors and Rulers
+
+* For detailed configuration of selectors and rules, please refer to: [Selector and rule management](../../user-guide/admin-usage/selector-and-rule)。
+
+In addition, sometimes a large gateway cluster corresponds to multiple applications (business), different applications (business) corresponds to different topics, related to isolation,
+then you can configure different topics (optional) and sampling rate (optional) by selector, the meaning of the configuration items as shown in the table above.
+The operation is shown below:
+
+
+## 2.5 Logging Info
+
+collect request info as follows
+
+| Field Name | Meaning | Description | Remarks |
+|:----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:------------------------------|:----|
+| clientIp | Client IP | | |
+| timeLocal | Request time string, format: yyyy-MM-dd HH:mm:ss.SSS | | |
+| method | request method (different rpc type is not the same, http class for: get, post wait, rpc class for the interface name) | | |
+| requestHeader | Request header (json format) | | |
+| responseHeader | Response header (json format) | | |
+| queryParams | Request query parameters | | |
+| requestBody | Request Body (body of binary type will not be captured) | | |
+| requestUri | Request uri | | |
+| responseBody | Response body | | |
+| responseContentLength | Response body size | | |
+| rpcType | rpc type | | |
+| status | response status | | |
+| upstreamIp | Upstream (program providing the service) IP | | |
+| upstreamResponseTime | Time taken by the upstream (program providing the service) to respond to the request (ms ms) | | |
+| userAgent | Requested user agent | | |
+| host | The requested host | | |
+| module | Requested modules | | |
+| path | The requested path | | |
+| traceId | Requested Link Tracking ID | Need to access link tracking plugins, such as skywalking,zipkin | |
+
+
+## 2.6 Examples
+
+### 2.6.1 Collect Http Log by Kafka
+
+#### 2.6.1.1 Plugin Configuration
+
+Open the plugin and configure kafka, configure it as follows.
+
+
+
+#### 2.6.1.2 Selector Configuration
+
+For detailed configuration of selectors and rules, please refer to: [Selector and rule management](../../user-guide/admin-usage/selector-and-rule)。
+
+In addition, sometimes a large gateway cluster corresponds to multiple applications (business), different applications (business) corresponds to different topics, related to isolation,
+then you can configure different topics (optional) and sampling rate (optional) by selector, the meaning of the configuration items as shown in the table above.
+The operation is shown below:
+
+
+#### 2.6.1.3 Rule Configuration
+
+
+
+#### 2.6.1.4 Request Service
+
+
+
+#### 2.6.1.5 Consumption and display of Logging
+
+As each logging platform has differences, such as storage available clickhouse, ElasticSearch, etc., visualization has self-developed or open source Grafana, Kibana, etc..
+Logging-Kafka plugin uses Kafka to decouple production and consumption, while outputting logs in json format,
+consumption and visualization require users to choose different technology stacks to achieve their own situation.=
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `loggingKafka` set Status disable.
+
+
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/observability/logging-plugin.md b/versioned_docs/version-2.6.1/plugin-center/observability/logging-plugin.md
new file mode 100644
index 00000000000..3bf717aecff
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/observability/logging-plugin.md
@@ -0,0 +1,117 @@
+---
+title: Logging Plugin
+keywords: ["logging"]
+description: logging plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Logging-Console Plugin
+
+## 1.2 Appropriate Scenario
+
+* Users may want to view the information about request(including request headers, request parameters, response headers, response body...etc) where in the side of gateway when debugging during development or troubleshooting problems online.
+
+## 1.3 Plugin functionality
+
+* Collect http request url, header, request body, response and response body by logback or log4j, the log file will be saved locally.
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-pluign-logging-console`.
+
+* Core Class `org.apache.shenyu.plugin.logging.console.LoggingConsolePlugin`
+
+## 1.5 Added Since Which shenyu version
+
+* Since ShenYu 2.4.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+- import maven config in shenyu-bootstrap project's `pom.xml` file.
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-logging-console
+ ${project.version}
+
+```
+
+## 2.3 Enable plugin
+
+- In shenyu-admin --> BasicConfig --> Plugin --> loggingConsole set Status enable.
+
+## 2.4 Config plugin
+
+* Selector and rule Config. Please refer: [Selector and rule config](../../user-guide/admin-usage/selector-and-rule.md).
+
+## 2.5 Examples
+
+## 2.5.1 Collect all http request log
+
+> you must open loggingConsole plugin before you use loggingConsole plugin.
+
+### 2.5.1.1 Selector Configuration
+
+
+
+### 2.5.1.2 Rule Configuration
+
+
+
+### 2.5.1.3 Call Http Service
+
+
+
+### 2.5.1.4 Check Result
+
+if the request arrived successfully, you will see request information as follow.
+
+```
+Request Uri: http://localhost:9195/test/payment
+Request Method: POST
+
+[Request Headers Start]
+Content-Type: application/json
+Content-Length: 46
+Host: localhost:9195
+Connection: Keep-Alive
+User-Agent: Apache-HttpClient/4.5.13 (Java/11.0.11)
+Cookie: JSESSIONID=CD325CE813F61BB37783A1D0835959DD
+Accept-Encoding: gzip,deflate
+[Request Headers End]
+
+[Request Body Start]
+{
+ "userId": "11",
+ "userName": "xiaoming"
+}
+[Request Body End]
+
+Response Code: 200 OK
+
+[Response Headers Start]
+transfer-encoding: chunked
+Content-Length: 37
+Content-Type: application/json
+[Response Headers End]
+
+[Response Body Start]
+{"userId":"11","userName":"xiaoming"}
+[Response Body End]
+```
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `loggingConsole` set Status disable.
+
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/observability/logging-pulsar.md b/versioned_docs/version-2.6.1/plugin-center/observability/logging-pulsar.md
new file mode 100644
index 00000000000..4f69a946a5f
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/observability/logging-pulsar.md
@@ -0,0 +1,162 @@
+---
+title: Logging-Pulsar Plugin
+keywords: ["Logging", "pulsar"]
+description: Logging-Pulsar Plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Logging-Pulsar Plugin
+
+## 1.2 Appropriate Scenario
+
+* collect http request log to Pulsar, consume Pulsar message to another application and analysis.
+
+## 1.3 Plugin functionality
+
+>`Apache ShenYu` The gateway receives requests from the client, forwards them to the server, and returns the server results to the client. The gateway can record the details of each request，
+> The list includes: request time, request parameters, request path, response result, response status code, time consumption, upstream IP, exception information waiting.
+> The Logging-Pulsar plugin is a plugin that records access logs and sends them to the Pulsar cluster.
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-logging-pulsar`.
+
+* Core Class `org.apache.shenyu.plugin.logging.pulsar.LoggingPulsarPlugin`
+* Core Claas `org.apache.shenyu.plugin.logging.pulsar.client.PulsarLogCollectClient`
+
+## 1.5 Added Since Which shenyu version
+
+* Since ShenYu 2.5.1
+
+## 1.6 Technical Solutions
+
+* Architecture Diagram
+
+
+
+* Full asynchronous collection and delivery of `Logging` inside the `Apache ShenYu` gateway
+
+* Logging platform by consuming the logs in the `Pulsar` cluster for repository, and then using `Grafana`, `Kibana` or other visualization platform to display
+
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+* Add the `Logging-Pulsar` dependency to the gateway's `pom.xml` file.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-logging-pulsar
+ ${project.version}
+
+
+```
+
+## 2.3 Enable plugin
+
+* In `shenyu-admin` --> Basic Configuration --> Plugin Management --> `loggingPulsar`, configure the pulsar parameter and set it to on.
+
+## 2.4 Config plugin
+
+### 2.4.1 Open the plugin and configure pulsar, configure it as follows.
+
+
+
+* The individual configuration items are described as follows:
+
+| | | | |
+|:----------------------------------|:---------------------|:----------------------------------|:------------|
+| config-item | type | description | remarks |
+| topic | String | Message Queue Topics | must |
+| serviceUrl | String | Message queue service address | must |
+| sampleRate | String | Sampling rate, range 0~1, 0: off, 0.01: acquisition 1%, 1: acquisition 100% | Optional, default 1, all collection |
+| compressAlg | String | Compression algorithm, no compression by default, currently supports LZ4 compression | Optional, no compression by default |
+| maxResponseBody | Ingeter | Maximum response size, above the threshold no response will be collected | Optional, default 512KB |
+| maxRequestBody | Ingeter | Maximum request body size, above the threshold no request body will be collected | Optional, default 512KB |
+Except for topic, serviceUrl, all others are optional, in most cases only these 3 items need to be configured. The default group id is "shenyu-access-logging"
+
+### 2.4.2 Configuring Selectors and Rulers
+
+* For detailed configuration of selectors and rules, please refer to: [Selector and rule management](../../user-guide/admin-usage/selector-and-rule)。
+
+In addition, sometimes a large gateway cluster corresponds to multiple applications (business), different applications (business) corresponds to different topics, related to isolation,
+then you can configure different topics (optional) and sampling rate (optional) by selector, the meaning of the configuration items as shown in the table above.
+The operation is shown below:
+
+
+## 2.5 Logging Info
+
+collect request info as follows
+
+| Field Name | Meaning | Description | Remarks |
+|:----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:------------------------------|:----|
+| clientIp | Client IP | | |
+| timeLocal | Request time string, format: yyyy-MM-dd HH:mm:ss.SSS | | |
+| method | request method (different rpc type is not the same, http class for: get, post wait, rpc class for the interface name) | | |
+| requestHeader | Request header (json format) | | |
+| responseHeader | Response header (json format) | | |
+| queryParams | Request query parameters | | |
+| requestBody | Request Body (body of binary type will not be captured) | | |
+| requestUri | Request uri | | |
+| responseBody | Response body | | |
+| responseContentLength | Response body size | | |
+| rpcType | rpc type | | |
+| status | response status | | |
+| upstreamIp | Upstream (program providing the service) IP | | |
+| upstreamResponseTime | Time taken by the upstream (program providing the service) to respond to the request (ms ms) | | |
+| userAgent | Requested user agent | | |
+| host | The requested host | | |
+| module | Requested modules | | |
+| path | The requested path | | |
+| traceId | Requested Link Tracking ID | Need to access link tracking plugins, such as skywalking,zipkin | |
+
+
+## 2.6 Examples
+
+### 2.6.1 Collect Http Log by Pulsar
+
+#### 2.6.1.1 Plugin Configuration
+
+Open the plugin and configure pulsar, configure it as follows.
+
+
+
+#### 2.6.1.2 Selector Configuration
+
+For detailed configuration of selectors and rules, please refer to: [Selector and rule management](../../user-guide/admin-usage/selector-and-rule)。
+
+In addition, sometimes a large gateway cluster corresponds to multiple applications (business), different applications (business) corresponds to different topics, related to isolation,
+then you can configure different topics (optional) and samplingf rate (optional) by selector, the meaning of the configuration items as shown in the table above.
+The operation is shown below:
+
+
+#### 2.6.1.3 Rule Configuration
+
+
+
+#### 2.6.1.4 Request Service
+
+
+
+#### 2.6.1.5 Consumption and display of Logging
+
+As each logging platform has differences, such as storage available clickhouse, ElasticSearch, etc., visualization has self-developed or open source Grafana, Kibana, etc..
+Logging-Pulsar plugin uses Pulsar to decouple production and consumption, while outputting logs in json format,
+consumption and visualization require users to choose different technology stacks to achieve their own situation.=
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `loggingPulsar` set Status disable.
+
+
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/observability/logging-rocketmq.md b/versioned_docs/version-2.6.1/plugin-center/observability/logging-rocketmq.md
new file mode 100644
index 00000000000..d59c340d7a4
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/observability/logging-rocketmq.md
@@ -0,0 +1,173 @@
+---
+title: Logging-RocketMQ Plugin
+keywords: ["Logging", "RocketMQ"]
+description: Logging-RocketMQ Plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Logging-RocketMQ Plugin
+
+## 1.2 Appropriate Scenario
+
+* collect http request log to rocketmq, consume rocketmq message to another application and analysis.
+
+## 1.3 Plugin functionality
+
+>`Apache ShenYu` The gateway receives requests from the client, forwards them to the server, and returns the server results to the client. The gateway can record the details of each request，
+> The list includes: request time, request parameters, request path, response result, response status code, time consumption, upstream IP, exception information waiting.
+> The Logging-RocketMQ plugin is a plugin that records access logs and sends them to the RocketMQ cluster.
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-logging-rocketmq`.
+
+* Core Class `org.apache.shenyu.plugin.logging.rocketmq.LoggingRocketMQPlugin`
+* Core Claas `org.apache.shenyu.plugin.logging.rocketmq.client.RocketMQLogCollectClient`
+
+## 1.5 Added Since Which shenyu version
+
+* Since ShenYu 2.5.0
+
+## 1.6 Technical Solutions
+
+* Architecture Diagram
+
+
+
+* Full asynchronous collection and delivery of `Logging` inside the `Apache ShenYu` gateway
+
+* Logging platform by consuming the logs in the `RocketMQ` cluster for repository, and then using `Grafana`, `Kibana` or other visualization platform to display
+
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+* Add the `Logging-RocketMQ` dependency to the gateway's `pom.xml` file.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-logging-rocketmq
+ ${project.version}
+
+
+```
+
+## 2.3 Enable plugin
+
+* In `shenyu-admin` --> Basic Configuration --> Plugin Management --> `loggingRocketMQ`, configure the rocketMQ parameter and set it to on.
+
+## 2.4 Config plugin
+
+### 2.4.1 Open the plugin and configure rocketmq, configure it as follows.
+
+
+
+* The individual configuration items are described as follows:
+
+| | | | |
+|:----------------------------------|:---------------------|:----------------------------------|:------------|
+| config-item | type | description | remarks |
+| topic | String | Message Queue Topics | must |
+| namesrvAddr | String | Message queue nameserver address | must |
+| producerGroup | String | Log Message Producer Group | must |
+| sampleRate | String | Sampling rate, range 0~1, 0: off, 0.01: acquisition 1%, 1: acquisition 100% | Optional, default 1, all collection |
+| compressAlg | String | Compression algorithm, no compression by default, currently supports LZ4 compression | Optional, no compression by default |
+| maxResponseBody | Ingeter | Maximum response size, above the threshold no response will be collected | Optional, default 512KB |
+| maxRequestBody | Ingeter | Maximum request body size, above the threshold no request body will be collected | Optional, default 512KB |
+Except for topic, namesrvAddr, producerGroup, all others are optional, in most cases only these 3 items need to be configured.
+
+### 2.4.2 Configuring Selectors and Rulers
+
+* For detailed configuration of selectors and rules, please refer to: [Selector and rule management](../../user-guide/admin-usage/selector-and-rule)。
+
+In addition, sometimes a large gateway cluster corresponds to multiple applications (business), different applications (business) corresponds to different topics, related to isolation,
+then you can configure different topics (optional) and sampling rate (optional) by selector, the meaning of the configuration items as shown in the table above.
+The operation is shown below:
+
+
+## 2.5 Logging Info
+
+collect request info as follows
+
+| Field Name | Meaning | Description | Remarks |
+|:----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:------------------------------|:----|
+| clientIp | Client IP | | |
+| timeLocal | Request time string, format: yyyy-MM-dd HH:mm:ss.SSS | | |
+| method | request method (different rpc type is not the same, http class for: get, post wait, rpc class for the interface name) | | |
+| requestHeader | Request header (json format) | | |
+| responseHeader | Response header (json format) | | |
+| queryParams | Request query parameters | | |
+| requestBody | Request Body (body of binary type will not be captured) | | |
+| requestUri | Request uri | | |
+| responseBody | Response body | | |
+| responseContentLength | Response body size | | |
+| rpcType | rpc type | | |
+| status | response status | | |
+| upstreamIp | Upstream (program providing the service) IP | | |
+| upstreamResponseTime | Time taken by the upstream (program providing the service) to respond to the request (ms ms) | | |
+| userAgent | Requested user agent | | |
+| host | The requested host | | |
+| module | Requested modules | | |
+| path | The requested path | | |
+| traceId | Requested Link Tracking ID | Need to access link tracking plugins, such as skywalking,zipkin | |
+
+
+## 2.6 Examples
+
+### 2.6.1 Collect Http Log by RocketMQ
+
+#### 2.6.1.1 Plugin Configuration
+
+Open the plugin and configure rocketmq, configure it as follows.
+
+
+
+#### 2.6.1.2 Selector Configuration
+
+For detailed configuration of selectors and rules, please refer to: [Selector and rule management](../../user-guide/admin-usage/selector-and-rule)。
+
+In addition, sometimes a large gateway cluster corresponds to multiple applications (business), different applications (business) corresponds to different topics, related to isolation,
+then you can configure different topics (optional) and sampling rate (optional) by selector, the meaning of the configuration items as shown in the table above.
+The operation is shown below:
+
+
+#### 2.6.1.3 Rule Configuration
+
+
+
+#### 2.6.1.4 Request Service
+
+
+
+#### 2.6.1.5 Consumption and display of Logging
+
+As each logging platform has differences, such as storage available clickhouse, ElasticSearch, etc., visualization has self-developed or open source Grafana, Kibana, etc..
+Logging-RocketMQ plugin uses RocketMQ to decouple production and consumption, while outputting logs in json format,
+consumption and visualization require users to choose different technology stacks to achieve their own situation.
+
+
+#### 2.6.1.6 Panel Display
+
+Users can choose to visualize the implementation according to their own situation.
+The following shows the effect of `Grafana`:
+[Grafana Sandbox Experience](https://play.grafana.org)
+
+
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `loggingRocketMQ` set Status disable.
+
+
+
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/observability/logging-tencent-cls.md b/versioned_docs/version-2.6.1/plugin-center/observability/logging-tencent-cls.md
new file mode 100644
index 00000000000..9ab9890d474
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/observability/logging-tencent-cls.md
@@ -0,0 +1,143 @@
+---
+title: Logging-Tencent-Cls Plugin
+keywords: ["Logging"]
+description: logging plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Logging-TencentCls Plugin
+
+## 1.2 Appropriate Scenario
+
+* collect http request information to tencent cls, analysis request information by tencent cls platform.
+
+## 1.3 Plugin functionality
+
+* The gateway receives requests from the client, forwards them to the server, and returns the server results to the client. The gateway can record the details of each request，
+* the plugin records access logs and sends to tencent cls platform.
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-logging-tencent-cls`
+
+* Core Class `org.apache.shenyu.plugin.tencent.cls.LoggingTencentClsPlugin`
+* Core Class `org.apache.shenyu.plugin.tencent.cls.client.TencentClsLogCollectClient`
+
+## 1.5 Added Since Which shenyu version
+
+ShenYu 2.5.1
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+- import maven config in shenyu-bootstrap project's `pom.xml` file.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-logging-tencent-cls
+ ${project.version}
+
+
+```
+
+## 2.3 Enable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `loggingTencentCls` set Status enable.
+
+## 2.4 Config plugin
+
+### 2.4.1 Plugin configuration
+
+
+
+| config-item | type | remarks | description |
+|:--------------------|:--------|:-------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| secretId | String | must | secretId |
+| secretKey | String | must | secretKey |
+| endpoint | String | must | host name, example:ap-guangzhou.cls.tencentcs.com |
+| topic | String | optional, default shenyu-topic | topic |
+| sendThreadCount | String | optional, default 1 | Number of core threads for log consumption callback |
+| TotalSizeInBytes | Integer | optional, default 104857600 | The maximum log size that the instance can cache |
+| MaxSendThreadCount | Integer | optional, default 50 | The maximum number of "goroutines" that the client can concurrently |
+| MaxBlockSec | Integer | optional, default 60000 ms | The maximum amount of time the caller can block on the send method if the client is running out of free space. If the required space cannot be satisfied after this time, the send method will throw a TimeoutException. Set this value to a negative number if you want the send method to block until the required space is met |
+| MaxBatchSize | Integer | optional, default 512 * 1024 (512KB) | When the cached log size in a Batch is greater than or equal to batchSizeThresholdInBytes, the batch will be sent, and the maximum size can be set to 5MB |
+| MaxBatchCount | Integer | optional, default 4096 | When the number of logs cached in a batch is greater than or equal to batchCountThreshold, the batch will be sent and the maximum can be set to 40960 |
+| LingerMs | Integer | optional, default 2000 ms | The duration of the batch from the creation to the time it can be sent, the minimum can be set to 100 milliseconds |
+| Retries | Integer | optional, default 10 | If a Batch fails to be sent for the first time, the number of times it can be retried, if the retries is less than or equal to 0, the ProducerBatch will directly enter the failure queue after the first failure of sending |
+| MaxReservedAttempts | Integer | optional, default 11 | Each batch that is attempted to be sent corresponds to an Attemp. This parameter is used to control the number of attempts returned to the user. By default, only the latest 11 attempts are retained. A larger parameter allows you to trace more information, but also consumes more memory |
+| BaseRetryBackoffMs | Integer | optional, default 100 ms | Backoff time for the first retry The client samples the exponential backoff algorithm, and the planned waiting time for the Nth retry is baseRetryBackoffMs * 2^(N-1 |
+| MaxRetryBackoffMs | Integer | optional, default 50 s | Maximum backoff time for retries |
+
+- get `topic`
+
+
+
+### 2.4.2 Configuration Selectors and Rules
+
+* Selector and rule Config. Please refer: [Selector and rule config](../../user-guide/admin-usage/selector-and-rule.md).
+
+## 2.5 Logging Info
+
+collect request info as follows
+
+| Field Name | Meaning | Description | Remarks |
+|:----------------------|:---------------------------------------------------------------------------------------------------------------------:|:----------------------------------------------------------------|:--------|
+| clientIp | Client IP | | |
+| timeLocal | Request time string, format: yyyy-MM-dd HH:mm:ss.SSS | | |
+| method | request method (different rpc type is not the same, http class for: get, post wait, rpc class for the interface name) | | |
+| requestHeader | Request header (json format) | | |
+| responseHeader | Response header (json format) | | |
+| queryParams | Request query parameters | | |
+| requestBody | Request Body (body of binary type will not be captured) | | |
+| requestUri | Request uri | | |
+| responseBody | Response body | | |
+| responseContentLength | Response body size | | |
+| rpcType | rpc type | | |
+| status | response status | | |
+| upstreamIp | Upstream (program providing the service) IP | | |
+| upstreamResponseTime | Time taken by the upstream (program providing the service) to respond to the request (ms ms) | | |
+| userAgent | Requested user agent | | |
+| host | The requested host | | |
+| module | Requested modules | | |
+| path | The requested path | | |
+| traceId | Requested Link Tracking ID | Need to access link tracking plugins, such as skywalking,zipkin | |
+
+## 2.6 Examples
+
+### 2.6.1 Collect Http Log by tencent cls platform
+
+#### 2.6.1.1 Plugin Configuration
+
+* Open the plugin and configure tencent-cls, configure it as follows.
+
+
+
+#### 2.6.1.2 Selector Configuration
+
+
+
+#### 2.6.1.3 Rule Configuration
+
+
+
+#### 2.6.1.4 Send Request
+
+
+
+#### 2.6.1.5 Tencent cls Platform Display
+
+
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `loggingTencentCls` set Status disable.
diff --git a/versioned_docs/version-2.6.1/plugin-center/observability/metrics-plugin.md b/versioned_docs/version-2.6.1/plugin-center/observability/metrics-plugin.md
new file mode 100644
index 00000000000..131a2344e8a
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/observability/metrics-plugin.md
@@ -0,0 +1,245 @@
+---
+title: Metrics Plugin
+keywords: ["Metrics"]
+description: Metrics plugin
+---
+
+## Description
+
+* Metrics plugin is used to monitor its own running status(JVM-related) by gateway, include request response delay, QPS, TPS, and other related metrics.
+
+## Technical Solutions
+
+* Flow Diagram
+ 
+* Make even tracking in ShenYu Gateway by asynchronous or synchronous mode.
+
+* The `prometheus` server pulls metrics' through http request, and then displays it by `Grafana`.
+
+## Plugin Setting
+
+* Introduce `metrics` dependency in the pom.xml file of the gateway.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-metrics
+ ${project.version}
+
+
+```
+
+* modify this config in shenyu gateway yaml
+
+```yml
+shenyu:
+ metrics:
+ enabled: false #false is close, true is open
+ name : prometheus
+ host: 127.0.0.1
+ port: 8090
+ jmxConfig:
+ props:
+ jvm_enabled: true #enable jvm monitoring
+```
+
+## Metrics Detail
+
+* All JVM，thread，memory，and other related information will be made event tracking，you can add a JVM module in the Grafana' panel, and it will be fully displayed, please refer to： https://github.com/prometheus/jmx_exporter
+
+* There are also the following custom `metrics`
+
+### shenyu gateway custom metrics
+
+| Name |type |labels | description |
+|:----------------------------------- |:--------------------- |:------------- |:-------------------- |
+|shenyu_request_total |Counter | none |collecting all requests of Apache ShenYu Gateway |
+|shenyu_request_throw_total |Counter | none |collecting all exception requests of Apache ShenYu Gateway |
+|shenyu_request_type_total |Counter | path,type |collecting all matched requests of monitor|
+|shenyu_execute_latency_millis |histogram | none | ShenYu gateway execute time interval |
+
+
+### jmx metrics
+
+| name | type | labals | help |
+|:-------------------------------:|:-------:|:------:|:--------------------------------------------------------------:|
+| jmx_config_reload_success_total | counter | | Number of times configuration have successfully been reloaded. |
+| jmx_config_reload_failure_total | counter | | Number of times configuration have failed to be reloaded. |
+| jmx_scrape_duration_seconds | gauge | | Time this JMX scrape took, in seconds. |
+| jmx_scrape_error | gauge | | Non-zero if this scrape failed. |
+| jmx_scrape_cached_beans | gauge | | Number of beans with their matching rule cached |
+| jmx_scrape_duration_seconds | gauge | | Time this JMX scrape took, in seconds. |
+| jmx_scrape_error | gauge | | Non-zero if this scrape failed. |
+| jmx_scrape_cached_beans | gauge | | Number of beans with their matching rule cached |
+
+### jvm metrics
+
+#### StandardExports
+
+| name | type | labels | help |
+|:-----------------------------:|:-------:|:------:|:------------------------------------------------------:|
+| process_cpu_seconds_total | counter | | Total user and system CPU time spent in seconds. |
+| process_start_time_seconds | gauge | | Start time of the process since unix epoch in seconds. |
+| process_open_fds | gauge | | Number of open file descriptors. |
+| process_max_fds | gauge | | Maximum number of open file descriptors. |
+| process_virtual_memory_bytes | gauge | | Virtual memory size in bytes. |
+| process_resident_memory_bytes | gauge | | Resident memory size in bytes. |
+
+#### MemoryPoolsExports
+
+| name | type | labels | help |
+|:------------------------------------------:|:-----:|:----------------------:|:-----------------------------------------------------------------:|
+| jvm_memory_objects_pending_finalization | gauge | {area="heap\|nonheap"} | The number of objects waiting in the finalizer queue. |
+| jvm_memory_bytes_used | gauge | {area="heap\|nonheap"} | Used bytes of a given JVM memory area. |
+| jvm_memory_bytes_committed | gauge | {area="heap\|nonheap"} | Committed (bytes) of a given JVM memory area. |
+| jvm_memory_bytes_max | gauge | {area="heap\|nonheap"} | Max (bytes) of a given JVM memory area. |
+| jvm_memory_bytes_init | gauge | {area="heap\|nonheap"} | Initial bytes of a given JVM memory area. |
+| jvm_memory_pool_bytes_used | gauge | {pool} | Used bytes of a given JVM memory pool. |
+| jvm_memory_pool_bytes_committed | gauge | {pool} | Committed bytes of a given JVM memory pool. |
+| jvm_memory_pool_bytes_max | gauge | {pool} | Max bytes of a given JVM memory pool. |
+| jvm_memory_pool_bytes_init | gauge | {pool} | Initial bytes of a given JVM memory pool. |
+| jvm_memory_pool_collection_used_bytes | gauge | {pool} | Used bytes after last collection of a given JVM memory pool. |
+| jvm_memory_pool_collection_committed_bytes | gauge | {pool} | Committed after last collection bytes of a given JVM memory pool. |
+| jvm_memory_pool_collection_max_bytes | gauge | {pool} | Max bytes after last collection of a given JVM memory pool. |
+| jvm_memory_pool_collection_init_bytes | gauge | {pool} | Initial after last collection bytes of a given JVM memory pool. |
+
+#### MemoryAllocationExports
+
+| name | type | labels | help |
+|:-------------------------------------:|:-------:|:------:|:------------------------------------------------------------------------------------------:|
+| jvm_memory_pool_allocated_bytes_total | counter | {pool} | Total bytes allocated in a given JVM memory pool. Only updated after GC, not continuously. |
+| | | | |
+| | | | |
+
+#### BufferPoolsExports
+
+| name | type | labels | help |
+|:------------------------------:|:-----:|:------:|:------------------------------------------:|
+| jvm_buffer_pool_used_bytes | gauge | {pool} | Used bytes of a given JVM buffer pool. |
+| jvm_buffer_pool_capacity_bytes | gauge | {pool} | Bytes capacity of a given JVM buffer pool. |
+| jvm_buffer_pool_used_buffers | gauge | {pool} | Used buffers of a given JVM buffer pool. |
+
+#### GarbageCollectorExports
+
+| name | type | labels | help |
+|:-------------------------:|:-------:|:------:|:-------------------------------------------------------:|
+| jvm_gc_collection_seconds | summary | {gc} | Time spent in a given JVM garbage collector in seconds. |
+
+#### ThreadExports
+
+| name | type | labels | help |
+|:------------------------------:|:-------:|:-------:|:------------------------------------------------------------------------------------------------------:|
+| jvm_threads_current | gauge | | Current thread count of a JVM |
+| jvm_threads_daemon | gauge | | Daemon thread count of a JVM |
+| jvm_threads_peak | gauge | | Peak thread count of a JVM |
+| jvm_threads_started_total | counter | | Started thread count of a JVM |
+| jvm_threads_deadlocked | gauge | | Cycles of JVM-threads that are in deadlock waiting to acquire object monitors or ownable synchronizers |
+| jvm_threads_deadlocked_monitor | gauge | | Cycles of JVM-threads that are in deadlock waiting to acquire object monitors |
+| jvm_threads_state | gauge | {state} | Current count of threads by state |
+
+#### ClassLoadingExports
+
+| name | type | labels | help |
+|:--------------------------:|:-------:|:------:|:---------------------------------------------------------------------------------------:|
+| jvm_classes_loaded | gauge | | The number of classes that are currently loaded in the JVM |
+| jvm_classes_loaded_total | counter | | The total number of classes that have been loaded since the JVM has started execution |
+| jvm_classes_unloaded_total | counter | | The total number of classes that have been unloaded since the JVM has started execution |
+
+#### VersionInfoExports
+
+| name | type | labels | help |
+|:----:|:----:|:---------------------------------------------------------------------------------:|:---------------:|
+| jvm | info | {version(java.runtime.version),vendor(java.vm.vendor),runtime(java.runtime.name)} | VM version info |
+
+
+## Collect metrics
+
+Users need to install `Prometheus` service to collect
+
+### Install Prometheus in windows
+
+* Choose the corresponding environment [download address](https://prometheus.io/download/) to install
+* Modify configuration file: `prometheus.yml`
+
+ ```yaml
+ scrape_configs:
+ - job_name: 'Apache ShenYu'
+ # metrics_path defaults to '/metrics'
+ # scheme defaults to 'http'.
+ static_configs:
+ - targets: ['localhost:8090'] # metrics of apache shenyu are exposed on port 8090 by default
+ ```
+
+* After the configuration is completed, you can directly double-click `prometheus.exe` in the window to start. The default boot port is `9090`,check `status`->`Targets` . Success can be verified at http://localhost:9090/
+
+
+
+### Install Prometheus in the macOS
+
+* Install prometheus with brew，After installation `prometheus` is in the `Cellar` folder under `homebrew`。
+
+```
+brew install prometheus
+```
+
+* Execute the following command in the location of the prometheus.yml file to start prometheus。
+
+```
+prometheus --config.file=prometheus.yml &
+```
+
+Visit `http://localhost:9090/` to verify that it starts normally。
+
+
+## Panel Display
+
+It is recommended to use `Grafana`, Users can customize the query to personalize the display panel.
+
+Here's how to install and deploy `Grafana`
+
+### Install Grafana in windows
+
+* Install Grafana
+
+[download](https://dl.grafana.com/oss/release/grafana-7.4.2.windows-amd64.zip) Unzip it and enter the `bin` directory and `double-click` `grafana-server.exe` to run it. Go to http://localhost:3000/?orgId=1 `admin/admin` to verify the success
+
+### Install Grafana in macOS
+
+* Install grafana using brew.
+
+```
+brew install grafana
+```
+
+* Start grafana as a service
+
+```
+brew services start grafana
+```
+
+Visit `http://localhost:3000/` to verify that it starts normally.
+
+### View monitoring data with Grafana
+
+* Configure the data source, select prometheus, note that the data source name is prometheus.
+
+
+
+
+
+* Config Custom Metric Dashboard `request_total`、`http_request_total`
+
+Click `Create` - `Import` and enter the [panel config json](https://shenyu.apache.org/img/shenyu/monitor/request_metric_dashboard.json)
+
+The final custom HTTP request monitoring panel looks like this:
+
+
+
+
+
+
+
+
+
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/proxy/_category_.json b/versioned_docs/version-2.6.1/plugin-center/proxy/_category_.json
new file mode 100644
index 00000000000..09c6722ca65
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/proxy/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Proxy",
+ "position": 2
+}
diff --git a/versioned_docs/version-2.6.1/plugin-center/proxy/divide-plugin.md b/versioned_docs/version-2.6.1/plugin-center/proxy/divide-plugin.md
new file mode 100644
index 00000000000..5afd38ac67c
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/proxy/divide-plugin.md
@@ -0,0 +1,145 @@
+---
+title: Divide Plugin
+keywords: ["divide"]
+description: divide plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* `divide` Plugin
+
+## 1.2 Appropriate Scenario
+
+* Handling `http protocol` requests.
+* Support traffic management, such as a/b test, grayscale test.
+* Service Load Balancing.
+* Set request timeout.
+
+## 1.3 Plugin functionality
+
+* Supports traffic management based on request information such as uri, header, and query.
+* Supports setting the load balancing strategy for requests, and supports service warm-up. Currently, three strategies are supported: ip hash (consistent hash with virtual nodes), round-robbin (weighted polling), random (weighted random).
+* Supports setting the maximum value of the request header, the maximum value of the request body, and the request level timeout.
+* Supports setting the timeout retry policy and the number of retries. Currently, the retry policy supports: current (retrying the server that failed before) and failover (retrying other servers).
+
+## 1.4 Plugin Code
+
+* Core module is ```shenyu-plugin-divide```.
+* Core class is ```org.apache.shenyu.plugin.divide.DividePlugin```.
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+- Import maven in shenyu-bootstrap project's `pom.xml` file.
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-gateway
+ ${project.version}
+
+```
+
+## 2.3 Enable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `divide` set Status enable.
+
+
+
+## 2.4 Config plugin
+
+### 2.4.1 Configure access parameters in the client project configuration file
+
+* Client access method and server address. The following example uses the http access method. Currently, the client supports the following access methods: http, zookeeper, etcd, nacos, consul. For detailed access configuration parameters, please refer to [Client Access Configuration](docs/user-guide/property-config/register-center-access.md).
+* Client configuration, including the protocol name and the routing address of the service, please use the http protocol here, and the value of contextPath must be configured as the routing address of each service.
+
+```yaml
+ shenyu:
+ register:
+ registerType: http
+ serverLists: http://localhost:9095
+ props:
+ username: admin
+ password: 123456
+ client:
+ http: # http protocol
+ props:
+ contextPath: /http # routing address for each service
+```
+
+### 2.4.2 Configure upstream validity detection parameters in the shenyu-admin configuration file
+
+The following example uses the http access method. Currently, the client supports the following access methods: http, zookeeper, etcd, nacos, consul. For detailed access configuration parameters, please refer to [Client Access Configuration](docs/user-guide/property-config/register-center-access.md).
+> Only http-type registries support upstream detection.
+
+```yaml
+ shenyu:
+ register:
+ registerType: http # Only http-type register center support upstream detection.
+ serverLists:
+ props:
+ checked: true # The default is true, set to false, do not detect.
+ zombieCheckTimes: 5 # The maximum number of zombie upstream detections. If it exceeds 5 times, its validity will no longer be detected. The default value is 5.
+ scheduledTime: 10 # Timing detection interval, the default is 10 seconds.
+ zombieRemovalTimes: 60 # How many seconds the upstream is offline to be considered as a zombie upstream, the default is 60 seconds.
+```
+
+### 2.4.3 Configure the selector and rule information of the divide plugin in shenyu-admin
+
+After the client is started, the [selector and rule](../../user-guide/admin-usage/selector-and-rule) information will be automatically registered in shenyu-admin -> Plugin List -> Proxy -> Divide.
+
+
+
+#### 2.4.3.1 Selector configuration
+
+Example of divide selector. For general selector configuration, please refer to [Selectors and Rules](../../user-guide/admin-usage/selector-and-rule).
+
+
+
+##### 2.4.3.1.1 Selector handling information configuration
+
+- `host`: fill in `localhost`, this field is not used currently.
+- `ip:port`: `ip` and port, fill in the `ip` + port of your real service here.
+- `protocol`: `http` protocol, fill in `http:` or `https:`, if not fill in, the default is: `http:`.
+- `startupTime`: Startup time in milliseconds.
+- `weight`: load balancing weight, the default value of service startup automatic registration is 50.
+- `warmupTime`: Warmup time, in milliseconds. The server during warmup will calculate the instantaneous weight, and the calculated value will be smaller than the actual configured weight to protect the server just started. The default value of service startup registration is 10. For example, the warm-up time is 100 milliseconds, the current startup is 50 milliseconds, the configured weight is 50, and the actual weight is 25.
+- `status`: On or off, this selector is valid only in the on state.
+
+#### 2.4.3.2 Processing information configuration of rules
+
+Example of divide rule. For general rule configuration, please refer to [selectors and rules](../../user-guide/admin-usage/selector-and-rule).
+
+
+
+##### 2.4.3.2.1 Rule processing information configuration
+
+- `loadStrategy`: If the `http` client is a cluster, which load balancing strategy is used when the `Apache ShenYu` gateway is called, currently supports `roundRobin`, `random` and `hash`.
+- `timeout`: The timeout for calling the `http` client.
+- `retry Count`: The number of retries that failed to call the `http` client timeout.
+- `headerMaxSize`: The maximum value of the requested `header`.
+- `requestMaxSize`: The maximum value of the request body.
+- `retryStrategy`: Supported since `2.4.3`, retry strategy after failure, default `current` to maintain compatibility with lower versions. For example, there are 3 downstream services `http:localhost:1111`, `http:localhost:1112` and `http:localhost:1113`, assuming the first load balancing to `http:localhost:1111` and `call failed`. Using the `current` strategy will continue to retry calling `http:localhost:1111`; using the `failover` strategy will retry calling other services such as `http:localhost:1112` through the `load balancing`, if it fails again at this time , call to `http:localhost:1113` until no service is available.
+
+## 2.5 Examples
+
+### 2.5.1 Example A/B Test
+
+To be added, welcome contribute.
+
+### 2.5.2 Example Grayscale Test
+
+To be added, welcome contribute.
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `divide` set Status disable.
+
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/proxy/dubbo-plugin.md b/versioned_docs/version-2.6.1/plugin-center/proxy/dubbo-plugin.md
new file mode 100644
index 00000000000..0789ee9690e
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/proxy/dubbo-plugin.md
@@ -0,0 +1,137 @@
+---
+title: Dubbo Plugin
+keywords: ["dubbo"]
+description: dubbo plugin
+---
+
+## Explanation
+
+* Dubbo is a plugin that converts `http protocol` into `Dubbo protocol` and it is also the key for gateway to realize dubbo generic service.
+* Dubbo plugin needs to cooperate with metadata to realize dubbo calls.
+* Apache Dubbo and Alibaba Dubbo users both use the same plugin.
+
+## Plugin Setting
+
+* Add related dependencies and enable plugin, please refer to: [Quick start with Dubbo](../../quick-start/quick-start-dubbo) .
+
+* `Dubbo` client access, please refer to: [Dubbo Proxy](../../user-guide/proxy/dubbo-proxy.md) .
+
+* Set selector and rule, please refer to: [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule) .
+
+* Since `version 2.4.3`, the new fields and meanings of the dubbo plugin:
+
+
+
+ * `corethreads`：The number of core threads in the business thread pool。
+
+ * `queues`：The length of the blocking queue of the business thread pool, 0 means `unbounded blocking queue`。
+
+ * `threadpool`：There are five types of business thread pools: `fixed`, `eager`, `cached`, `limited` and `shared`. The first 4 types correspond to the thread pools officially provided by dubbo. Let's talk about `shared`, as its name implies, `all proxy plugins` share a `shared` thread pool, the advantage of this is that it can reduce the number of thread pools, thereby reducing memory and improving resource utilization。
+
+ * `threads`：The maximum number of threads in the business thread pool。
+
+## Plugin Detail
+
+After the client accesses the `ShenYu` gateway, it will automatically register the selector and rule information. For details about the selector and rule configuration, see [Selector and Rule Config](../../user-guide/admin-usage/selector-and-rule) .
+
+#### Selector Handler
+
+
+
+Selector Handler, the `handle` field, is an operation that can be processed by the gateway after matching the traffic. For more information, please refer to [Plugin handle management](../plugin-handle-explanation) in Plugin Config.
+
+* details：
+
+ * `host`：host string.
+
+ * `ip:port`：ip+port string.
+
+ * `protocol`：protocol default is 'http'.
+
+ * `group`：the group of dubbo service.
+
+ * `version`：the version of dubbo service.
+
+ * `weight`：the server instance and participate in load balancing calculation.
+
+ * `warmupTime`：the server's warm up time and and participate in load balancing calculation.
+
+ * `startupTime`：the server's start time.
+
+ * `status`：true: the server is available，false: the server is unavailable.
+
+ * `gray`：enable gray routing.
+
+Gray routing
+
+if you want to user gray route in dubbo-plugin, you can click the `gray` button.
+
+* Gray level publishing can customize and control the traffic proportion of new version applications when publishing new version applications, gradually complete the full launch of new version applications, maximize the business risk caused by new version publishing, reduce the impact surface caused by faults, and support rapid roll back.
+
+when the gray is open,Gateway load balancing will select one node from the current node list for routing and you can modify node weights to change the weight of nodes in the load balancing algorithm.
+It should be noted that,if your business instance not use the client jar of 'shenyu-client-apache-dubbo' or 'shenyu-client-alibaba-dubbo', You should add gray node information manually on this selector page.
+
+#### Rule Handler
+
+
+
+Rule Handler, the `handle` field, can be performed by the gateway after the final matching of traffic. For more information, please refer to [Plugin handle management](../plugin-handle-explanation) in Plugin Config.
+
+* details：
+
+ * `loadbalance`：the loadbalance of dubbo service, if the gray node selection fails, the default load balancing method will be used.
+
+* Apache ShenYu will obtain the real IP of the corresponding service and initiate rpc proxy calls from registration center of dubbo.
+
+
+## Metadata
+
+* Every dubbo interface method corresponds to a piece of metadata, which can be found in `shenyu-admin` --> BasicConfig -> Metadata .
+
+
+
+* AppName: The name of the application to which this piece of metadata belongs.
+
+* MethodName: The name of the method that needs to be called.
+
+* Path: your http request path.
+
+* PathDescribe: Description of the path, for easy viewing.
+
+* ParamsType: List of parameter types of dubbo interface, there are two declaration methods here:
+ e.g. we have an interface `update(Integer id, String name, Integer age)`
+
+ * Type list
+
+ ```yaml
+ java.lang.Integer,java.lang.String,java.lang.Integer
+ ```
+
+ * According to the order of the parameter types of the interface, separated by `,`
+
+ * When requesting to pass parameters, **the parameters must be passed in strictly in accordance with the order of the parameter types**, if a parameter without value use `null` as a placeholder.
+
+ Request body example: `{"id":1,"name": null,"age":18}`
+
+ * Name mapping
+
+ ```yaml
+ {"id":"java.lang.Integer","name":"java.lang.String","age":"java.lang.Integer"}
+ ```
+
+ * Use `"parameter name":"parameter type"` to represent a parameter, set in order of interface parameter type, separated by `,`
+
+ * No need to pay attention to the order when requesting, and no need to use null placeholders.
+
+ Request body example: `{"name":"Mike","id":1}`
+
+* RpcExpand: corresponding to some configurations of dubbo interface; If you want to adjust, please modify here, which support json format like the following fields:
+
+```yaml
+{"timeout":10000,"group":"",version":"","loadbalance":"","retries":1}
+```
+
+* Interface: The fully-qualified name for dubbo interface .
+
+* RpcType: Choose `dubbo` .
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/proxy/grpc-plugin.md b/versioned_docs/version-2.6.1/plugin-center/proxy/grpc-plugin.md
new file mode 100644
index 00000000000..85a298e66c1
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/proxy/grpc-plugin.md
@@ -0,0 +1,81 @@
+---
+title: gRPC Plugin
+keywords: ["grpc-plugin"]
+description: grpc-plugin
+---
+
+
+## Description
+
+* The grpc plugin is a plugin that converts the Http protocol into the grpc protocol.
+
+
+## Plugin Setting
+
+* Add related dependencies and enable plugin, please refer to: [Quick start with gRPC](../../quick-start/quick-start-grpc) .
+
+* `gRPC` client access, please refer to: [gRPC Proxy](../../user-guide/proxy/grpc-proxy.md) .
+
+* New fields and meanings of grpc plugin since `2.4.3`:
+
+ * `threadpool`：There are two types of business thread pools, `cached` and `shared`.
+
+ `cached` is equivalent to the default thread pool officially provided by grpc;
+
+ `shared` thread pool, just as its name, `all proxy plugins` share a `shared` `Thread pool, the advantage of doing this is that it can reduce the number of thread pools, thereby reducing memory and improving resource utilization.
+
+
+## Plugin Detail
+
+
+After the client accesses the `Apache ShenYu` gateway, it will automatically register the selector and rule information. You can see it in PluginList -> rpc proxy -> grpc. For details about the selector and rule configuration, see [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule) .
+
+
+#### Selector Handler
+
+
+
+
+Selector Handler, the `handle` field, is the processing operation that the gateway can perform after matching the traffic.
+
+
+* config details：
+
+ * `ip:port`：enter the ip:port of your real service .
+
+ * `protocol`：indicates the Http protocol. Generally, the value is `http://` or `https://`. If the value is not specified, the default value is `http://` .
+
+ * `weight`：service weight.
+
+ * `status`：open or close.
+
+
+## Metadata
+
+Each `grpc` interface method, will correspond to a metadata, when the `grpc` application client access to the `Apache ShenYu` gateway, will be automatically registered, can be viewed in the `shenyu-admin` background management system of the BasicConfig --> Metadata management.
+
+
+
+
+* AppName: specifies the name of the application to which the metadata belongs.
+
+* MethodName: the name of the method to call.
+
+* Path: http request path.
+
+* PathDescribe: the description of the path is easy to view.
+
+* ParamsType: the parameters are separated by commas (,) in the order of interface parameter types.
+
+* RpcExpand: other configurations of the `grpc` interface, which support the `JSON` format, are as follows:
+
+```json
+{
+ "timeout": 5000,
+ "methodType": "SERVER_STREAMING"
+}
+```
+
+* Interface: The fully qualified class name of the `grpc` interface.
+
+* RpcType：choose `grpc`.
diff --git a/versioned_docs/version-2.6.1/plugin-center/proxy/motan-plugin.md b/versioned_docs/version-2.6.1/plugin-center/proxy/motan-plugin.md
new file mode 100644
index 00000000000..e94e497c266
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/proxy/motan-plugin.md
@@ -0,0 +1,68 @@
+---
+title: Motan Plugin
+keywords: ["motan-plugin"]
+description: motan-plugin
+---
+
+
+## Description
+
+* The motan plugin is a plugin that converts the Http protocol into the motan protocol.
+
+
+## Plugin Setting
+
+* Add related dependencies and enable plugin, please refer to: [Quick start with Motan](../../quick-start/quick-start-motan) .
+
+* `Motan` client access, please refer to: [Motan Proxy](../../user-guide/proxy/motan-proxy.md) .
+
+
+
+## Plugin Detail
+
+After the client accesses the `Apache ShenYu` gateway, it will automatically register the selector and rule information.
+
+You can see it in PluginList -> rpc proxy -> motan. For details about the selector and rule configuration, see [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule) .
+
+## Metadata
+
+Each `motan` interface method, will correspond to a metadata, when the `motan` application client access to the `Apache ShenYu` gateway, will be automatically registered, can be viewed in the `shenyu-admin` background management system of the BasicConfig --> Metadata management.
+
+
+
+
+* AppName: specifies the name of the application to which the metadata belongs.
+
+* MethodName: the name of the method to call.
+
+* Path: http request path.
+
+* PathDescribe: the description of the path is easy to view.
+
+* ParamsType: the parameters are separated by commas (,) in the order of interface parameter types.
+
+* RpcExpand: description of each interface in a `motan` service. For example, here is the interface information for the `motan` service:
+
+
+
+```json
+{
+ "methodInfo": [
+ {
+ "methodName": "hello",
+ "params": [
+ {
+ "left": "java.lang.String",
+ "right": "name"
+ }
+ ]
+ }
+ ],
+ "group": "motan-shenyu-rpc"
+}
+```
+
+
+* Interface: The fully qualified class name of the `motan` interface.
+
+* RpcType：choose `motan`.
diff --git a/versioned_docs/version-2.6.1/plugin-center/proxy/mqtt-plugin.md b/versioned_docs/version-2.6.1/plugin-center/proxy/mqtt-plugin.md
new file mode 100644
index 00000000000..07f49b2f40d
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/proxy/mqtt-plugin.md
@@ -0,0 +1,46 @@
+---
+title: Mqtt Plugin
+keywords: ["Mqtt"]
+description: Mqtt access shenyu gateway
+---
+
+## Description
+
+* After the plugin is used, it will give the ability of mqtt.
+
+## Introducing Plugin Support of Mqtt Gateway
+
+* Introducing those dependencies in the pom.xml file of the gateway.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-mqtt
+ ${project.version}
+
+```
+
+## Plugin Setting
+
+* port: MQTT BS port designation.
+
+* bossGroupThreadCount: default 1.
+
+* maxPayloadSize: Maximum packet size.
+
+* workerGroupThreadCount: default 12.
+
+* username: default shenyu.
+
+* password: default shenyu.
+
+* isEncryptPassword: The default is false , whether to encrypt the password.
+
+* encryptMode: encryption mode, currently only MD5 is implemented, the encryption mode can be customized, `org.apache.shenyu.protocol.mqtt.utils.EncryptUtil` view the implementation of this encryption class.
+
+* leakDetectorLevel: default DISABLED, resource target detection or detection level.
+
+## Notice
+
+* Mqtt does not have selector and ruler configurations.
diff --git a/versioned_docs/version-2.6.1/plugin-center/proxy/sofa-plugin.md b/versioned_docs/version-2.6.1/plugin-center/proxy/sofa-plugin.md
new file mode 100644
index 00000000000..b0b86cc58a8
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/proxy/sofa-plugin.md
@@ -0,0 +1,213 @@
+---
+title: Sofa Plugin
+keywords: ["sofa"]
+description: Sofa Plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin name
+
+- Sofa plugin
+
+## 1.2 Appropriate scenario
+
+- Protocol conversion, a plugin that converts http protocol requests into the sofa framework protocol
+- Service Load Balancing.
+
+## 1.3 Plugin functionality
+
+- Converting http protocol requests to sofa framework protocol.
+
+## 1.4 Plugin code
+
+- Core Module `shenyu-plugin-sofa`
+- Core Class `org.apache.shenyu.plugin.sofa.SofaPlugin`
+
+## 1.5 Added since which shenyu version
+
+- 2.3.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+```xml
+
+ com.alipay.sofa
+ rpc-sofa-boot-starter
+ ${rpc-sofa-boot-starter.version}
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-sofa
+ ${project.version}
+
+
+ guava
+ com.google.guava
+
+
+
+```
+
+## 2.3 Configure in the client project
+
+1. Configure the sofa configuration in application.yml.
+
+```yaml
+com:
+ alipay:
+ sofa:
+ rpc:
+ registry-address: zookeeper://127.0.0.1:2181 # consul # nacos
+ bolt-port: 8888
+shenyu:
+ register:
+ registerType: http #zookeeper #etcd #nacos #consul
+ serverLists: http://localhost:9095 #localhost:2181 #http://localhost:2379 #localhost:8848
+ props:
+ username: admin
+ password: 123456
+ client:
+ sofa:
+ props:
+ contextPath: /sofa
+ ipAndPort: sofa
+ appName: sofa
+ port: 8888
+```
+
+2. Configure the service interface exposed by the sofa service in the xml file in the resources directory.
+
+```xml
+
+
+
+
+
+
+
+
+
+
+```
+
+3. Add the `@ShenyuSofaClient` annotation to the interface.
+
+```java
+@ShenyuSofaClient("/demo")
+@Service
+public class SofaClientMultiParamServiceImpl implements SofaClientMultiParamService {
+
+ @Override
+ @ShenyuSofaClient("/findByIdsAndName")
+ public SofaSimpleTypeBean findByIdsAndName(final List ids, final String name) {
+ return new SofaSimpleTypeBean(ids.toString(), "hello world shenyu sofa param findByIdsAndName ：" + name);
+ }
+}
+```
+
+## 2.4 Enable plugin
+
+- In shenyu-admin --> BasicConfig --> Plugin --> `sofa` set Status enabled.
+
+ 
+
+
+## 2.5 Config plugin
+
+### 2.5.1 Registry Config
+
+
+
+- `protocol`: Register center protocol, currently supports zookeeper、consul、nacos.
+- `register`: The service IP and PORT of the registry.
+- `threadpool`：There are five types of business thread pools: `fixed`, `eager`, `cached`, `limited` and `shared`. The first 4 types correspond to the thread pools officially provided by dubbo. Let's talk about `shared`, as its name implies, `all proxy plugins` share a `shared` thread pool, the advantage of this is that it can reduce the number of thread pools, thereby reducing memory and improving resource utilization.
+- `corethreads`：The number of core threads in the business thread pool.
+- `threads`：The maximum number of threads in the business thread pool.
+- `queues`：The length of the blocking queue of the business thread pool, 0 means `unbounded blocking queue`.
+
+### 2.5.2 Selector config
+
+> Flow needs to be matched by selector.
+
+
+
+- Automatically configure the selector with the `@ShenyuSofaClient` annotation.
+
+### 2.5.3 Rule Config
+
+> After the traffic has been successfully matched by the selector, it will enter the rules for the final traffic matching.
+
+
+
+- Automatically configure the selector with the `@ShenyuSofaClient` annotation.
+
+### 2.5.4 Metadata config
+
+> When the `sofa` application client accesses the `Apache ShenYu` gateway, it will be automatically registered, and can be viewed in the `-shenyu-admin` backend management system's basic configuration `-->` metadata management, each `sofa` interface method, will correspond to a metadata.
+
+
+
+- AppName: specifies the name of the application to which the metadata belongs.
+
+- MethodName: the name of the method to call.
+
+- Path: http request path.
+
+- PathDescribe: the description of the path is easy to view.
+
+- ParamsType: the parameters are separated by commas (,) in the order of interface parameter types.
+
+- RpcExpand: other configurations of the `sofa` interface, which support the `JSON` format.
+
+ examples：`{"loadbalance":"hash","retries":3,"timeout":-1}`
+
+ - `loadbalance`：Load balancing policy, currently supports roundRobin, random and hash.
+ - `retries`：Number of retries to call client timeout failures.
+ - `timeout`：Calling the client's timeout time.
+
+- Interface: The fully qualified class name of the `sofa` interface.
+
+- RpcType：choose `sofa`.
+
+## 2.6 Examples
+
+### 2.6.1 Accessing the sofa service via Zookeeper using ShenYu
+
+#### 2.6.1.1 Preparation
+
+- Start `Zookeeper` service.
+- Start `ShenYu Admin`.
+- Start `Shenyu Bootstrap`.
+
+#### 2.6.1.2 Plugin Config
+
+- In shenyu-admin --> BasicConfig --> Plugin --> `sofa` set Status enabled, And adjust the registry configuration as needed.
+- Adjust to the actual situation [shenyu-examples-sofa](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-sofa) application.yml configuration in the project and start it.
+
+#### 2.6.2.6 Request service and check result
+
+
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `sofa` set Status disable.
+
+
+
+
+
+
+
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/proxy/spring-cloud-plugin.md b/versioned_docs/version-2.6.1/plugin-center/proxy/spring-cloud-plugin.md
new file mode 100644
index 00000000000..82412c203c3
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/proxy/spring-cloud-plugin.md
@@ -0,0 +1,317 @@
+---
+title: Spring Cloud Plugin
+keywords: ["SpringCloud"]
+description: SpringCloud Plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* SpringCloud Plugin
+
+## 1.2 Appropriate Scenario
+
+* transform http to springcloud
+* springcloud gray flow control
+
+## 1.3 Plugin functionality
+
+* transform http protocol into springCloud protocol.
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-springcloud`
+
+* Core Class `org.apache.shenyu.plugin.springcloud.SpringCloudPlugin`
+
+## 1.5 Added Since Which shenyu version
+
+Since ShenYu 2.4.0
+
+# 2. How to use plugin
+
+* Add related dependencies and enable plugin, please refer to: [Quick start with Spring Cloud](../../quick-start/quick-start-springcloud) .
+
+* `Spring Cloud` client access, please refer to: [Spring Cloud Proxy](../../user-guide/proxy/spring-cloud-proxy.md) .
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+* Eureka Registry
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-springcloud
+ ${project.version}
+
+
+
+ org.springframework.cloud
+ spring-cloud-starter-netflix-eureka-client
+ ${eureka-client.version}
+
+
+
+ org.springframework.cloud
+ spring-cloud-commons
+ ${spring-cloud-commons.version}
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-httpclient
+ ${project.version}
+
+```
+
+* Nacos Registry
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-springcloud
+ ${project.version}
+
+
+
+ com.alibaba.cloud
+ spring-cloud-starter-alibaba-nacos-discovery
+ ${nacos-discovery.version}
+
+
+
+ org.springframework.cloud
+ spring-cloud-commons
+ ${spring-cloud-commons.version}
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-httpclient
+ ${project.version}
+
+```
+
+## 2.3 Config SpringCloud in ShenYu-Boostrap
+
+### 2.3.1 Config SpringCloud Registry With Eureka
+
+```yaml
+spring:
+ cloud:
+ discovery:
+ enabled: true
+
+eureka:
+ client:
+ enabled: true
+ serviceUrl:
+ defaultZone: http://localhost:8761/eureka/
+ instance:
+ prefer-ip-address: true
+```
+
+### 2.3.2 Config SpringCloud Registry With Nacos
+
+```yaml
+spring:
+ cloud:
+ discovery:
+ enabled: true
+ nacos:
+ discovery:
+ server-addr: 127.0.0.1:8848 # Spring Cloud Alibaba Dubbo use this.
+ enabled: true
+ namespace: ShenyuRegisterCenter
+```
+
+### 2.3.3 Config SpringCloud LoadBalancer
+
+> *Notice*
+>
+> After ShenYu 2.5.0(include), ShenYu use `shenyu-loadbalancer` as loadbalancer client, you just config loadbalance in springcloud plugin rule.
+> if you don't config loadbalance, springcloud plugin will use `roundRobin` algorithm.
+>
+> Before ShenYu 2.4.3(include), ShenYu use `Ribbon` as loadbalancer client, you must config loadbalancer as follows.
+
+```yaml
+spring:
+ cloud:
+ loadbalancer:
+ ribbon:
+ enabled: true
+```
+
+## 2.4 Enable plugin
+
+- In shenyu-admin --> BasicConfig --> Plugin --> `springCloud` set Status enabled.
+
+
+
+## 2.5 Config plugin
+
+### 2.5.1 Plugin config
+
+* you must config springcloud registry and set springcloud plugin enabled.
+
+### 2.5.2 Selector And Gray Config
+
+
+
+* Gray routing
+
+if you want to user gray route in springCloud-plugin, you can click the `gray` button.
+
+
+
+* Gray level publishing can customize and control the traffic proportion of new version applications when publishing new version applications, gradually complete the full launch of new version applications, maximize the business risk caused by new version publishing, reduce the impact surface caused by faults, and support rapid roll back.
+
+when the gray is open,Gateway load balancing will select one node from the current node list for routing and you can modify node weights to change the weight of nodes in the load balancing algorithm.
+
+
+
+It should be noted that,if your business instance not use the client jar of `shenyu-client-springcloud`, You should add gray node information manually on this selector page.
+
+* `serviceId`: your springcloud service id
+
+* `gray`：enable gray routing.
+
+ * `protocol`: protocol default is 'http://'.
+
+ * `upstreamUrl`: the server instance host, ip:port.
+
+ * `weight`: the server instance and participate in load balancing calculation.
+
+ * `status`: true: the server is available，false: the server is unavailable.
+
+ * `timestamp`: the server's start time.
+
+ * `warmup`: the server's warm up time and and participate in load balancing calculation.
+
+### 2.5.3 Rule Config
+
+Rule Handler, the `handle` field, can be performed by the gateway after the final matching of traffic. For more information, please refer to [Plugin handle management](../plugin-handle-explanation) in Plugin Config.
+
+* use `shenyu-client-springcloud` rule config
+
+
+
+* details：
+
+ * `timeout`：set time out.
+ * `loadbalance`：loadbalance algorithm,there are three options: `roundRobin`,`random`,`hash`
+
+* not use `shenyu-client-springcloud` rule config
+
+
+
+* details：
+
+ * `path`：request path.
+ * `timeout`：set time out.
+
+### 2.5.4 SpringCloud ServiceInstance Cache Config
+
+you can config springcloud serviceInstance cache in `shenyu-bootstrap.yml` as follows.
+
+```yaml
+shenyu:
+ springCloudCache:
+ enabled: false
+```
+
+this config will help you get serviceInstance from springcloud registry every heartbeat time(listen to spring cloud heartbeat event)
+
+* when you use nacos or eureka as registry, you can config springcloud serviceInstance cache to `false`.
+* when you use zookeeper or consul as registry, you can config springcloud serviceInstance cache to `true`.
+
+## 2.6 Examples
+
+### 2.6.1 Use ShenYu Request SpringCloud Service
+
+#### 2.6.1.1 Preparation
+
+- Start `Eureka` or `Nacos` Registry, if you use eureka, start `shenyu-examples-eureka` in `shenyu-example`
+- Start `ShenYu Admin` application
+- Start `shenyu-examples-springcloud`
+
+#### 2.6.1.2 Plugin Config
+
+- In shenyu-admin --> BasicConfig --> Plugin --> `springCloud` set Status enabled.
+
+- Config SpringCloud Registry in `ShenYu Bootstrap`, please read [2.3 Config SpringCloud in ShenYu-Boostrap](#2.3 Config SpringCloud in ShenYu-Boostrap)
+
+#### 2.6.1.3 Selector Config
+
+
+
+if your want to use gray flow and the gray flow have registered to `ShenyYu`, you must config gray upstream as follows.
+
+
+
+#### 2.6.1.4 Rule Config
+
+if you use `shenyu-client-springcloud` register service to `ShenYu`, you don't config rule, if you want to change rule config,
+please read [2.5.3 Rule Config](#2.5.3 Rule Config)
+
+#### 2.6.1.5 Request SpringCloud Service and Check Result
+
+
+
+### 2.6.2 Use ShenYu Request Unregistered SpringCloud Service
+
+#### 2.6.2.1 Preparation
+
+- Start `Eureka` or `Nacos` Registry, if you use eureka, start `shenyu-examples-eureka` in `shenyu-example`
+- Start `ShenYu Admin` application
+- Start `shenyu-examples-springcloud`
+
+#### 2.6.2.2 Plugin Config
+
+- In shenyu-admin --> BasicConfig --> Plugin --> `springCloud` set Status enabled.
+
+- Config SpringCloud Registry in `ShenYu Bootstrap`, please read [2.3 Config SpringCloud in ShenYu-Boostrap](#2.3 Config SpringCloud in ShenYu-Boostrap)
+
+#### 2.6.2.3 Selector Config
+
+
+
+if your want to use gray flow and the gray flow unregister to `ShenyYu`, you must config gray upstream as follows.
+
+
+
+#### 2.6.2.4 Rule Config
+
+
+
+you must config `path` in rule config, `path` is your service uri, for example: `/springcloud/new/feature/gateway/not`,
+`timeout` is your service allow timeout.
+
+#### 2.6.2.5 Access Unregistered Services Through Configuration
+
+##### 2.6.2.5.1 use the field `rpc_type` in http request header
+
+```
+### shengyu getway proxy not support
+POST http://localhost:9195/springcloud/new/feature/gateway/not
+Accept: application/json
+Content-Type: application/json
+rpc_type: springCloud
+```
+
+##### 2.6.2.5.2 add meta_data in ShenYu Admin
+
+
+
+#### 2.6.2.6 Request SpringCloud Service and Check Result
+
+
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `springCloud` set Status disable.
diff --git a/versioned_docs/version-2.6.1/plugin-center/proxy/tars-plugin.md b/versioned_docs/version-2.6.1/plugin-center/proxy/tars-plugin.md
new file mode 100644
index 00000000000..fd9c3628b02
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/proxy/tars-plugin.md
@@ -0,0 +1,170 @@
+---
+title: Tars Plugin
+keywords: ["Tars"]
+description: Tars Plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin name
+
+- Tars plugin
+
+## 1.2 Appropriate scenario
+
+- Protocol conversion, a plugin that converts http protocol requests into the Tars framework protocol
+- Service Load Balancing.
+
+## 1.3 Plugin functionality
+
+- Converting http protocol requests to Tars framework protocol.
+
+## 1.4 Plugin code
+
+- Core Module `shenyu-plugin-tars`
+- Core Class `org.apache.shenyu.plugin.tars.TarsPlugin`
+
+## 1.5 Added since which shenyu version
+
+- 2.3.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-tars
+ ${shenyu.version}
+
+```
+
+## 2.3 Configure in the client project
+
+1. Configure the Tars configuration in application.yml.
+
+```yaml
+shenyu:
+ register:
+ registerType: http #zookeeper #etcd #nacos #consul
+ serverLists: http://localhost:9095 #localhost:2181 #http://localhost:2379 #localhost:8848
+ props:
+ username: admin
+ password: 123456
+ client:
+ tars:
+ props:
+ contextPath: /tars
+ appName: tars
+ port: 21715
+ host: 192.168.41.103 # client IP
+```
+
+2. Add the `@ShenyuTarsService` and `@ShenyuTarsClient` and annotation to the interface.
+
+```java
+@TarsServant("HelloObj")
+@ShenyuTarsService(serviceName = "ShenyuExampleServer.ShenyuExampleApp.HelloObj")
+public class HelloServantImpl implements HelloServant {
+
+ @Override
+ @ShenyuTarsClient("/hello")
+ public String hello(final int no, final String name) {
+ return String.format("hello no=%s, name=%s, time=%s", no, name, System.currentTimeMillis());
+ }
+}
+```
+
+
+## 2.4 Enable plugin
+
+- In shenyu-admin --> BasicConfig --> Plugin --> `tars` set Status enabled.
+
+
+
+
+## 2.5 Config plugin
+
+### 2.5.1 Config plugin
+
+
+
+- `multiSelectorHandle`：Set to enable multiple selector processing, multiple selector processing services can be configured in the selector list.
+- `multiRuleHandle`：Set to multiple rules processing, configure multiple processing rules in the rule list, it is recommended to configure as single rule.
+- `threadpool`：There are five types of business thread pools: `fixed`, `eager`, `cached`, `limited` and `shared`. The first 4 types correspond to the thread pools officially provided by dubbo. Let's talk about `shared`, as its name implies, `all proxy plugins` share a `shared` thread pool, the advantage of this is that it can reduce the number of thread pools, thereby reducing memory and improving resource utilization.
+- `corethreads`：The number of core threads in the business thread pool.
+- `threads`：The maximum number of threads in the business thread pool.
+- `queues`：The length of the blocking queue of the business thread pool, 0 means `unbounded blocking queue`.
+
+### 2.5.2 Selector config
+
+> Flow needs to be matched by selector.
+
+
+
+Automatically configure the selectors with the `@ShenyuTarsClient` annotation.
+
+### 2.5.3 Rule Config
+
+> After the traffic has been successfully matched by the selector, it will enter the rules for the final traffic matching.
+
+
+
+Automatically configure the rules with the `@ShenyuTarsClient` annotation.
+
+### 2.5.4 Metadata config
+
+> When the `Tars` application client accesses the `Apache ShenYu` gateway, it will be automatically registered, and can be viewed in the `shenyu-admin` backend management system's basic configuration `-->` metadata management, each `Tars` interface method, will correspond to a metadata.
+
+
+
+- AppName: specifies the name of the application to which the metadata belongs.
+
+- MethodName: the name of the method to call.
+
+- Path: http request path.
+
+- PathDescribe: the description of the path is easy to view.
+
+- ParamsType: the parameters are separated by commas (,) in the order of interface parameter types.
+
+- RpcExpand: other configurations of the `Tars` interface, which support the `JSON` format.
+
+ examples：`{"loadbalance":"hash","retries":3,"timeout":-1}`
+
+ - `loadbalance`：Load balancing policy, currently supports roundRobin, random and hash.
+ - `retries`：Number of retries to call client timeout failures.
+ - `timeout`：Calling the client's timeout time.
+
+- Interface: The fully qualified class name of the `Tars` interface.
+
+- RpcType：Auto-registration defaults to `Tars`.
+
+## 2.6 Examples
+
+### 2.6.1 Using ShenYu to access the Tars service
+
+#### 2.6.1.1 Preparation
+
+- Start `ShenYu Admin`.
+- Start `Shenyu Bootstrap`.
+
+#### 2.6.1.2 Plugin Config
+
+- In shenyu-admin --> BasicConfig --> Plugin --> `tars` set Status enabled, And adjust the registry configuration as needed.
+- Adjust to the actual situation [shenyu-examples-tars](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-tars) application.yml configuration in the project and start it.
+
+#### 2.6.2.6 Request service and check result
+
+
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `tars` set Status disable.
+
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/proxy/tcp-plugin.md b/versioned_docs/version-2.6.1/plugin-center/proxy/tcp-plugin.md
new file mode 100644
index 00000000000..a7b3724e3c5
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/proxy/tcp-plugin.md
@@ -0,0 +1,156 @@
+---
+title: Tcp Plugin
+keywords: [ "Tcp" ]
+description: TcpPlugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin name
+
+- TCP Plugin
+
+## 1.2 Appropriate Scenario
+
+- Process TCP protocol requests and forward them to backend services of other TCP protocols
+- Service load balancing
+
+## 1.3 Plugin functionality
+
+* Supports TCP proxy based on configured upstream list
+* The upstream list can be hot-synchronized to the gateway by the admin module
+* Support setting load balancing policy for requests, currently support shenyu load balancing module policy
+* Configurable open port for listening, configurable reactor-netty parameter
+* Enable multiple proxy selectors
+
+> __Note__: When a connection is established with the gateway, after the connection is established, the traffic continues to stay in the upstream that has been selected by the load balancing module
+
+## 1.4 Plugin code
+
+- Core Module: `shenyu-plugin-tcp` `shenyu-protocol-tcp`
+
+## 1.5 Added since which shenyu version
+
+- 2.6.0
+
+# 2. How to use plugin
+
+## 2.1 Enable plugin
+
+- When using it for the first time, start the admin server,
+in `shenyu-admin` --> BasicConfig --> Plugin, search for the tcp plugin and click "Resource" to activate the TCP plugin module.
+
+
+
+- In `shenyu-admin` --> BasicConfig--> Plugin --> `tcp`, set status enabled.
+
+
+
+## 2.2 Configure plugin
+
+- The TCP plugin is created in units of proxy-selectors, so configuring the plugin is to configure the properties of the proxy-selector.
+When creating a proxy-selector, click the "Add" button on the page, and in the pop-up selector form, you can configure the selector properties:
+
+
+
+The default configuration is as follows:
+
+```json
+{
+ "loadBalanceAlgorithm": "random",
+ "bossGroupThreadCount": "1",
+ "workerGroupThreadCount": "12",
+ "clientMaxConnections": "20",
+ "clientMaxIdleTimeMs": "30000",
+ "clientMaxLifeTimeMs": "60000",
+ "clientPendingAcquireTimeout": "5",
+ "clientPendingAcquireMaxCount": "5"
+}
+```
+
+- `loadBalanceAlgorithm` : shenyu load balancing algorithm, random by default
+- `bossGroupThreadCount` , `workerGroupThreadCount`:
+ReactorNetty TcpServer For configuration details, see `shenyu-protocol-tcp#TcpBootstrapServer#start` for details
+- `clientMaxConnections` , `clientMaxIdleTimeMs` , `clientMaxLifeTimeMs` , `clientPendingAcquireTimeout` ,
+ `clientPendingAcquireMaxCount`
+ReactorNetty `ConnectionProvider` , see `shenyu-protocol-tcp#ConnectionContext` for details
+
+You can search for the tcp plugin in `shenyu-admin` --> BasicConfig --> PluginHandle, and modify the default configuration:
+
+
+
+## 2.3 Configure service discovery
+
+`discovery` see [discovery-mode](../discovery/discovery-mode.md)
+
+The TCP plugin supports two levels of discovery configuration: plugin-level and selector-level:
+
+① You can click the "Discovery Configuration" button on the page to configure plugin-level discovery in the pop-up form.
+After the configuration is complete, you can open the form again to modify or delete the previous configuration.
+After the plug-in level discovery is configured, the discovery settings of the selectors are consistent with the plugin-level config by default:
+
+
+
+② If you have not configured plugin-level discovery,
+you can configure the selector-level discovery every time you create a proxy-selector:
+
+
+
+Discovery `Zookeeper` and `Local` modes are currently supported.
+
+### 2.3.1 Zookeeper Mode
+
+
+- When the type of service Discovery is Zookeeper, you need to fill out the Discovery-ZooKeeper configuration training for details [discovery-mode](../discovery/discovery-mode.md)
+
+- In zookeeper mode, the discovery module will automatically monitor the user's zookeeper registration center
+and automatically maintain discovery upstreams:
+
+
+
+### 2.3.2 Local Mode
+
+- When "local" is selected as the discovery type,
+you need to manually fill in the discovery upstream list.
+As shown in the figure below, the discovery upstream list is an editable table.
+ Double-click each cell to modify the table content:
+
+
+
+## 2.4 Configure selectors
+
+- In addition to the discovery configuration above, when creating a selector,
+you also need to fill in the "basic config" part of the selector,
+including name and forward port, etc. In order to improve the convenience of filling in,
+you can click "Copy Selector" to copy part of the information of the created selector.
+
+> __Note__: The name of the selector uniquely identifies the selector and cannot be repeated
+
+
+
+- After the selectors are created,
+the selectors are displayed in the form of cards.
+When the mouse hovers over the cards, the creation time, update time and properties of the selectors will be displayed.
+ At the bottom of the card there are three clickable icons, from left to right the Sync, Edit, and Delete selector icons:
+
+
+
+
+- If there is difference between the discovery upstream list of the current admin and the gateway,
+you can click the "Sync" icon to force synchronization to the gateway.
+
+
+## 2.5 Shenyu log
+
+- shenyu-gateway port start log
+
+
+- shenyu-gateway proxy upstreamList‘s success log
+
+
+## 2.6 Example
+
+Take proxying redis as an example, use `redis-cli -p {forwardPort}` to access.
+
+
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/proxy/websocket-plugin.md b/versioned_docs/version-2.6.1/plugin-center/proxy/websocket-plugin.md
new file mode 100644
index 00000000000..5fd8651b671
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/proxy/websocket-plugin.md
@@ -0,0 +1,277 @@
+---
+title: Websocket Plugin
+keywords: ["Websocket"]
+description: Websocket Plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Websocket Plugin.
+
+## 1.2 Appropriate Scenario
+
+* Forwarding scenarios, processing websocket protocol requests and forwarding them to other websocket protocol services on the backend.
+* Service Load Balancing.
+
+## 1.3 Plugin functionality
+
+* Support traffic management based on host, uri, query and other request information.
+* Supports setting load balancing policies for requests and also supports service warm-up, currently supports three policies: ip hash (consistent hashing with virtual nodes), round-robbin (weighted polling), random (weighted random).
+* Support setting interface level request timeout time.
+* Support setting the number of timeout retries.
+
+## 1.4 Plugin code
+
+* Core Module ```shenyu-plugin-websocket```.
+* Core Class ```org.apache.shenyu.plugin.websocket.WebSocketPlugin```.
+
+## 1.5 Added Since Which shenyu version
+
+- 2.4.3
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+**Explanation of terms**
+- Shenyu gateway service：Include shenyu-admin and shenyu-bootstrap services.
+- Client services：Real backend websocket service.
+
+**Explanation of the process**
+1. Start shenyu gateway service: Refer to the deployment, start shenyu-admin and shenyu-bootstrap to make sure shenyu gateway service is normal.
+2. Enable the websocket plugin in shenyu-admin: Turn on the websocket plugin in the shenyu-admin plugin management page.
+3. Configure and start the client service: start the client project (real websocket service on the back end) and configure the service information into the shenyu gateway, in two ways: manual configuration and automatic configuration.
+4. Check if forwarding is normal: Check if forwarding is successful.
+
+## 2.2 Enable plugin
+
+- In shenyu-admin --> BasicConfig --> Plugin --> websocket is set to on.
+
+
+
+
+## 2.3 Client Services configuration
+
+### 2.3.1 Manual configuration
+
+> Manually configure the client service on the shenyu-admin page, and the backend service will implement the websocket protocol forwarding without any changes.
+
+1. Adding selectors to the websocket plugin.
+
+
+
+2. Add rules to the websocket plugin.
+
+
+
+3. Start the client service (backend websocket service).
+
+4. Test the success of service forwarding.
+
+- See Annex 5.1 for the test code.
+
+
+
+### 2.3.2 Automatic configuration
+
+> If there are scenarios where you need to automate configuration to reduce workload, you can add annotations to the backend service to automate the configuration of the service to the shenyu gateway.
+
+1. Add the plugin maven configuration to the pom.xml file in the backend service project.
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-websocket
+ ${project.version}
+
+```
+
+2. Use the `@ShenyuSpringWebSocketClient` annotation, which will automatically register the websocket service to the shenyu gateway.
+3. Adjust the plugin configuration, see 2.4.1 for details of the configuration parameters.
+4. Start the client project (the backend `websocket service), see 2.5 for sample code.
+5. Check whether the PluginList service registration information in the shenyu-admin page is registered successfully.
+6. Test the success of service forwarding.
+
+- See Annex 5.1 for the test code.
+
+
+
+## 2.4 Config plugin
+
+### 2.4.1 Configure access parameters in the configuration file in the client service
+
+* Client access method and server address, the parameters are: `shenyu.register.*`, the following example uses the http access method, currently the client supports the following access methods: http, zookeeper, etcd, nacos, consul, please refer to [client access configuration](../../user-guide/property-config/register-center-access) for detailed access configuration parameters.
+* Client configuration with the parameter: `shenyu.client.websocket.*`, containing the service name, routing address and port, and the contextPath value must be configured as the routing address for each service.
+
+```yaml
+shenyu:
+ register:
+ registerType: http
+ serverLists: http://localhost:9095
+ props:
+ username: admin
+ password: 123456
+ client:
+ websocket:
+ props:
+ contextPath: /ws-annotation
+ appName: ws-annotation
+ port: 8001 # Need to be consistent with the service port
+```
+
+### 2.4.2 Configure the websocket plugin's selector and rule information in shenyu-admin
+
+Using auto-configuration, after the client starts it will automatically register [selectors and rules](../../user-guide/admin-usage/selector-and-rule.md) in shenyu-admin -> Plugin List -> Proxy -> Websocket information.
+
+
+#### 2.4.2.1 Configuration of selectors
+
+The example of websocket selector configuration, please refer to [selectors and rules](../../user-guide/admin-usage/selector-and-rule.md) for general selector configuration.
+
+
+
+##### 2.4.2.1.1 Selector handler configuration
+
+- `host`：Fill in `localhost`, this field is not used for now.
+- `ip:port`：`ip` and port, here fill in the `ip` + port of your real service.
+- `protocol`：`ws` protocol, do not fill in the default: `ws://`.
+- `startupTime`：Start-up time in milliseconds.
+- `weight`：The default value for load balancing weight, which is automatically registered for service startup, is 50.
+- `warmupTime`：Warm-up time, in milliseconds, the server in warm-up will calculate the instantaneous weight, the calculated value will be less than the actual weight configured to protect the server just started, the default value of service start registration is 10. For example, the warm-up time is 100 milliseconds, currently started 50 milliseconds, the configured weight is 50, the actual weight is 25.
+- `status`：open or close, the start state of this processor is only valid.
+
+#### 2.4.2.2 Configuration of rules
+
+The example of websocket rule configuration, please refer to [selectors and rules](../../user-guide/admin-usage/selector-and-rule.md) for general rule configuration .
+
+
+
+##### 2.4.2.2.1 Rule handler configuration
+
+- `loadStrategy`: if the websocket client is a cluster, which load balancing strategy to take when the Apache ShenYu gateway is invoked, currently supports roundRobin, random and hash.
+- `timeout`: The timeout period for calling the client.
+- `retryCount`: The number of retries to call client timeout failures.
+
+## 2.5 示例
+
+### 2.5.1 Spring Annotation Websocket Example
+
+[shenyu-example-spring-annotation-websocket](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-websocket/shenyu-example-spring-annotation-websocket)
+
+### 2.5.2 Spring Native Websocket Example
+
+[shenyu-example-spring-native-websocket](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-websocket/shenyu-example-spring-native-websocket)
+
+### 2.5.3 Spring Reactive Websocket Example
+
+[shenyu-example-spring-reactive-websocket](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-websocket/shenyu-example-spring-reactive-websocket)
+
+# 3. How to disable plugin
+
+- shenyu-admin --> BasicConfig --> Plugin --> Close websocket plugin status.
+
+
+
+# 4. Frequently Asked Questions
+
+**4.1 Websocket connection establishment error 1002**
+
+Possible causes: client service is not normal, shenyu gateway and client project can not establish a normal connection, please check the gateway to the client network, client service is normal.
+
+**4.2 Multiple client services are displayed as empty in the websocket selector**
+
+Possible cause: BasicConfig -> Plugin -> websocket -> multiSelectorHandle option select multiple handle.
+
+
+
+# 5. Annexes
+
+## 5.1 websocket debugging code
+
+- Create a file called websocket.html and copy the following code into the file.
+- Open websocket.html with Chrome.
+
+```html
+
+
+
+
+ Shenyu WebSocket Test
+
+
+
+
+
+
+
+
+
+
+
+
+```
diff --git a/versioned_docs/version-2.6.1/plugin-center/security/_category_.json b/versioned_docs/version-2.6.1/plugin-center/security/_category_.json
new file mode 100644
index 00000000000..45fba4709cc
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/security/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Security",
+ "position": 4
+}
diff --git a/versioned_docs/version-2.6.1/plugin-center/security/casdoor.md b/versioned_docs/version-2.6.1/plugin-center/security/casdoor.md
new file mode 100644
index 00000000000..3fecb12048d
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/security/casdoor.md
@@ -0,0 +1,70 @@
+---
+title: Casdoor Plugin
+keywords: [Casdoor]
+description: Casdoor plugin
+---
+
+ShenYu has Casdoor plugin to use Casdoor
+
+## Step1. Deploy Casdoor
+
+Firstly, the Casdoor should be deployed.
+
+You can refer to the Casdoor official documentation
+
+After a successful deployment, you need to ensure:
+
+- The Casdoor server is successfully running on **http://localhost:8000**.
+- Open your favorite browser and visit **http://localhost:7001**, you will see the login page of Casdoor.
+- Input `admin` and `123` to test login functionality is working fine.
+
+Then you can quickly implement a Casdoor based login page in your own app with the following steps.
+
+## Step2. Configure Casdoor application
+
+### 1. Create or use an existing Casdoor application
+
+### 2. Add Your redirect url
+
+ 
+
+### 3. On the certificate editing page, you can see your `certificate`
+
+ 
+
+## Step3. Use Casdoor plugin in Shenyu
+
+### 1. Config Casdoor plugin in Shenyu
+
+ 
+
+note: because the shenyu only have Single line input box so we need add \n in every line of cert.
+
+ 
+
+You can copy it and paste it on the certificate of shenyu casdoor config.
+
+**You don't need save it in Casdoor certificate editing page**,because it just for copying.
+
+### 2. Confing Shenyu Casdoor's plugin
+
+ 
+
+ You can config what you need to use Casdoor config
+
+### 3. Get the service and use
+
+#### 3.1 Visit the Web directly like
+
+ 
+
+#### 3.2 Use Casdoor login like this
+
+ 
+ 
+
+#### 3.3 Carry token in Headers,you also can visit it
+
+ 
+
+#### 3.4 It also can save name,id and organization in Headers so that you can use them in next time
diff --git a/versioned_docs/version-2.6.1/plugin-center/security/cryptor-request-plugin.md b/versioned_docs/version-2.6.1/plugin-center/security/cryptor-request-plugin.md
new file mode 100644
index 00000000000..5cbd4acbabf
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/security/cryptor-request-plugin.md
@@ -0,0 +1,62 @@
+---
+title: CryptorRequest plugin
+keywords: ["CryptorRequest"]
+description: CryptorRequest plugin
+---
+
+## Description
+
+* The `cryptorRequest` plugin uses `fieldNames` to match the parameters in `requestBody` for `decryption` processing, replacing the current `requestBody` content.
+
+## Plugin Setting
+
+1. In `shenyu-admin` BasicConfig --> plugin -> `cryptor_request` set to enable.
+
+
+
+2. Open `selector` to configure the traffic that needs to be matched.
+
+3. Open the `Rules` configuration corresponding to the `selector`.
+
+
+
+* strategyName: Algorithm name. Currently, based on shenyu's SPI mechanism, the encryption and decryption algorithms can be customized,
+ Need to implement the `org.apache.shenyu.plugin.cryptor.strategy.CryptorStrategy` interface.
+
+ At the same time find the `org.apache.shenyu.plugin.cryptor.strategy.CryptorStrategy` file under `resources/META-INF/shenyu/`,
+ Write the name of the algorithm, and the package name of the class that implements the `CryptorStrategy` interface.
+
+* fieldNames: Matching parameter name. Support parsing multi-level json format matching, using `.` segmentation, such as data.id.
+
+```json5
+ {
+ data: {
+ "id": ""
+ }
+ }
+```
+
+* decryptKey: Secret key. Used to decrypt data.
+
+* encryptKey: Secret key. Used to encrypt data.
+
+* way: Select encrypt or decrypt.
+
+## Plugin Use
+
+* Add support for `cryptorRequest` in the `pom.xml` file of shenyu-bootstrap.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-cryptor
+ ${project.version}
+
+
+```
+
+## Situation
+
+Prevent Internet hacking and obtain data maliciously. Improve data security.
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/security/cryptor-response-plugin.md b/versioned_docs/version-2.6.1/plugin-center/security/cryptor-response-plugin.md
new file mode 100644
index 00000000000..185ded13879
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/security/cryptor-response-plugin.md
@@ -0,0 +1,65 @@
+---
+title: CryptorResponse plugin
+keywords: ["CryptorResponse"]
+description: CryptorResponse plugin
+---
+
+## Description
+
+* The `CryptorResponse` plug-in uses `fieldNames` to match the parameters in `responseBody` for `encryption` processing, replacing the corresponding content of the current `fieldNames`.
+
+## Plugin Setting
+
+1. In `shenyu-admin` BasicConfig --> plugin -> `cryptor_response` set to enable.
+
+
+
+2. Open `selector` to configure the traffic that needs to be matched.
+
+3. Open the `Rules` configuration corresponding to the `selector`.
+
+
+
+* strategyName: Algorithm name. Currently, based on shenyu's SPI mechanism, the encryption and decryption algorithms can be customized,
+ Need to implement the `org.apache.shenyu.plugin.cryptor.strategy.CryptorStrategy` interface.
+
+ At the same time find the `org.apache.shenyu.plugin.cryptor.strategy.CryptorStrategy` file under `resources/META-INF/shenyu/`,
+ Write the name of the algorithm, and the package name of the class that implements the `CryptorStrategy` interface.
+
+
+* fieldNames: Matching parameter name. Support parsing multi-level json format matching, using `.` segmentation, such as data.id.
+
+```json5
+ {
+ data: {
+ "id": ""
+ }
+ }
+```
+
+* decryptKey: Secret key. Used to decrypt data.
+
+* encryptKey: Secret key. Used to encrypt data.
+
+* way: Select encrypt or decrypt.
+
+## Plugin Use
+
+* Add support for `cryptorResponse` in the `pom.xml` file of shenyu-bootstrap.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-cryptor
+ ${project.version}
+
+
+```
+
+## Situation
+
+Prevent Internet hacking and obtain data maliciously. Improve data security.
+
+
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/security/jwt-plugin.md b/versioned_docs/version-2.6.1/plugin-center/security/jwt-plugin.md
new file mode 100644
index 00000000000..c58d2fa446d
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/security/jwt-plugin.md
@@ -0,0 +1,156 @@
+---
+title: JWT plugin
+keywords: ["JWT"]
+description: JWT plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* `jwt` plugin
+
+## 1.2 Appropriate Scenario
+
+* Requires unified authentication by jwt at the gateway.
+
+
+## 1.3 Plugin functionality
+
+* The `jwt` plug-in is for the `token` attribute or `authorization` of the http request header to carry the attribute value for authentication judgment and judge `OAuth2.0` .
+
+## 1.4 Plugin code
+
+* Core module is `shenyu-plugin-jwt`.
+* Core class is `org.apache.shenyu.plugin.jwt.JwtPlugin`.
+
+## 1.5 Added Since Which shenyu version
+
+* Since ShenYu 2.4.0
+
+# 2.How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-jwt
+ ${project.version}
+
+```
+
+## 2.3 Enable plugin
+
+- In shenyu-admin --> BasicConfig --> Plugin --> jwt set Status enable.
+
+## 2.4 Config plugin
+
+### 2.4.1 Config plugin in ShenYu-Admin
+
+* Config secretKey of jwt-plugin in shenyu-admin, the secretKey must more than 256 bit.
+* `secretKey`: The private key when using `jwt` to generate `token`, it is required.
+
+
+
+### 2.4.2 Selector config
+
+* Selector and rule Config. Please refer: [Selector and rule config](../../user-guide/admin-usage/selector-and-rule.md).
+
+### 2.4.3 Rule Config
+
+
+
+* convert means jwt converter
+* jwtVal: jwt of body name
+* headerVal: jwt header name
+
+custom covert algorithm：[custom-jwt-covert-algorithm](../../developer/custom-jwt-covert-algorithm.md)
+
+## 2.5 Examples
+
+### 2.5.1 Use jwt token for authentication judgment
+
+#### 2.5.1.1 Config jwt-plugin
+
+
+
+#### 2.5.1.2 Config selector match service
+
+
+
+#### 2.5.1.3 Config rule match service
+
+
+
+#### 2.5.1.4 Generate json web token(jwt) with website
+
+* You can open `https://jwt.io/` in your browser and fill in the corresponding parameters.
+* Config jwt header `HEADER` in `https://jwt.io/`
+* Config jwt body `PAYLOAD` in `https://jwt.io/`
+* Config jwt signature `VERIFY SIGNATURE` in `https://jwt.io/`
+
+
+
+#### 2.5.1.5 Generate json web token(jwt) with java code
+
+```java
+public final class JwtPluginTest {
+
+ public void generateJwtCode() {
+ final String secreteKey = "shenyu-test-shenyu-test-shenyu-test";
+ Map map = new HashMap<>();
+ map.put("id", "1");
+ map.put("name", "xiaoming");
+ Date date = new Date();
+ date.setTime(1655524800000L);
+ String token = Jwts.builder()
+ .setIssuedAt(date)
+ .setExpiration(new Date())
+ .setClaims(map)
+ .signWith(Keys.hmacShaKeyFor(secreteKey.getBytes(StandardCharsets.UTF_8)), SignatureAlgorithm.HS256)
+ .compact();
+ System.out.println(token);
+ }
+}
+```
+
+#### 2.5.1.6 Request Service
+
+##### 2.5.1.6.1 Request service with token
+
+* request your service with jwt token `token: eyJhbGciOiJIUzI1NiJ9.eyJuYW1lIjoieGlhb21pbmciLCJpZCI6IjEifQ.LdRzGlB49alhq204chwF7pf3C0z8ZpuowPvoQdJmSRw` in your request header.
+
+##### 2.5.1.6.2 Request service Authorization
+
+* request your service with Authorization `Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJuYW1lIjoieGlhb21pbmciLCJpZCI6IjEifQ.LdRzGlB49alhq204chwF7pf3C0z8ZpuowPvoQdJmSRw` in your request header.
+
+#### 2.5.1.7 Validate request result
+
+* error token request result
+
+```
+{
+ "code": 401,
+ "message": "Illegal authorization"
+}
+```
+
+* normal token request result
+
+```
+{
+ "id": "123",
+ "name": "hello world save order"
+}
+```
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `jwt` set Status disable.
+
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/security/oauth2-plugin.md b/versioned_docs/version-2.6.1/plugin-center/security/oauth2-plugin.md
new file mode 100644
index 00000000000..39525e12760
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/security/oauth2-plugin.md
@@ -0,0 +1,54 @@
+---
+title: OAuth2 Plugin
+keywords: ["OAuth2"]
+description: OAuth2 plugin
+---
+
+## Description
+
+The `OAuth2` plugin in Apache Shenyu is implemented using the OAuth2 standard. It allows for secure and authorized access to protected resources on a web server by using a token-based authentication method.
+
+## How Does It Works?
+
+In Apache Shenyu, the OAuth2 plugin acts as the client application, while the authorization server and resource server are typically provided by external services like GitHub, Google, or Facebook. When a user attempts to access a protected resource on the Apache Shenyu server, the OAuth2 plugin redirects the user to the authorization server to request permission to access the resource. The user then logs in to the authorization server and grants permission for the client application (OAuth2 plugin) to access the requested resource on their behalf. The authorization server then sends a token to the client application, which it can use to access the resource server and retrieve the protected resource.
+
+## Plugin Setting
+
+Setting up the OAuth2 Plugin in Apache Shenyu
+
+To configure the OAuth2 plugin in Apache Shenyu, you will need to follow these steps:
+
+* Step 1: Install the OAuth2 Plugin
+
+ First, you need to ensure that the OAuth2 plugin is installed and enabled in Apache Shenyu. If it is not already installed, you can download it from the Shenyu GitHub repository and follow the installation instructions.
+
+* Step 2: Register an OAuth2 Application with the Authorization Server
+
+ Before you can use the OAuth2 plugin in Apache Shenyu, you need to register an OAuth2 application with the authorization server you plan to use (e.g., GitHub, Google, etc.). The registration process typically involves providing basic information about your application, such as the application name, website URL, and redirect URI.
+
+ Once you have registered your OAuth2 application with the authorization server, you will receive a client ID and client secret, which you will need to use in the next step.
+
+* Step 3: Configure the OAuth2 Plugin
+
+ To configure the OAuth2 plugin in Apache Shenyu, you will need to modify the shenyu-server.yaml configuration file. Here's an example of what the configuration might look like:
+
+ ```
+ plugins:
+ oauth2:
+ enabled: true
+ client_id:
+ client_secret:
+ authorization_url:
+ token_url:
+ user_info_url:
+ ```
+
+ * `enabled`: Set this to `true` to enable the OAuth2 plugin in Shenyu.
+ * `client_id` and `client_secret`: These are the client credentials you received when you registered your OAuth2 application with the authorization server.
+ * `authorization_url`: This is the URL of the authorization server's authorization endpoint.
+ * `token_url`: This is the URL of the authorization server's token endpoint.
+ * `user_info_url`: This is the URL of the authorization server's user info endpoint, which is used to retrieve information about the authenticated user.
+
+* Step 4: Test the OAuth2 Plugin
+
+ To test the OAuth2 plugin in Apache Shenyu, you can try to access a protected resource on the Shenyu server that requires authentication. When you attempt to access the resource, the OAuth2 plugin should redirect you to the authorization server's login page. After you log in and grant permission to the client application (OAuth2 plugin), the plugin should be able to retrieve an access token and use it to access the protected resource on your behalf.
diff --git a/versioned_docs/version-2.6.1/plugin-center/security/sign-plugin.md b/versioned_docs/version-2.6.1/plugin-center/security/sign-plugin.md
new file mode 100644
index 00000000000..ed940f4960b
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/security/sign-plugin.md
@@ -0,0 +1,501 @@
+---
+title: Sign Plugin
+keywords: ["sign"]
+description: sign plugin
+---
+
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Sign Plugin
+
+## 1.2 Appropriate Scenario
+
+* Support http header to authorize
+* Support http header and request body to authorize
+
+## 1.3 Plugin functionality
+
+* Process signature authentication of requests.
+
+## 1.4 Plugin code
+
+* Core Module: `shenyu-plugin-sign`
+
+* Core Class: `org.apache.shenyu.plugin.sign.SignPlugin`
+
+## 1.5 Added Since Which shenyu version
+
+* Since ShenYu 2.4.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+* Introducing `sign` dependency in the `pom.xml` file of the gateway
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-sign
+ ${project.version}
+
+
+```
+
+## 2.3 Enable plugin
+
+* In `shenyu-admin`--> BasicConfig --> Plugin --> `sign` set to enable.
+
+## 2.4 Config Plugin With Authorize（1.0.0）
+
+### 2.4.1 AK/SK Config
+
+#### 2.4.1.1 Explanation
+
+- Manage and control the permissions of requests passing through the Apache ShenYu gateway.
+- Generate `AK/SK` and use it with the `Sign` plugin to achieve precise authority control based on URI level.
+
+#### 2.4.1.2 Tutorial
+
+First, we can add a piece of authentication information in `BasicConfig` - `Authentication`
+
+
+
+Then configure this authentication information
+
+
+
+- AppName：The application name associated with this account, it can can fill in or choose (data comes from the application name configured in the Metadata).
+- TelPhone：Telphone information.
+- AppParams：When the requested context path is the same as the AppName，add this value to the header, the key is `appParam`.
+- UserId：Give the user a name, just as an information record.
+- ExpandInfo：Description of the account.
+- PathAuth：After opening, the account only allows access to the resource path configured below.
+- ResourcePath：Allow access to the resource path, support path matching，e.g. `/order/**` .
+
+After submit, a piece of authentication information is generated, which contains `AppKey` and `AppSecret`, which is the `AK/SK` in the `Sign` plugin.
+
+Please refer to the detailed instructions of the `Sign` plugin： [Sign Plugin](../../plugin-center/authority-and-certification/sign-plugin).
+
+#### 2.4.1.3 PathOperation
+
+For the created authentication information, you can click `PathOperation` at the end of a piece of authentication information.
+
+
+
+- On the left is a list of configurable paths, and on the right is a list of paths that allow the account to access.
+- Check the resource path, click the `>` or `<` in the middle to move the checked data to the corresponding list.
+- In the list of configurable paths on the left, click "Editor" at the end of the account information line, and add them in the "Resource Path" in the pop-up box.
+
+### 2.4.2 Implementation of Gateway Technology
+
+* Adopt `AK/SK` authentication technical scheme.
+* Adopt authentication plug-in and Chain of Responsibility Pattern to realize.
+* Take effect when the authentication plugin is enabled and all interfaces are configured for authentication.
+
+### 2.4.3 Authentication Guide
+
+* Step 1: `AK/SK` is assigned by the gateway. For example, the `AK` assigned to you is: `1TEST123456781` SK is: ` 506eeb535cf740d7a755cb49f4a1536'
+
+* Step 2: Decide the gateway path you want to access, such as `/api/service/abc`
+
+* Step 3: Construct parameters (the following are general parameters)
+
+| Field | Value | Description |
+| -------- | -------- | :--------: |
+| timestamp | current timestamp(String) | The number of milliseconds of the current time（gateway will filter requests the before 5 minutes） |
+| path | /api/service/abc | The path that you want to request(Modify by yourself according to your configuration of gateway) |
+| version | 1.0.0 | `1.0.0` is a fixed string value |
+
+Sort the above three field natually according to the key, then splice fields and fields, finally splice SK. The following is a code example.
+
+#### 2.4.3.1 Generate sign with request header
+
+Step 1: First, construct a Map.
+
+```java
+
+ Map map = Maps.newHashMapWithExpectedSize(3);
+ //timestamp is string format of millisecond. String.valueOf(LocalDateTime.now().toInstant(ZoneOffset.of("+8")).toEpochMilli())
+ map.put("timestamp","1571711067186"); // Value should be string format of milliseconds
+ map.put("path", "/api/service/abc");
+ map.put("version", "1.0.0");
+```
+
+Step 2: Sort the `Keys` naturally, then splice the key and values, and finally splice the `SK` assigned to you.
+
+```java
+List storedKeys = Arrays.stream(map.keySet()
+ .toArray(new String[]{}))
+ .sorted(Comparator.naturalOrder())
+ .collect(Collectors.toList());
+final String sign = storedKeys.stream()
+ .map(key -> String.join("", key, map.get(key)))
+ .collect(Collectors.joining()).trim()
+ .concat("506EEB535CF740D7A755CB4B9F4A1536");
+```
+
+* The returned sign value should be:`path/api/service/abctimestamp1571711067186version1.0.0506EEB535CF740D7A755CB4B9F4A1536`
+
+Step 3: Md5 encryption and then capitalization.
+
+```java
+DigestUtils.md5DigestAsHex(sign.getBytes()).toUpperCase()
+```
+
+* The final returned value is: `A021BF82BE342668B78CD9ADE593D683`.
+
+#### 2.4.3.2 Generate sign with request header and request body
+
+Step 1: First, construct a Map, and the map must save every request body parameters
+
+```java
+
+ Map map = Maps.newHashMapWithExpectedSize(3);
+ //timestamp is string format of millisecond. String.valueOf(LocalDateTime.now().toInstant(ZoneOffset.of("+8")).toEpochMilli())
+ map.put("timestamp","1660659201000"); // Value should be string format of milliseconds
+ map.put("path", "/http/order/save");
+ map.put("version", "1.0.0");
+ // if your request body is:{"id":123,"name":"order"}
+ map.put("id", "1");
+ map.put("name", "order")
+```
+
+Step 2: Sort the `Keys` naturally, then splice the key and values, and finally splice the `SK` assigned to you.
+
+```java
+List storedKeys = Arrays.stream(map.keySet()
+ .toArray(new String[]{}))
+ .sorted(Comparator.naturalOrder())
+ .collect(Collectors.toList());
+final String sign = storedKeys.stream()
+ .map(key -> String.join("", key, map.get(key)))
+ .collect(Collectors.joining()).trim()
+ .concat("2D47C325AE5B4A4C926C23FD4395C719");
+```
+
+* The returned sign value should be:`id123nameorderpath/http/order/savetimestamp1660659201000version1.0.02D47C325AE5B4A4C926C23FD4395C719`
+
+Step 3: Md5 encryption and then capitalization.
+
+```java
+DigestUtils.md5DigestAsHex(sign.getBytes()).toUpperCase()
+```
+
+* The final returned value is: `35FE61C21F73E9AAFC46954C14F299D7`.
+
+### 2.4.4 Request GateWay
+
+* If your visited path is:`/api/service/abc`.
+
+* Address: http: domain name of gateway `/api/service/abc`.
+
+* Set `header`，`header` Parameter：
+
+| Field | Value | Description |
+| -------- | -----: | :----: |
+| timestamp | `1571711067186` | Timestamp when signing |
+| appKey | `1TEST123456781` | The AK value assigned to you |
+| sign | `A90E66763793BDBC817CF3B52AAAC041` | The signature obtained above |
+| version | `1.0.0` | `1.0.0` is a fixed value. |
+
+* The signature plugin will filter requests before `5` minutes by default
+
+* If the authentication fails, will return code `401`, message may change.
+
+```json
+{
+ "code": 401,
+ "message": "sign is not pass,Please check you sign algorithm!",
+ "data": null
+}
+```
+
+### 2.4.5 Plugin Config
+
+
+
+### 2.4.6 Selector Config
+
+
+
+* Only those matched requests can be authenticated by signature.
+
+* Selectors and rules, please refer to: [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule)
+
+### 2.4.7 Rule Config
+
+
+
+* close(signRequestBody): generate signature with request header.
+* open(signRequestBody): generate signature with request header and request body.
+
+## 2.5 Config Plugin With Authorize（2.0.0）
+
+This authentication algorithm is the version 2.0.0 algorithm, which is same as version1's except **Authentication Guide** and **Request GateWay.**
+
+### 2.5.1 Authentication Guide
+
+Authentication algorithm of Version 2.0.0 generates a Token based on the signature algorithm, and puts the Token value into the request header `ShenYu-Authorization` parameter when sending a request. To distinguish it from version 1.0.0, the `version` parameter of the request header is left, which is 2.0.0.
+
+#### 2.5.1.1 prepare
+
+* Step 1: `AK/SK` is assigned by the gateway. For example, the `AK` assigned to you is: `1TEST123456781` SK is: ` 506eeb535cf740d7a755cb49f4a1536'
+
+* Step 2: Decide the gateway path you want to access, such as `/api/service/abc`
+
+#### 2.5.1.2 Generate Token
+
++ build parameter
+
+ build the `parameters` that is json string
+
+ ```json
+ {
+ "alg":"MD5",
+ "appKey":"506EEB535CF740D7A755CB4B9F4A1536",
+ "timestamp":"1571711067186"
+ }
+ ```
+
+ **alg**: signature algorithm（result is uppercase HEX string）
+
+ - MD5: MD5-HASH(data+key)
+ - HMD5:HMAC-MD5
+ - HS256:HMAC-SHA-256
+ - HS512:HMAC-SHA-512
+
+ **appKey**：appKey
+
+ **timestamp**: timestamp of the length is 13
+
++ Calculate signature value
+
+ ```tex
+ signature = sign(
+ base64Encoding(parameters) + Relative URL + Body*,
+ secret
+ );
+ * indicate Optional , it depends on handler config
+ Relative URL = path [ "?" query ] eg: /apache/shenyu/pulls?name=jack
+ ```
+
+ > note :`Relative URL` is not include fragment
+
++ Calculate Token
+
+ > token = base64Encoding(parameters) + '.' + base64Encoding(signature)
+
+ Put the Token into the request header `ShenYu-Authorization` parameter.
+
+### 2.5.2 Request GateWay
+
+| Field | 值 | 描述 |
+| :------------ | :------ |:------------------------------------------------------------|
+| ShenYu-Authorization | Token | Token |
+| version | `2.0.0` | Fixed value |
+
+>please change the Authorization field to ShenYu-Authorization as soon as possible to avoid conflicts with application Authorization.
+
+## 2.6 Examples
+
+### 2.6.1 Verify api with sign plugin（1.0.0）
+
+#### 2.6.1.1 Plugin Config
+
+
+
+#### 2.6.1.2 Selector Config
+
+
+
+#### 2.6.1.3 Rule Config
+
+
+
+#### 2.6.1.4 Add AppKey/SecretKey
+
+
+
+#### 2.6.1.5 Request Service and check result
+
+* build request params with `Authentication Guide`,
+
+```java
+public class Test1 {
+ public static void main(String[] args) {
+ Map map = Maps.newHashMapWithExpectedSize(3);
+ //timestamp为毫秒数的字符串形式 String.valueOf(LocalDateTime.now().toInstant(ZoneOffset.of("+8")).toEpochMilli())
+ map.put("timestamp","1660658725000"); //值应该为毫秒数的字符串形式
+ map.put("path", "/http/order/save");
+ map.put("version", "1.0.0");
+ map.put("id", "123");
+ map.put("name", "order");
+ // map.put("body", "{\"id\":123,\"name\":\"order\"}");
+
+ List storedKeys = Arrays.stream(map.keySet()
+ .toArray(new String[]{}))
+ .sorted(Comparator.naturalOrder())
+ .collect(Collectors.toList());
+ final String sign = storedKeys.stream()
+ .map(key -> String.join("", key, map.get(key)))
+ .collect(Collectors.joining()).trim()
+ .concat("2D47C325AE5B4A4C926C23FD4395C719");
+ System.out.println(sign);
+
+ System.out.println(DigestUtils.md5DigestAsHex(sign.getBytes()).toUpperCase());
+ }
+}
+```
+
+* signature without body: `path/http/order/savetimestamp1571711067186version1.0.02D47C325AE5B4A4C926C23FD4395C719`
+* sign without body result is: `9696D3E549A6AEBE763CCC2C7952DDC1`
+
+
+
+```java
+public class Test2 {
+ public static void main(String[] args) {
+ Map map = Maps.newHashMapWithExpectedSize(3);
+ //timestamp为毫秒数的字符串形式 String.valueOf(LocalDateTime.now().toInstant(ZoneOffset.of("+8")).toEpochMilli())
+ map.put("timestamp","1660659201000"); //值应该为毫秒数的字符串形式
+ map.put("path", "/http/order/save");
+ map.put("version", "1.0.0");
+
+ List storedKeys = Arrays.stream(map.keySet()
+ .toArray(new String[]{}))
+ .sorted(Comparator.naturalOrder())
+ .collect(Collectors.toList());
+ final String sign = storedKeys.stream()
+ .map(key -> String.join("", key, map.get(key)))
+ .collect(Collectors.joining()).trim()
+ .concat("2D47C325AE5B4A4C926C23FD4395C719");
+ System.out.println(sign);
+
+ System.out.println(DigestUtils.md5DigestAsHex(sign.getBytes()).toUpperCase());
+ }
+}
+```
+
+*signature with body:`id123nameorderpath/http/order/savetimestamp1660659201000version1.0.02D47C325AE5B4A4C926C23FD4395C719`
+*sign with body result is:`35FE61C21F73E9AAFC46954C14F299D7`
+
+
+
+### 2.6.2 Verify api with sign plugin（2.0.0）
+
+All the configuration parts are the same, so let's look directly at the the calculation part of parameter of request header and the part of sending request.
+
+#### 2.6.2.1 Request Service and check result
+
+- implements the algorithm
+
+ Suppose we use a signature algorithm named MD5. According to the previous description, the signature value is to concatenate the data and key, and then hash.
+
+ ```java
+ private static String sign(final String signKey, final String base64Parameters, final URI uri, final String body) {
+
+ String data = base64Parameters
+ + getRelativeURL(uri)
+ + Optional.ofNullable(body).orElse("");
+
+ return DigestUtils.md5Hex(data+signKey).toUpperCase();
+ }
+
+ private static String getRelativeURL(final URI uri) {
+ if (Objects.isNull(uri.getQuery())) {
+ return uri.getPath();
+ }
+ return uri.getPath() + "?" + uri.getQuery();
+ }
+ ```
+
+- verify without the request body
+
+ ```java
+ public static void main(String[] args) {
+
+ String appSecret = "2D47C325AE5B4A4C926C23FD4395C719";
+
+ URI uri = URI.create("/http/order/save");
+
+ String parameters = JsonUtils.toJson(ImmutableMap.of(
+ "alg","MD5",
+ "appKey","BD7980F5688A4DE6BCF1B5327FE07F5C",
+ "timestamp","1673708353996"));
+
+ String base64Parameters = Base64.getEncoder()
+ .encodeToString(parameters.getBytes(StandardCharsets.UTF_8));
+
+ String signature = sign(appSecret,base64Parameters,uri,null);
+
+ String Token = base64Parameters+"."+signature;
+
+ System.out.println(Token);
+
+ }
+ ```
+
+ Token:
+
+ ```tex
+ eyJhbGciOiJNRDUiLCJhcHBLZXkiOiJCRDc5ODBGNTY4OEE0REU2QkNGMUI1MzI3RkUwN0Y1QyIsInRpbWVzdGFtcCI6IjE2NzM3MDgzNTM5OTYifQ==.33ED53DF79CA5B53C0BF2448B670AF35
+ ```
+
+ 发送请求：
+
+ 
+
+- verify with the request body
+
+```java
+ public static void main(String[] args) {
+ String appSecret = "2D47C325AE5B4A4C926C23FD4395C719";
+
+ URI uri = URI.create("/http/order/save");
+
+ String parameters = JsonUtils.toJson(ImmutableMap.of(
+ "alg","MD5",
+ "appKey","BD7980F5688A4DE6BCF1B5327FE07F5C",
+ "timestamp","1673708905488"));
+
+ String base64Parameters = Base64.getEncoder()
+ .encodeToString(parameters.getBytes(StandardCharsets.UTF_8));
+
+ String requestBody = "{\"id\":123,\"name\":\"order\"}";
+
+ String signature = sign(appSecret,base64Parameters,uri,requestBody);
+
+ String Token = base64Parameters+"."+signature;
+
+ System.out.println(Token);
+
+ }
+```
+
+Token:
+
+```tex
+eyJhbGciOiJNRDUiLCJhcHBLZXkiOiJCRDc5ODBGNTY4OEE0REU2QkNGMUI1MzI3RkUwN0Y1QyIsInRpbWVzdGFtcCI6IjE2NzM3MDg5MDU0ODgifQ==.FBCEB6D816644A98378635050AB85EF1
+```
+
+
+
+
+
+# 3. How to disable plugin
+
+* In `shenyu-admin`--> BasicConfig --> Plugin --> `sign` set to disabled.
+
+# 4. Extension
+
+* Please refer to: [dev-sign](../../developer/custom-sign-algorithm).
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/security/waf-plugin.md b/versioned_docs/version-2.6.1/plugin-center/security/waf-plugin.md
new file mode 100644
index 00000000000..802dd9865b8
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/security/waf-plugin.md
@@ -0,0 +1,76 @@
+---
+title: Waf Plugin
+keywords: ["waf"]
+description: waf plugin
+---
+
+## Description
+
+* `Waf` is the core implementation of gateway to realize firewall function for network traffic.
+
+## Plugin Setting
+
+Please refer to the `deployment` document, choose a way to start `shenyu-admin`. For example, through [Local Deployment](../../deployment/deployment-local) to start the `Apache ShenYu` management system.
+
+* In `shenyu-admin` BasicConfig --> plugin -> `waf` set to enable.If you don't want to use this function, please disable this plugin in the `shenyu-admin`.
+
+
+
+* Add configuration mode in plugin editing.
+
+```yaml
+{"model":"black"}
+# model can be 'black' or 'mixed'
+# The default mode is blacklist mode; If setting is mixed, it will be mixed mode. We will explain it specifically below.
+```
+
+## Add Dependency
+
+* Introducing `waf` dependency in the pom.xml of the gateway.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-waf
+ ${project.version}
+
+
+```
+
+## Waf Plugin Configuration
+
+For more instructions on selector and rule configuration, please refer to: [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule), here only some fields are introduced.
+
+`Waf` plugin rule configuration page:
+
+
+
+For requests that are denied access by `Waf` , the response header status code is: `403`.
+
+#### Black Model
+
+* When `model` is set to `black` mode, only the matched traffic will execute the rejection policy, and the unmatched traffic will be skipped directly.
+* The `Handler` feild in the rule configuration is invalid and can be configured to be empty.
+
+#### Mixed Model
+
+* When `model` is set to `mixed` mode, all traffic will pass through waf plugin. For different matching traffic, users can set whether to reject or pass.
+
+* The `Handler` feild in the rule configuration must be configured:
+
+ * `permission`: The handle logic that matches the rule. `reject`: deny access, `allow`: allow access.
+
+ * `statusCode`: When access is denied, the value of the code field in the response body. `Will not modify the status code of the response header`.
+
+ e.g.：`statusCode=10001`，The rejected response body is :
+
+ ```json
+ {"code":10001,"message":"You are forbidden to visit"}
+ ```
+
+## Situation
+
+* `Waf` is also the pre-plugin of `ShenYu`, which is mainly used to intercept illegal requests or exception requests and give relevant rejection policies.
+* When faced with replay attacks, you can intercept illegal `ip` and `host`, and set reject strategy according to matched `ip` or `host`.
+* How to determine `ip` and `host`, please refer to: [parsing-ip-and-host](../../developer/custom-parsing-ip-and-host)
diff --git a/versioned_docs/version-2.6.1/quick-start/_category_.json b/versioned_docs/version-2.6.1/quick-start/_category_.json
new file mode 100644
index 00000000000..6b00aae3947
--- /dev/null
+++ b/versioned_docs/version-2.6.1/quick-start/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Quick Start",
+ "position": 4
+}
diff --git a/versioned_docs/version-2.6.1/quick-start/quick-start-dubbo.md b/versioned_docs/version-2.6.1/quick-start/quick-start-dubbo.md
new file mode 100644
index 00000000000..8fd022ffbd2
--- /dev/null
+++ b/versioned_docs/version-2.6.1/quick-start/quick-start-dubbo.md
@@ -0,0 +1,180 @@
+---
+title: Quick start with Dubbo
+description: Quick start with Dubbo
+---
+
+This document introduces how to quickly access the Apache ShenYu gateway using Dubbo. You can get the code example of this document by clicking [here](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-dubbo).
+
+## Environment to prepare
+
+Please refer to the deployment to select a way to start shenyu-admin. For example, start the Apache ShenYu gateway management system through [local deployment](../deployment/deployment-local) .
+
+After successful startup, you need to open the Dubbo plugin on in the BasicConfig `->` Plugin, and set your registry address. Please make sure the registry center is open locally.
+
+
+
+If you are a startup gateway by means of source, can be directly run the ShenyuBootstrapApplication of shenyu-bootstrap module.
+
+> Note: Before starting, make sure the gateway has added dependencies.
+
+
+If client is `apache dubbo`, registry center is `Zookeeper`, please refer to the following configuration:
+
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-apache-dubbo
+ ${project.version}
+
+
+ org.apache.dubbo
+ dubbo
+ 2.7.5
+
+
+
+ org.apache.curator
+ curator-client
+ 4.0.1
+
+
+ log4j
+ log4j
+
+
+
+
+ org.apache.curator
+ curator-framework
+ 4.0.1
+
+
+ org.apache.curator
+ curator-recipes
+ 4.0.1
+
+
+
+```
+
+If client is `alibaba dubbo`, registry center is `Zookeeper`, please refer to the following configuration:
+
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-alibaba-dubbo
+ ${project.version}
+
+
+ com.alibaba
+ dubbo
+ ${alibaba.dubbo.version}
+
+
+ org.apache.curator
+ curator-client
+ ${curator.version}
+
+
+ log4j
+ log4j
+
+
+
+
+ org.apache.curator
+ curator-framework
+ ${curator.version}
+
+
+ org.apache.curator
+ curator-recipes
+ ${curator.version}
+
+
+```
+
+
+## Run the shenyu-examples-dubbo project
+
+Download [shenyu-examples-dubbo](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-dubbo) .
+
+replace the register address in `shenyu-examples-alibaba-dubbo-service/src/main/resources/spring-dubbo.xml` with your local zk address, such as:
+
+```xml
+
+```
+
+Execute the `org.apache.shenyu.examples.alibaba.dubbo.service.TestAlibabaDubboApplication` main method to start dubbo project.
+
+The following log appears when the startup is successful:
+
+```shell
+2021-02-06 20:58:01.807 INFO 3724 --- [pool-2-thread-1] o.d.s.client.common.utils.RegisterUtils : dubbo client register success: {"appName":"dubbo","contextPath":"/dubbo","path":"/dubbo/insert","pathDesc":"Insert a row of data","rpcType":"dubbo","serviceName":"org.dromara.shenyu.examples.dubbo.api.service.DubboTestService","methodName":"insert","ruleName":"/dubbo/insert","parameterTypes":"org.dromara.shenyu.examples.dubbo.api.entity.DubboTest","rpcExt":"{\"group\":\"\",\"version\":\"\",\"loadbalance\":\"random\",\"retries\":2,\"timeout\":10000,\"url\":\"\"}","enabled":true}
+2021-02-06 20:58:01.821 INFO 3724 --- [pool-2-thread-1] o.d.s.client.common.utils.RegisterUtils : dubbo client register success: {"appName":"dubbo","contextPath":"/dubbo","path":"/dubbo/findAll","pathDesc":"Get all data","rpcType":"dubbo","serviceName":"org.dromara.shenyu.examples.dubbo.api.service.DubboTestService","methodName":"findAll","ruleName":"/dubbo/findAll","parameterTypes":"","rpcExt":"{\"group\":\"\",\"version\":\"\",\"loadbalance\":\"random\",\"retries\":2,\"timeout\":10000,\"url\":\"\"}","enabled":true}
+2021-02-06 20:58:01.833 INFO 3724 --- [pool-2-thread-1] o.d.s.client.common.utils.RegisterUtils : dubbo client register success: {"appName":"dubbo","contextPath":"/dubbo","path":"/dubbo/findById","pathDesc":"Query by Id","rpcType":"dubbo","serviceName":"org.dromara.shenyu.examples.dubbo.api.service.DubboTestService","methodName":"findById","ruleName":"/dubbo/findById","parameterTypes":"java.lang.String","rpcExt":"{\"group\":\"\",\"version\":\"\",\"loadbalance\":\"random\",\"retries\":2,\"timeout\":10000,\"url\":\"\"}","enabled":true}
+2021-02-06 20:58:01.844 INFO 3724 --- [pool-2-thread-1] o.d.s.client.common.utils.RegisterUtils : dubbo client register success: {"appName":"dubbo","contextPath":"/dubbo","path":"/dubbo/findByListId","pathDesc":"","rpcType":"dubbo","serviceName":"org.dromara.shenyu.examples.dubbo.api.service.DubboMultiParamService","methodName":"findByListId","ruleName":"/dubbo/findByListId","parameterTypes":"java.util.List","rpcExt":"{\"group\":\"\",\"version\":\"\",\"loadbalance\":\"random\",\"retries\":2,\"timeout\":10000,\"url\":\"\"}","enabled":true}
+2021-02-06 20:58:01.855 INFO 3724 --- [pool-2-thread-1] o.d.s.client.common.utils.RegisterUtils : dubbo client register success: {"appName":"dubbo","contextPath":"/dubbo","path":"/dubbo/findByIdsAndName","pathDesc":"","rpcType":"dubbo","serviceName":"org.dromara.shenyu.examples.dubbo.api.service.DubboMultiParamService","methodName":"findByIdsAndName","ruleName":"/dubbo/findByIdsAndName","parameterTypes":"java.util.List,java.lang.String","rpcExt":"{\"group\":\"\",\"version\":\"\",\"loadbalance\":\"random\",\"retries\":2,\"timeout\":10000,\"url\":\"\"}","enabled":true}
+2021-02-06 20:58:01.866 INFO 3724 --- [pool-2-thread-1] o.d.s.client.common.utils.RegisterUtils : dubbo client register success: {"appName":"dubbo","contextPath":"/dubbo","path":"/dubbo/batchSave","pathDesc":"","rpcType":"dubbo","serviceName":"org.dromara.shenyu.examples.dubbo.api.service.DubboMultiParamService","methodName":"batchSave","ruleName":"/dubbo/batchSave","parameterTypes":"java.util.List","rpcExt":"{\"group\":\"\",\"version\":\"\",\"loadbalance\":\"random\",\"retries\":2,\"timeout\":10000,\"url\":\"\"}","enabled":true}
+2021-02-06 20:58:01.876 INFO 3724 --- [pool-2-thread-1] o.d.s.client.common.utils.RegisterUtils : dubbo client register success: {"appName":"dubbo","contextPath":"/dubbo","path":"/dubbo/findByArrayIdsAndName","pathDesc":"","rpcType":"dubbo","serviceName":"org.dromara.shenyu.examples.dubbo.api.service.DubboMultiParamService","methodName":"findByArrayIdsAndName","ruleName":"/dubbo/findByArrayIdsAndName","parameterTypes":"[Ljava.lang.Integer;,java.lang.String","rpcExt":"{\"group\":\"\",\"version\":\"\",\"loadbalance\":\"random\",\"retries\":2,\"timeout\":10000,\"url\":\"\"}","enabled":true}
+2021-02-06 20:58:01.889 INFO 3724 --- [pool-2-thread-1] o.d.s.client.common.utils.RegisterUtils : dubbo client register success: {"appName":"dubbo","contextPath":"/dubbo","path":"/dubbo/saveComplexBeanTestAndName","pathDesc":"","rpcType":"dubbo","serviceName":"org.dromara.shenyu.examples.dubbo.api.service.DubboMultiParamService","methodName":"saveComplexBeanTestAndName","ruleName":"/dubbo/saveComplexBeanTestAndName","parameterTypes":"org.dromara.shenyu.examples.dubbo.api.entity.ComplexBeanTest,java.lang.String","rpcExt":"{\"group\":\"\",\"version\":\"\",\"loadbalance\":\"random\",\"retries\":2,\"timeout\":10000,\"url\":\"\"}","enabled":true}
+2021-02-06 20:58:01.901 INFO 3724 --- [pool-2-thread-1] o.d.s.client.common.utils.RegisterUtils : dubbo client register success: {"appName":"dubbo","contextPath":"/dubbo","path":"/dubbo/batchSaveAndNameAndId","pathDesc":"","rpcType":"dubbo","serviceName":"org.dromara.shenyu.examples.dubbo.api.service.DubboMultiParamService","methodName":"batchSaveAndNameAndId","ruleName":"/dubbo/batchSaveAndNameAndId","parameterTypes":"java.util.List,java.lang.String,java.lang.String","rpcExt":"{\"group\":\"\",\"version\":\"\",\"loadbalance\":\"random\",\"retries\":2,\"timeout\":10000,\"url\":\"\"}","enabled":true}
+2021-02-06 20:58:01.911 INFO 3724 --- [pool-2-thread-1] o.d.s.client.common.utils.RegisterUtils : dubbo client register success: {"appName":"dubbo","contextPath":"/dubbo","path":"/dubbo/saveComplexBeanTest","pathDesc":"","rpcType":"dubbo","serviceName":"org.dromara.shenyu.examples.dubbo.api.service.DubboMultiParamService","methodName":"saveComplexBeanTest","ruleName":"/dubbo/saveComplexBeanTest","parameterTypes":"org.dromara.shenyu.examples.dubbo.api.entity.ComplexBeanTest","rpcExt":"{\"group\":\"\",\"version\":\"\",\"loadbalance\":\"random\",\"retries\":2,\"timeout\":10000,\"url\":\"\"}","enabled":true}
+2021-02-06 20:58:01.922 INFO 3724 --- [pool-2-thread-1] o.d.s.client.common.utils.RegisterUtils : dubbo client register success: {"appName":"dubbo","contextPath":"/dubbo","path":"/dubbo/findByStringArray","pathDesc":"","rpcType":"dubbo","serviceName":"org.dromara.shenyu.examples.dubbo.api.service.DubboMultiParamService","methodName":"findByStringArray","ruleName":"/dubbo/findByStringArray","parameterTypes":"[Ljava.lang.String;","rpcExt":"{\"group\":\"\",\"version\":\"\",\"loadbalance\":\"random\",\"retries\":2,\"timeout\":10000,\"url\":\"\"}","enabled":true}
+```
+
+Note: When you need to expose `multiple protocols` at the same time, please do not configure `shenyu.client.dubbo.props.port`.
+
+## Test
+
+The `shenyu-examples-dubbo` project will automatically register interface methods annotated with `@ShenyuDubboClient` in the Apache ShenYu gateway after successful startup.
+
+Open PluginList -> rpc proxy -> dubbo to see the list of plugin rule configurations:
+
+
+
+Use `PostMan` to simulate `HTTP` to request your `Dubbo` service:
+
+
+
+Complex multi-parameter example: The related interface implementation class is `org.apache.shenyu.examples.alibaba.dubbo.service.impl.DubboMultiParamServiceImpl#batchSaveAndNameAndId`.
+
+```java
+@Override
+@ShenyuDubboClient(path = "/batchSaveAndNameAndId")
+public DubboTest batchSaveAndNameAndId(List dubboTestList, String id, String name) {
+ DubboTest test = new DubboTest();
+ test.setId(id);
+ test.setName("hello world shenyu alibaba dubbo param batchSaveAndNameAndId :" + name + ":" + dubboTestList.stream().map(DubboTest::getName).collect(Collectors.joining("-")));
+ return test;
+}
+```
+
+
+
+When your arguments do not match, the following exception will occur:
+
+```java
+2021-02-07 22:24:04.015 ERROR 14860 --- [:20888-thread-3] o.d.shenyu.web.handler.GlobalErrorHandler : [e47b2a2a] Resolved [ShenyuException: org.apache.dubbo.remoting.RemotingException: java.lang.IllegalArgumentException: args.length != types.length
+java.lang.IllegalArgumentException: args.length != types.length
+ at org.apache.dubbo.common.utils.PojoUtils.realize(PojoUtils.java:91)
+ at org.apache.dubbo.rpc.filter.GenericFilter.invoke(GenericFilter.java:82)
+ at org.apache.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:81)
+ at org.apache.dubbo.rpc.filter.ClassLoaderFilter.invoke(ClassLoaderFilter.java:38)
+ at org.apache.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:81)
+ at org.apache.dubbo.rpc.filter.EchoFilter.invoke(EchoFilter.java:41)
+ at org.apache.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:81)
+ at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol$1.reply(DubboProtocol.java:150)
+ at org.apache.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.handleRequest(HeaderExchangeHandler.java:100)
+ at org.apache.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.received(HeaderExchangeHandler.java:175)
+ at org.apache.dubbo.remoting.transport.DecodeHandler.received(DecodeHandler.java:51)
+ at org.apache.dubbo.remoting.transport.dispatcher.ChannelEventRunnable.run(ChannelEventRunnable.java:57)
+ at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
+ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
+ at java.lang.Thread.run(Thread.java:748)
+] for HTTP POST /dubbo/batchSaveAndNameAndId
+```
diff --git a/versioned_docs/version-2.6.1/quick-start/quick-start-grpc.md b/versioned_docs/version-2.6.1/quick-start/quick-start-grpc.md
new file mode 100644
index 00000000000..36d1300ce9a
--- /dev/null
+++ b/versioned_docs/version-2.6.1/quick-start/quick-start-grpc.md
@@ -0,0 +1,169 @@
+---
+title: Quick start with gRPC
+description: Quick start with gRPC
+---
+
+This document introduces how to quickly access the Apache ShenYu gateway using gRPC. You can get the code example of this document by clicking [here](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-grpc) .
+
+## Prepare For Environment
+
+Please refer to the deployment to select a way to start shenyu-admin. For example, start the Apache ShenYu gateway management system through [local deployment](../deployment/deployment-local) .
+
+After successful startup, you need to open the gRPC plugin on in the BasicConfig `->` Plugin.
+
+
+
+If you are a startup gateway by means of source, can be directly run the ShenyuBootstrapApplication of shenyu-bootstrap module.
+
+> Note: Before starting, make sure the gateway has added dependencies.
+
+
+Add the following dependencies to the gateway's `pom.xml` file:
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-grpc
+ ${project.version}
+
+
+```
+
+## Run the shenyu-examples-grpc project
+
+Download [shenyu-examples-grpc](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-grpc)
+
+Run the following command under `shenyu-examples-grpc` to generate Java code:
+
+```shell
+mvn protobuf:compile
+mvn protobuf:compile-custom
+```
+
+Execute the `org.apache.shenyu.examples.grpc.ShenyuTestGrpcApplication` main method to start project.
+
+The following log appears when the startup is successful:
+
+```shell
+2021-06-18 19:33:32.866 INFO 11004 --- [or_consumer_-19] o.a.s.r.client.http.utils.RegisterUtils : grpc client register success: {"appName":"127.0.0.1:8080","contextPath":"/grpc","path":"/grpc/clientStreamingFun","pathDesc":"clientStreamingFun","rpcType":"grpc","serviceName":"stream.StreamService","methodName":"clientStreamingFun","ruleName":"/grpc/clientStreamingFun","parameterTypes":"io.grpc.stub.StreamObserver","rpcExt":"{\"timeout\":5000,\"methodType\":\"CLIENT_STREAMING\"}","enabled":true,"host":"172.20.10.6","port":8080,"registerMetaData":false}
+2021-06-18 19:33:32.866 INFO 11004 --- [or_consumer_-17] o.a.s.r.client.http.utils.RegisterUtils : grpc client register success: {"appName":"127.0.0.1:8080","contextPath":"/grpc","path":"/grpc/echo","pathDesc":"echo","rpcType":"grpc","serviceName":"echo.EchoService","methodName":"echo","ruleName":"/grpc/echo","parameterTypes":"echo.EchoRequest,io.grpc.stub.StreamObserver","rpcExt":"{\"timeout\":5000,\"methodType\":\"UNARY\"}","enabled":true,"host":"172.20.10.6","port":8080,"registerMetaData":false}
+2021-06-18 19:33:32.866 INFO 11004 --- [or_consumer_-20] o.a.s.r.client.http.utils.RegisterUtils : grpc client register success: {"appName":"127.0.0.1:8080","contextPath":"/grpc","path":"/grpc/bidiStreamingFun","pathDesc":"bidiStreamingFun","rpcType":"grpc","serviceName":"stream.StreamService","methodName":"bidiStreamingFun","ruleName":"/grpc/bidiStreamingFun","parameterTypes":"io.grpc.stub.StreamObserver","rpcExt":"{\"timeout\":5000,\"methodType\":\"BIDI_STREAMING\"}","enabled":true,"host":"172.20.10.6","port":8080,"registerMetaData":false}
+2021-06-18 19:33:32.866 INFO 11004 --- [or_consumer_-21] o.a.s.r.client.http.utils.RegisterUtils : grpc client register success: {"appName":"127.0.0.1:8080","contextPath":"/grpc","path":"/grpc/unaryFun","pathDesc":"unaryFun","rpcType":"grpc","serviceName":"stream.StreamService","methodName":"unaryFun","ruleName":"/grpc/unaryFun","parameterTypes":"stream.RequestData,io.grpc.stub.StreamObserver","rpcExt":"{\"timeout\":5000,\"methodType\":\"UNARY\"}","enabled":true,"host":"172.20.10.6","port":8080,"registerMetaData":false}
+2021-06-18 19:33:32.866 INFO 11004 --- [or_consumer_-18] o.a.s.r.client.http.utils.RegisterUtils : grpc client register success: {"appName":"127.0.0.1:8080","contextPath":"/grpc","path":"/grpc/serverStreamingFun","pathDesc":"serverStreamingFun","rpcType":"grpc","serviceName":"stream.StreamService","methodName":"serverStreamingFun","ruleName":"/grpc/serverStreamingFun","parameterTypes":"stream.RequestData,io.grpc.stub.StreamObserver","rpcExt":"{\"timeout\":5000,\"methodType\":\"SERVER_STREAMING\"}","enabled":true,"host":"172.20.10.6","port":8080,"registerMetaData":false}
+```
+
+
+## Test
+
+The `shenyu-examples-grpc` project will automatically register interface methods annotated with `@ShenyuGrpcClient` in the Apache ShenYu gateway after successful startup.
+
+Open PluginList -> rpc proxy -> gRPC to see the list of plugin rule configurations:
+
+
+
+Use `postman` to simulate `http` to request your gRPC service. The following is the request body.
+
+```json
+{
+ "data": [
+ {
+ "message": "hello grpc"
+ }
+ ]
+}
+```
+
+
+
+The parameters are passed in json format. The name of the key is `data` by default, and you can reset it in `GrpcConstants.JSON_DESCRIPTOR_PROTO_FIELD_NAME`. The input of value is based on the proto file defined by you.
+
+## Streaming
+
+the Apache ShenYu can support streaming of gRPC. The following shows the calls of the four method types of gRPC. In streaming, you can pass multiple parameters in the form of an array.
+
+
+- `UNARY`
+
+The request body like this.
+
+```json
+{
+ "data": [
+ {
+ "text": "hello grpc"
+ }
+ ]
+}
+```
+
+Then, call gRPC service by `UNARY` method type.
+
+
+
+- `CLIENT_STREAMING`
+
+The request body like this.
+
+```json
+{
+ "data": [
+ {
+ "text": "hello grpc"
+ },
+ {
+ "text": "hello grpc"
+ },
+ {
+ "text": "hello grpc"
+ }
+ ]
+}
+```
+
+Then, call gRPC service by `CLIENT_STREAMING` method type.
+
+
+
+- `SERVER_STREAMING`
+
+The request body like this.
+
+```json
+{
+ "data": [
+ {
+ "text": "hello grpc"
+ }
+ ]
+}
+```
+
+Then, call gRPC service by `SERVER_STREAMING` method type.
+
+
+
+- `BIDI_STREAMING`
+
+
+The request body like this.
+
+```json
+{
+ "data": [
+ {
+ "text": "hello grpc"
+ },
+ {
+ "text": "hello grpc"
+ },
+ {
+ "text": "hello grpc"
+ }
+ ]
+}
+```
+
+Then, call gRPC service by `BIDI_STREAMING` method type.
+
+
diff --git a/versioned_docs/version-2.6.1/quick-start/quick-start-http.md b/versioned_docs/version-2.6.1/quick-start/quick-start-http.md
new file mode 100644
index 00000000000..21d05c79d11
--- /dev/null
+++ b/versioned_docs/version-2.6.1/quick-start/quick-start-http.md
@@ -0,0 +1,80 @@
+---
+title: Quick start with Http
+description: Quick start with http
+---
+
+This document introduces how to quickly access the Apache ShenYu gateway using Http. You can get the code example of this document by clicking [here](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http).
+
+## Environment to prepare
+
+Please refer to the deployment to select a way to start shenyu-admin. For example, start the Apache ShenYu gateway management system through [local deployment](../deployment/deployment-local) .
+
+After successful startup, you need to open the Divide plugin on in the BasicConfig `->` Plugin. In the Apache ShenYu gateway, the HTTP request is handled by the Divide plugin.
+
+
+
+If you are a startup gateway by means of source, can be directly run the ShenyuBootstrapApplication of shenyu-bootstrap module.
+
+> Note: Before starting, make sure the gateway has added dependencies.
+
+
+Add the following dependencies to the gateway's `pom.xml` file:
+
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-divide
+ ${project.version}
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-httpclient
+ ${project.version}
+
+```
+
+
+## Run the shenyu-examples-http project
+
+Download [shenyu-examples-http](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http)
+
+Execute the `org.apache.shenyu.examples.http.ShenyuTestHttpApplication` main method to start project.
+
+Since `2.4.3`, `shenyu.client.http.props.port` can be non-configured if you like.
+
+The following log appears when the startup is successful:
+
+```shell
+2021-02-10 00:57:07.561 INFO 3700 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : http client register success: {"appName":"http","context":"/http","path":"/http/test/**","pathDesc":"","rpcType":"http","host":"192.168.50.13","port":8188,"ruleName":"/http/test/**","enabled":true,"registerMetaData":false}
+2021-02-10 00:57:07.577 INFO 3700 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : http client register success: {"appName":"http","context":"/http","path":"/http/order/save","pathDesc":"Save order","rpcType":"http","host":"192.168.50.13","port":8188,"ruleName":"/http/order/save","enabled":true,"registerMetaData":false}
+2021-02-10 00:57:07.587 INFO 3700 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : http client register success: {"appName":"http","context":"/http","path":"/http/order/path/**/name","pathDesc":"","rpcType":"http","host":"192.168.50.13","port":8188,"ruleName":"/http/order/path/**/name","enabled":true,"registerMetaData":false}
+2021-02-10 00:57:07.596 INFO 3700 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : http client register success: {"appName":"http","context":"/http","path":"/http/order/findById","pathDesc":"Find by id","rpcType":"http","host":"192.168.50.13","port":8188,"ruleName":"/http/order/findById","enabled":true,"registerMetaData":false}
+2021-02-10 00:57:07.606 INFO 3700 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : http client register success: {"appName":"http","context":"/http","path":"/http/order/path/**","pathDesc":"","rpcType":"http","host":"192.168.50.13","port":8188,"ruleName":"/http/order/path/**","enabled":true,"registerMetaData":false}
+2021-02-10 00:57:08.023 INFO 3700 --- [ main] o.s.b.web.embedded.netty.NettyWebServer : Netty started on port(s): 8188
+2021-02-10 00:57:08.026 INFO 3700 --- [ main] o.d.s.e.http.ShenyuTestHttpApplication : Started ShenyuTestHttpApplication in 2.555 seconds (JVM running for 3.411)
+```
+
+
+
+## Test
+
+The `shenyu-examples-http` project will automatically register interface methods annotated with `@ShenyuSpringMvcClient` in the Apache ShenYu gateway after successful startup.
+
+Open PluginList -> Proxy -> divide to see the list of plugin rule configurations:
+
+
+
+Use PostMan to simulate HTTP to request your http service:
+
+
+
+Use IDEA HTTP Client Plugin to simulate HTTP to request your http service[local:no Shenyu proxy]:
+
+
+
+Use IDEA HTTP Client Plugin to simulate HTTP to request your http service[Shenyu proxy]:
+
+
diff --git a/versioned_docs/version-2.6.1/quick-start/quick-start-motan.md b/versioned_docs/version-2.6.1/quick-start/quick-start-motan.md
new file mode 100644
index 00000000000..536382c9c13
--- /dev/null
+++ b/versioned_docs/version-2.6.1/quick-start/quick-start-motan.md
@@ -0,0 +1,97 @@
+---
+title: Quick start with Motan
+description: Motan quick start
+---
+
+This document introduces how to quickly access the Apache ShenYu gateway using Motan RPC. You can get the code example of this document by clicking [here](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-motan).
+
+
+## Environment to prepare
+
+
+Please refer to the deployment to select a way to start shenyu-admin. For example, start the Apache ShenYu gateway management system through [local deployment](../deployment/deployment-local) .
+
+After successful startup, you need to open the Sofa plugin on in the BasicConfig `->` Plugin.
+
+
+
+If you are a startup gateway by means of source, can be directly run the ShenyuBootstrapApplication of shenyu-bootstrap module.
+
+> Note: Before starting, make sure the gateway has added dependencies.
+> Start up zookeeper in local.
+
+Import the gateway proxy plugin for `Motan` and add the following dependencies to the gateway's `pom.xml` file:
+
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-motan
+ ${project.version}
+
+
+
+ com.weibo
+ motan-core
+ 1.1.9
+
+
+
+ com.weibo
+ motan-registry-zookeeper
+ 1.1.9
+
+
+
+ com.weibo
+ motan-transport-netty4
+ 1.1.9
+
+
+
+ com.weibo
+ motan-springsupport
+ 1.1.9
+
+```
+
+
+
+## Run the shenyu-examples-motan project
+
+Download [shenyu-examples-motan](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-motan) .
+
+Run main method of `org.apache.shenyu.examples.motan.service.TestMotanApplication` to start this project.
+
+log info as follows after starting:
+
+```shell
+2021-07-18 16:46:25.388 INFO 96 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8081 (http) with context path ''
+2021-07-18 16:46:25.393 INFO 96 --- [ main] o.a.s.e.m.service.TestMotanApplication : Started TestMotanApplication in 3.89 seconds (JVM running for 4.514)
+2021-07-18 16:46:25.396 INFO 96 --- [ main] info : [ZookeeperRegistry] Url (null) will set to available to Registry [zookeeper://localhost:2181/default_rpc/com.weibo.api.motan.registry.RegistryService/1.0/service]
+2021-07-18 16:46:25.399 INFO 96 --- [ Thread-6] o.a.s.c.c.s.ShenyuClientShutdownHook : hook Thread-0 will sleep 3000ms when it start
+2021-07-18 16:46:25.399 INFO 96 --- [ Thread-6] o.a.s.c.c.s.ShenyuClientShutdownHook : hook SpringContextShutdownHook will sleep 3000ms when it start
+2021-07-18 16:46:25.445 INFO 96 --- [ntLoopGroup-3-2] info : NettyChannelHandler channelActive: remote=/192.168.1.8:49740 local=/192.168.1.8:8002
+2021-07-18 16:46:25.445 INFO 96 --- [ntLoopGroup-3-1] info : NettyChannelHandler channelActive: remote=/192.168.1.8:49739 local=/192.168.1.8:8002
+2021-07-18 16:46:25.925 INFO 96 --- [or_consumer_-17] o.a.s.r.client.http.utils.RegisterUtils : motan client register success: {"appName":"motan","contextPath":"/motan","path":"/motan/hello","pathDesc":"","rpcType":"motan","serviceName":"org.apache.shenyu.examples.motan.service.MotanDemoService","methodName":"hello","ruleName":"/motan/hello","parameterTypes":"java.lang.String","rpcExt":"{\"methodInfo\":[{\"methodName\":\"hello\",\"params\":[{\"left\":\"java.lang.String\",\"right\":\"name\"}]}],\"group\":\"motan-shenyu-rpc\"}","enabled":true,"host":"192.168.220.1","port":8081,"registerMetaData":false}
+
+```
+
+
+
+## Test
+
+The `shenyu-examples-motan` project will automatically register the `@ShenyuMotanClient` annotated interface methods with the gateway and add selectors and rules. If not, you can manually add them.
+
+
+Open PluginList -> rpc proxy -> motan to see the list of plugin rule configurations:
+
+
+
+
+Use PostMan to simulate HTTP to request your Motan service:
+
+
+
+
diff --git a/versioned_docs/version-2.6.1/quick-start/quick-start-sofa.md b/versioned_docs/version-2.6.1/quick-start/quick-start-sofa.md
new file mode 100644
index 00000000000..713ed8c12fd
--- /dev/null
+++ b/versioned_docs/version-2.6.1/quick-start/quick-start-sofa.md
@@ -0,0 +1,138 @@
+---
+title: Quick start with Sofa
+description: Quick start with Sofa
+---
+
+This document introduces how to quickly access the Apache ShenYu gateway using Sofa RPC. You can get the code example of this document by clicking [here](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-sofa).
+
+## Environment to prepare
+
+
+Please refer to the deployment to select a way to start shenyu-admin. For example, start the Apache ShenYu gateway management system through [local deployment](../deployment/deployment-local) .
+
+After successful startup, you need to open the Sofa plugin on in the BasicConfig `->` Plugin, and set your registry address. Please make sure the registry center is open locally.
+
+
+
+If you are a startup gateway by means of source, can be directly run the ShenyuBootstrapApplication of shenyu-bootstrap module.
+
+> Note: Before starting, make sure the gateway has added dependencies.
+
+
+If client is `sofa`, registry center is `Zookeeper`, please refer to the following configuration:
+
+
+
+```xml
+
+
+ com.alipay.sofa
+ sofa-rpc-all
+ 5.7.6
+
+
+ org.apache.curator
+ curator-client
+ 4.0.1
+
+
+ org.apache.curator
+ curator-framework
+ 4.0.1
+
+
+ org.apache.curator
+ curator-recipes
+ 4.0.1
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-sofa
+ ${project.version}
+
+
+
+```
+
+## Run the shenyu-examples-sofa project
+
+Download [shenyu-examples-sofa](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-sofa), replace the register address in `spring-dubbo.xml` with your local zk address, such as:
+
+```yaml
+com:
+ alipay:
+ sofa:
+ rpc:
+ registry-address: zookeeper://127.0.0.1:2181
+```
+
+Execute the `org.apache.shenyu.examples.sofa.service.TestSofaApplication` main method to start sofa service.
+
+The following log appears when the startup is successful:
+
+```shell
+2021-02-10 02:31:45.599 INFO 2156 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : sofa client register success: {"appName":"sofa","contextPath":"/sofa","path":"/sofa/insert","pathDesc":"Insert a row of data","rpcType":"sofa","serviceName":"org.dromara.shenyu.examples.sofa.api.service.SofaSingleParamService","methodName":"insert","ruleName":"/sofa/insert","parameterTypes":"org.dromara.shenyu.examples.sofa.api.entity.SofaSimpleTypeBean","rpcExt":"{\"loadbalance\":\"hash\",\"retries\":3,\"timeout\":-1}","enabled":true}
+2021-02-10 02:31:45.605 INFO 2156 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : sofa client register success: {"appName":"sofa","contextPath":"/sofa","path":"/sofa/findById","pathDesc":"Find by Id","rpcType":"sofa","serviceName":"org.dromara.shenyu.examples.sofa.api.service.SofaSingleParamService","methodName":"findById","ruleName":"/sofa/findById","parameterTypes":"java.lang.String","rpcExt":"{\"loadbalance\":\"hash\",\"retries\":3,\"timeout\":-1}","enabled":true}
+2021-02-10 02:31:45.611 INFO 2156 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : sofa client register success: {"appName":"sofa","contextPath":"/sofa","path":"/sofa/findAll","pathDesc":"Get all data","rpcType":"sofa","serviceName":"org.dromara.shenyu.examples.sofa.api.service.SofaSingleParamService","methodName":"findAll","ruleName":"/sofa/findAll","parameterTypes":"","rpcExt":"{\"loadbalance\":\"hash\",\"retries\":3,\"timeout\":-1}","enabled":true}
+2021-02-10 02:31:45.616 INFO 2156 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : sofa client register success: {"appName":"sofa","contextPath":"/sofa","path":"/sofa/batchSaveNameAndId","pathDesc":"","rpcType":"sofa","serviceName":"org.dromara.shenyu.examples.sofa.api.service.SofaMultiParamService","methodName":"batchSaveNameAndId","ruleName":"/sofa/batchSaveNameAndId","parameterTypes":"java.util.List,java.lang.String,java.lang.String#org.dromara.shenyu.examples.sofa.api.entity.SofaSimpleTypeBean","rpcExt":"{\"loadbalance\":\"hash\",\"retries\":3,\"timeout\":-1}","enabled":true}
+2021-02-10 02:31:45.621 INFO 2156 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : sofa client register success: {"appName":"sofa","contextPath":"/sofa","path":"/sofa/saveComplexBeanAndName","pathDesc":"","rpcType":"sofa","serviceName":"org.dromara.shenyu.examples.sofa.api.service.SofaMultiParamService","methodName":"saveComplexBeanAndName","ruleName":"/sofa/saveComplexBeanAndName","parameterTypes":"org.dromara.shenyu.examples.sofa.api.entity.SofaComplexTypeBean,java.lang.String","rpcExt":"{\"loadbalance\":\"hash\",\"retries\":3,\"timeout\":-1}","enabled":true}
+2021-02-10 02:31:45.627 INFO 2156 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : sofa client register success: {"appName":"sofa","contextPath":"/sofa","path":"/sofa/findByArrayIdsAndName","pathDesc":"","rpcType":"sofa","serviceName":"org.dromara.shenyu.examples.sofa.api.service.SofaMultiParamService","methodName":"findByArrayIdsAndName","ruleName":"/sofa/findByArrayIdsAndName","parameterTypes":"[Ljava.lang.Integer;,java.lang.String","rpcExt":"{\"loadbalance\":\"hash\",\"retries\":3,\"timeout\":-1}","enabled":true}
+2021-02-10 02:31:45.632 INFO 2156 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : sofa client register success: {"appName":"sofa","contextPath":"/sofa","path":"/sofa/findByStringArray","pathDesc":"","rpcType":"sofa","serviceName":"org.dromara.shenyu.examples.sofa.api.service.SofaMultiParamService","methodName":"findByStringArray","ruleName":"/sofa/findByStringArray","parameterTypes":"[Ljava.lang.String;","rpcExt":"{\"loadbalance\":\"hash\",\"retries\":3,\"timeout\":-1}","enabled":true}
+2021-02-10 02:31:45.637 INFO 2156 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : sofa client register success: {"appName":"sofa","contextPath":"/sofa","path":"/sofa/saveTwoList","pathDesc":"","rpcType":"sofa","serviceName":"org.dromara.shenyu.examples.sofa.api.service.SofaMultiParamService","methodName":"saveTwoList","ruleName":"/sofa/saveTwoList","parameterTypes":"java.util.List,java.util.Map#org.dromara.shenyu.examples.sofa.api.entity.SofaComplexTypeBean","rpcExt":"{\"loadbalance\":\"hash\",\"retries\":3,\"timeout\":-1}","enabled":true}
+2021-02-10 02:31:45.642 INFO 2156 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : sofa client register success: {"appName":"sofa","contextPath":"/sofa","path":"/sofa/batchSave","pathDesc":"","rpcType":"sofa","serviceName":"org.dromara.shenyu.examples.sofa.api.service.SofaMultiParamService","methodName":"batchSave","ruleName":"/sofa/batchSave","parameterTypes":"java.util.List#org.dromara.shenyu.examples.sofa.api.entity.SofaSimpleTypeBean","rpcExt":"{\"loadbalance\":\"hash\",\"retries\":3,\"timeout\":-1}","enabled":true}
+2021-02-10 02:31:45.647 INFO 2156 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : sofa client register success: {"appName":"sofa","contextPath":"/sofa","path":"/sofa/findByListId","pathDesc":"","rpcType":"sofa","serviceName":"org.dromara.shenyu.examples.sofa.api.service.SofaMultiParamService","methodName":"findByListId","ruleName":"/sofa/findByListId","parameterTypes":"java.util.List","rpcExt":"{\"loadbalance\":\"hash\",\"retries\":3,\"timeout\":-1}","enabled":true}
+2021-02-10 02:31:45.653 INFO 2156 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : sofa client register success: {"appName":"sofa","contextPath":"/sofa","path":"/sofa/saveComplexBean","pathDesc":"","rpcType":"sofa","serviceName":"org.dromara.shenyu.examples.sofa.api.service.SofaMultiParamService","methodName":"saveComplexBean","ruleName":"/sofa/saveComplexBean","parameterTypes":"org.dromara.shenyu.examples.sofa.api.entity.SofaComplexTypeBean","rpcExt":"{\"loadbalance\":\"hash\",\"retries\":3,\"timeout\":-1}","enabled":true}
+2021-02-10 02:31:45.660 INFO 2156 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : sofa client register success: {"appName":"sofa","contextPath":"/sofa","path":"/sofa/findByIdsAndName","pathDesc":"","rpcType":"sofa","serviceName":"org.dromara.shenyu.examples.sofa.api.service.SofaMultiParamService","methodName":"findByIdsAndName","ruleName":"/sofa/findByIdsAndName","parameterTypes":"java.util.List,java.lang.String","rpcExt":"{\"loadbalance\":\"hash\",\"retries\":3,\"timeout\":-1}","enabled":true}
+2021-02-10 02:31:46.055 INFO 2156 --- [ main] o.a.c.f.imps.CuratorFrameworkImpl : Starting
+2021-02-10 02:31:46.059 INFO 2156 --- [ main] org.apache.zookeeper.ZooKeeper : Client environment:zookeeper.version=3.4.6-1569965, built on 02/20/2014 09:09 GMT
+2021-02-10 02:31:46.059 INFO 2156 --- [ main] org.apache.zookeeper.ZooKeeper : Client environment:host.name=host.docker.internal
+2021-02-10 02:31:46.059 INFO 2156 --- [ main] org.apache.zookeeper.ZooKeeper : Client environment:java.version=1.8.0_211
+2021-02-10 02:31:46.059 INFO 2156 --- [ main] org.apache.zookeeper.ZooKeeper : Client environment:java.vendor=Oracle Corporation
+2021-02-10 02:31:46.059 INFO 2156 --- [ main] org.apache.zookeeper.ZooKeeper : Client environment:java.home=C:\Program Files\Java\jdk1.8.0_211\jre
+2021-02-10 02:31:46.059 INFO 2156 --- [ main] org.apache.zookeeper.ZooKeeper : Client environment:java.class.path=C:\Program Files\Java\jdk1.8.0_211\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\deploy.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\ext\access-bridge-64.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\ext\cldrdata.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\ext\dnsns.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\ext\jaccess.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\ext\jfxrt.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\ext\localedata.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\ext\nashorn.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\ext\sunec.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\ext\sunjce_provider.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\ext\sunmscapi.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\ext\sunpkcs11.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\ext\zipfs.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\javaws.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\jfxswt.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\management-agent.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\plugin.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_211\jre\lib\rt.jar;D:\X\dlm_github\shenyu\shenyu-examples\shenyu-examples-sofa\shenyu-examples-sofa-service\target\classes;D:\SOFT\m2\repository\com\alipay\sofa\rpc-sofa-boot-starter\6.0.4\rpc-sofa-boot-starter-6.0.4.jar;D:\SOFT\m2\repository\com\alipay\sofa\rpc-sofa-boot-core\6.0.4\rpc-sofa-boot-core-6.0.4.jar;D:\SOFT\m2\repository\com\alipay\sofa\sofa-rpc-all\5.5.7\sofa-rpc-all-5.5.7.jar;D:\SOFT\m2\repository\com\alipay\sofa\bolt\1.4.6\bolt-1.4.6.jar;D:\SOFT\m2\repository\org\javassist\javassist\3.20.0-GA\javassist-3.20.0-GA.jar;D:\SOFT\m2\repository\io\netty\netty-all\4.1.43.Final\netty-all-4.1.43.Final.jar;D:\SOFT\m2\repository\com\alipay\sofa\hessian\3.3.6\hessian-3.3.6.jar;D:\SOFT\m2\repository\com\alipay\sofa\tracer-core\2.1.2\tracer-core-2.1.2.jar;D:\SOFT\m2\repository\io\opentracing\opentracing-api\0.22.0\opentracing-api-0.22.0.jar;D:\SOFT\m2\repository\io\opentracing\opentracing-noop\0.22.0\opentracing-noop-0.22.0.jar;D:\SOFT\m2\repository\io\opentracing\opentracing-mock\0.22.0\opentracing-mock-0.22.0.jar;D:\SOFT\m2\repository\io\opentracing\opentracing-util\0.22.0\opentracing-util-0.22.0.jar;D:\SOFT\m2\repository\com\alipay\sofa\lookout\lookout-api\1.4.1\lookout-api-1.4.1.jar;D:\SOFT\m2\repository\com\alipay\sofa\runtime-sofa-boot-starter\3.1.4\runtime-sofa-boot-starter-3.1.4.jar;D:\SOFT\m2\repository\org\apache\curator\curator-client\2.9.1\curator-client-2.9.1.jar;D:\SOFT\m2\repository\org\apache\zookeeper\zookeeper\3.4.6\zookeeper-3.4.6.jar;D:\SOFT\m2\repository\log4j\log4j\1.2.16\log4j-1.2.16.jar;D:\SOFT\m2\repository\jline\jline\0.9.94\jline-0.9.94.jar;D:\SOFT\m2\repository\io\netty\netty\3.7.0.Final\netty-3.7.0.Final.jar;D:\SOFT\m2\repository\com\google\guava\guava\16.0.1\guava-16.0.1.jar;D:\SOFT\m2\repository\org\apache\curator\curator-framework\2.9.1\curator-framework-2.9.1.jar;D:\SOFT\m2\repository\org\apache\curator\curator-recipes\2.9.1\curator-recipes-2.9.1.jar;D:\SOFT\m2\repository\org\jboss\resteasy\resteasy-jaxrs\3.0.12.Final\resteasy-jaxrs-3.0.12.Final.jar;D:\SOFT\m2\repository\org\jboss\spec\javax\annotation\jboss-annotations-api_1.1_spec\1.0.1.Final\jboss-annotations-api_1.1_spec-1.0.1.Final.jar;D:\SOFT\m2\repository\javax\activation\activation\1.1.1\activation-1.1.1.jar;D:\SOFT\m2\repository\org\apache\httpcomponents\httpclient\4.5.10\httpclient-4.5.10.jar;D:\SOFT\m2\repository\org\apache\httpcomponents\httpcore\4.4.12\httpcore-4.4.12.jar;D:\SOFT\m2\repository\commons-io\commons-io\2.1\commons-io-2.1.jar;D:\SOFT\m2\repository\net\jcip\jcip-annotations\1.0\jcip-annotations-1.0.jar;D:\SOFT\m2\repository\org\jboss\resteasy\resteasy-client\3.0.12.Final\resteasy-client-3.0.12.Final.jar;D:\SOFT\m2\repository\org\jboss\resteasy\resteasy-jackson-provider\3.0.12.Final\resteasy-jackson-provider-3.0.12.Final.jar;D:\SOFT\m2\repository\org\codehaus\jackson\jackson-core-asl\1.9.12\jackson-core-asl-1.9.12.jar;D:\SOFT\m2\repository\org\codehaus\jackson\jackson-mapper-asl\1.9.12\jackson-mapper-asl-1.9.12.jar;D:\SOFT\m2\repository\org\codehaus\jackson\jackson-jaxrs\1.9.12\jackson-jaxrs-1.9.12.jar;D:\SOFT\m2\repository\org\codehaus\jackson\jackson-xc\1.9.12\jackson-xc-1.9.12.jar;D:\SOFT\m2\repository\org\jboss\resteasy\resteasy-netty4\3.0.12.Final\resteasy-netty4-3.0.12.Final.jar;D:\SOFT\m2\repository\org\jboss\resteasy\resteasy-validator-provider-11\3.0.12.Final\resteasy-validator-provider-11-3.0.12.Final.jar;D:\SOFT\m2\repository\com\fasterxml\classmate\1.5.1\classmate-1.5.1.jar;D:\SOFT\m2\repository\org\jboss\resteasy\jaxrs-api\3.0.12.Final\jaxrs-api-3.0.12.Final.jar;D:\SOFT\m2\repository\org\jboss\resteasy\resteasy-multipart-provider\3.0.12.Final\resteasy-multipart-provider-3.0.12.Final.jar;D:\SOFT\m2\repository\org\jboss\resteasy\resteasy-jaxb-provider\3.0.12.Final\resteasy-jaxb-provider-3.0.12.Final.jar;D:\SOFT\m2\repository\com\sun\xml\bind\jaxb-impl\2.2.7\jaxb-impl-2.2.7.jar;D:\SOFT\m2\repository\com\sun\xml\bind\jaxb-core\2.2.7\jaxb-core-2.2.7.jar;D:\SOFT\m2\repository\javax\xml\bind\jaxb-api\2.3.1\jaxb-api-2.3.1.jar;D:\SOFT\m2\repository\javax\activation\javax.activation-api\1.2.0\javax.activation-api-1.2.0.jar;D:\SOFT\m2\repository\com\sun\istack\istack-commons-runtime\2.16\istack-commons-runtime-2.16.jar;D:\SOFT\m2\repository\com\sun\xml\fastinfoset\FastInfoset\1.2.12\FastInfoset-1.2.12.jar;D:\SOFT\m2\repository\javax\xml\bind\jsr173_api\1.0\jsr173_api-1.0.jar;D:\SOFT\m2\repository\javax\mail\mail\1.5.0-b01\mail-1.5.0-b01.jar;D:\SOFT\m2\repository\org\apache\james\apache-mime4j\0.6\apache-mime4j-0.6.jar;D:\SOFT\m2\repository\commons-logging\commons-logging\1.1.1\commons-logging-1.1.1.jar;D:\SOFT\m2\repository\com\alibaba\dubbo\2.4.10\dubbo-2.4.10.jar;D:\SOFT\m2\repository\org\jboss\netty\netty\3.2.5.Final\netty-3.2.5.Final.jar;D:\SOFT\m2\repository\com\101tec\zkclient\0.10\zkclient-0.10.jar;D:\SOFT\m2\repository\com\alibaba\nacos\nacos-api\1.0.0\nacos-api-1.0.0.jar;D:\SOFT\m2\repository\com\alibaba\fastjson\1.2.47\fastjson-1.2.47.jar;D:\SOFT\m2\repository\org\apache\commons\commons-lang3\3.9\commons-lang3-3.9.jar;D:\SOFT\m2\repository\com\alibaba\nacos\nacos-client\1.0.0\nacos-client-1.0.0.jar;D:\SOFT\m2\repository\com\alibaba\nacos\nacos-common\1.0.0\nacos-common-1.0.0.jar;D:\SOFT\m2\repository\commons-codec\commons-codec\1.13\commons-codec-1.13.jar;D:\SOFT\m2\repository\com\fasterxml\jackson\core\jackson-core\2.10.1\jackson-core-2.10.1.jar;D:\SOFT\m2\repository\com\fasterxml\jackson\core\jackson-databind\2.10.1\jackson-databind-2.10.1.jar;D:\SOFT\m2\repository\com\fasterxml\jackson\core\jackson-annotations\2.10.1\jackson-annotations-2.10.1.jar;D:\SOFT\m2\repository\io\prometheus\simpleclient\0.5.0\simpleclient-0.5.0.jar;D:\SOFT\m2\repository\org\springframework\spring-beans\5.2.2.RELEASE\spring-beans-5.2.2.RELEASE.jar;D:\SOFT\m2\repository\org\springframework\spring-core\5.2.2.RELEASE\spring-core-5.2.2.RELEASE.jar;D:\SOFT\m2\repository\org\springframework\spring-jcl\5.2.2.RELEASE\spring-jcl-5.2.2.RELEASE.jar;D:\SOFT\m2\repository\com\alipay\sofa\infra-sofa-boot-starter\3.1.4\infra-sofa-boot-starter-3.1.4.jar;D:\SOFT\m2\repository\com\alipay\sofa\common\log-sofa-boot-starter\1.0.18\log-sofa-boot-starter-1.0.18.jar;D:\SOFT\m2\repository\org\springframework\spring-context\5.2.2.RELEASE\spring-context-5.2.2.RELEASE.jar;D:\SOFT\m2\repository\org\springframework\spring-aop\5.2.2.RELEASE\spring-aop-5.2.2.RELEASE.jar;D:\SOFT\m2\repository\org\springframework\spring-expression\5.2.2.RELEASE\spring-expression-5.2.2.RELEASE.jar;D:\SOFT\m2\repository\com\alipay\sofa\common\sofa-common-tools\1.0.18\sofa-common-tools-1.0.18.jar;D:\SOFT\m2\repository\org\springframework\boot\spring-boot-starter-validation\2.2.2.RELEASE\spring-boot-starter-validation-2.2.2.RELEASE.jar;D:\SOFT\m2\repository\jakarta\validation\jakarta.validation-api\2.0.1\jakarta.validation-api-2.0.1.jar;D:\SOFT\m2\repository\org\hibernate\validator\hibernate-validator\6.0.18.Final\hibernate-validator-6.0.18.Final.jar;D:\SOFT\m2\repository\org\jboss\logging\jboss-logging\3.4.1.Final\jboss-logging-3.4.1.Final.jar;D:\SOFT\m2\repository\org\apache\tomcat\embed\tomcat-embed-el\9.0.29\tomcat-embed-el-9.0.29.jar;D:\SOFT\m2\repository\org\springframework\boot\spring-boot-autoconfigure\2.2.2.RELEASE\spring-boot-autoconfigure-2.2.2.RELEASE.jar;D:\SOFT\m2\repository\org\springframework\boot\spring-boot\2.2.2.RELEASE\spring-boot-2.2.2.RELEASE.jar;D:\X\dlm_github\shenyu\shenyu-examples\shenyu-examples-sofa\shenyu-examples-sofa-api\target\classes;D:\SOFT\m2\repository\org\projectlombok\lombok\1.18.10\lombok-1.18.10.jar;D:\X\dlm_github\shenyu\shenyu-spring-boot-starter\shenyu-spring-boot-starter-client\shenyu-spring-boot-starter-client-sofa\target\classes;D:\SOFT\m2\repository\org\springframework\boot\spring-boot-starter\2.2.2.RELEASE\spring-boot-starter-2.2.2.RELEASE.jar;D:\SOFT\m2\repository\org\springframework\boot\spring-boot-starter-logging\2.2.2.RELEASE\spring-boot-starter-logging-2.2.2.RELEASE.jar;D:\SOFT\m2\repository\ch\qos\logback\logback-classic\1.2.3\logback-classic-1.2.3.jar;D:\SOFT\m2\repository\ch\qos\logback\logback-core\1.2.3\logback-core-1.2.3.jar;D:\SOFT\m2\repository\org\apache\logging\log4j\log4j-to-slf4j\2.12.1\log4j-to-slf4j-2.12.1.jar;D:\SOFT\m2\repository\org\apache\logging\log4j\log4j-api\2.12.1\log4j-api-2.12.1.jar;D:\SOFT\m2\repository\org\slf4j\jul-to-slf4j\1.7.29\jul-to-slf4j-1.7.29.jar;D:\SOFT\m2\repository\jakarta\annotation\jakarta.annotation-api\1.3.5\jakarta.annotation-api-1.3.5.jar;D:\SOFT\m2\repository\org\yaml\snakeyaml\1.25\snakeyaml-1.25.jar;D:\X\dlm_github\shenyu\shenyu-client\shenyu-client-sofa\target\classes;D:\X\dlm_github\shenyu\shenyu-client\shenyu-client-common\target\classes;D:\X\dlm_github\shenyu\shenyu-common\target\classes;D:\SOFT\m2\repository\org\springframework\boot\spring-boot-starter-json\2.2.2.RELEASE\spring-boot-starter-json-2.2.2.RELEASE.jar;D:\SOFT\m2\repository\org\springframework\spring-web\5.2.2.RELEASE\spring-web-5.2.2.RELEASE.jar;D:\SOFT\m2\repository\com\fasterxml\jackson\datatype\jackson-datatype-jdk8\2.10.1\jackson-datatype-jdk8-2.10.1.jar;D:\SOFT\m2\repository\com\fasterxml\jackson\datatype\jackson-datatype-jsr310\2.10.1\jackson-datatype-jsr310-2.10.1.jar;D:\SOFT\m2\repository\com\fasterxml\jackson\module\jackson-module-parameter-names\2.10.1\jackson-module-parameter-names-2.10.1.jar;D:\SOFT\m2\repository\com\squareup\okhttp3\okhttp\3.14.4\okhttp-3.14.4.jar;D:\SOFT\m2\repository\com\squareup\okio\okio\1.17.2\okio-1.17.2.jar;D:\SOFT\m2\repository\com\google\code\gson\gson\2.8.6\gson-2.8.6.jar;D:\SOFT\m2\repository\org\slf4j\slf4j-api\1.7.29\slf4j-api-1.7.29.jar;D:\SOFT\m2\repository\org\slf4j\jcl-over-slf4j\1.7.29\jcl-over-slf4j-1.7.29.jar;C:\Program Files\JetBrains\IntelliJ IDEA 2019.3.3\lib\idea_rt.jar
+2021-02-10 02:31:46.060 INFO 2156 --- [ main] org.apache.zookeeper.ZooKeeper : Client environment:java.library.path=C:\Program Files\Java\jdk1.8.0_211\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Common Files\Oracle\Java\javapath;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\Java\jdk1.8.0_211\bin;C:\Program Files\Java\jdk1.8.0_211\jre\bin;D:\SOFT\apache-maven-3.5.0\bin;C:\Program Files\Go\bin;C:\Program Files\nodejs\;C:\Program Files\Python\Python38\;C:\Program Files\OpenSSL-Win64\bin;C:\Program Files\Git\bin;D:\SOFT\protobuf-2.5.0\src;D:\SOFT\zlib-1.2.8;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Docker\Docker\resources\bin;C:\ProgramData\DockerDesktop\version-bin;D:\SOFT\gradle-6.0-all\gradle-6.0\bin;C:\Program Files\mingw-w64\x86_64-8.1.0-posix-seh-rt_v6-rev0\mingw64\bin;D:\SOFT\hugo_extended_0.55.5_Windows-64bit;C:\Users\DLM\AppData\Local\Microsoft\WindowsApps;C:\Users\DLM\go\bin;C:\Users\DLM\AppData\Roaming\npm;;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\nimbella-cli\bin;.
+2021-02-10 02:31:46.060 INFO 2156 --- [ main] org.apache.zookeeper.ZooKeeper : Client environment:java.io.tmpdir=C:\Users\DLM\AppData\Local\Temp\
+2021-02-10 02:31:46.060 INFO 2156 --- [ main] org.apache.zookeeper.ZooKeeper : Client environment:java.compiler=
+2021-02-10 02:31:46.060 INFO 2156 --- [ main] org.apache.zookeeper.ZooKeeper : Client environment:os.name=Windows 10
+2021-02-10 02:31:46.060 INFO 2156 --- [ main] org.apache.zookeeper.ZooKeeper : Client environment:os.arch=amd64
+2021-02-10 02:31:46.060 INFO 2156 --- [ main] org.apache.zookeeper.ZooKeeper : Client environment:os.version=10.0
+2021-02-10 02:31:46.060 INFO 2156 --- [ main] org.apache.zookeeper.ZooKeeper : Client environment:user.name=DLM
+2021-02-10 02:31:46.060 INFO 2156 --- [ main] org.apache.zookeeper.ZooKeeper : Client environment:user.home=C:\Users\DLM
+2021-02-10 02:31:46.060 INFO 2156 --- [ main] org.apache.zookeeper.ZooKeeper : Client environment:user.dir=D:\X\dlm_github\shenyu
+2021-02-10 02:31:46.061 INFO 2156 --- [ main] org.apache.zookeeper.ZooKeeper : Initiating client connection, connectString=127.0.0.1:21810 sessionTimeout=60000 watcher=org.apache.curator.ConnectionState@3e850122
+2021-02-10 02:31:46.069 INFO 2156 --- [27.0.0.1:21810)] org.apache.zookeeper.ClientCnxn : Opening socket connection to server 127.0.0.1/127.0.0.1:21810. Will not attempt to authenticate using SASL (unknown error)
+2021-02-10 02:31:46.071 INFO 2156 --- [27.0.0.1:21810)] org.apache.zookeeper.ClientCnxn : Socket connection established to 127.0.0.1/127.0.0.1:21810, initiating session
+2021-02-10 02:31:46.078 INFO 2156 --- [27.0.0.1:21810)] org.apache.zookeeper.ClientCnxn : Session establishment complete on server 127.0.0.1/127.0.0.1:21810, sessionid = 0x10005b0d05e0001, negotiated timeout = 40000
+2021-02-10 02:31:46.081 INFO 2156 --- [ain-EventThread] o.a.c.f.state.ConnectionStateManager : State change: CONNECTED
+2021-02-10 02:31:46.093 WARN 2156 --- [ main] org.apache.curator.utils.ZKPaths : The version of ZooKeeper being used doesn't support Container nodes. CreateMode.PERSISTENT will be used instead.
+2021-02-10 02:31:46.141 INFO 2156 --- [ main] o.d.s.e.s.service.TestSofaApplication : Started TestSofaApplication in 3.41 seconds (JVM running for 4.423)
+```
+
+
+## Test
+
+The `shenyu-examples-sofa` project will automatically register interface methods annotated with `@ShenyuSofaClient` in the Apache ShenYu gateway after successful startup.
+
+Open PluginList -> rpc proxy -> sofa to see the list of plugin rule configurations:
+
+
+
+Use PostMan to simulate HTTP to request your Sofa service:
+
+
+
+Complex multi-parameter example: The related interface implementation class is `org.apache.shenyu.examples.sofa.service.impl.SofaMultiParamServiceImpl#batchSaveNameAndId`
+
+```java
+@Override
+@ShenyuSofaClient(path = "/batchSaveNameAndId")
+public SofaSimpleTypeBean batchSaveNameAndId(final List sofaTestList, final String id, final String name) {
+ SofaSimpleTypeBean simpleTypeBean = new SofaSimpleTypeBean();
+ simpleTypeBean.setId(id);
+ simpleTypeBean.setName("hello world shenyu sofa param batchSaveAndNameAndId :" + name + ":" + sofaTestList.stream().map(SofaSimpleTypeBean::getName).collect(Collectors.joining("-")));
+ return simpleTypeBean;
+}
+```
+
+
diff --git a/versioned_docs/version-2.6.1/quick-start/quick-start-springcloud.md b/versioned_docs/version-2.6.1/quick-start/quick-start-springcloud.md
new file mode 100644
index 00000000000..710c8045359
--- /dev/null
+++ b/versioned_docs/version-2.6.1/quick-start/quick-start-springcloud.md
@@ -0,0 +1,166 @@
+---
+title: Quick start with Spring Cloud
+description: Quick start with SpringCloud
+---
+
+This document introduces how to quickly access the Apache ShenYu gateway using Spring Cloud. You can get the code example of this document by clicking [here](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-springcloud) .
+
+## Environment to prepare
+
+
+Please refer to the deployment to select a way to start shenyu-admin. For example, start the Apache ShenYu gateway management system through [local deployment](../deployment/deployment-local) .
+
+After successful startup, you need to open the springCloud plugin on in the BasicConfig `->` Plugin.
+
+
+
+If you are a startup gateway by means of source, can be directly run the ShenyuBootstrapApplication of shenyu-bootstrap module.
+
+> Note: Before starting, make sure the gateway has added dependencies.
+
+Add the gateway proxy plugin for `Spring Cloud` and add your registry center dependencies:
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-springcloud
+ ${project.version}
+
+
+
+ org.springframework.cloud
+ spring-cloud-commons
+ 2.2.0.RELEASE
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-httpclient
+ ${project.version}
+
+
+
+ org.springframework.cloud
+ spring-cloud-starter-netflix-eureka-client
+ 2.2.0.RELEASE
+
+
+```
+
+
+`eureka` config information:
+
+```yml
+eureka:
+ client:
+ serviceUrl:
+ defaultZone: http://localhost:8761/eureka/
+ instance:
+ prefer-ip-address: true
+```
+
+Note: Please ensure that the spring Cloud registry service discovery configuration is enabled
+
+* Configuration method
+
+```yml
+spring:
+ cloud:
+ discovery:
+ enabled: true
+```
+
+* code method
+
+```java
+@SpringBootApplication
+@EnableDiscoveryClient
+public class ShenyuBootstrapApplication {
+
+ /**
+ * Main Entrance.
+ *
+ * @param args startup arguments
+ */
+ public static void main(final String[] args) {
+ SpringApplication.run(ShenyuBootstrapApplication.class, args);
+ }
+}
+```
+
+Restart the `shenyu-bootstrap` project.
+
+## Run the shenyu-examples-springcloud project
+
+In the example project we used `Eureka` as the registry for `Spring Cloud`. You can use the local `Eureka` or the application provided in the example.
+
+
+Download [shenyu-examples-eureka](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-eureka) 、[shenyu-examples-springcloud](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-springcloud) .
+
+
+Startup the Eureka service:
+Execute the `org.apache.shenyu.examples.eureka.EurekaServerApplication` main method to start project.
+
+Startup the Spring Cloud service:
+Execute the `org.apache.shenyu.examples.springcloud.ShenyuTestSpringCloudApplication` main method to start project.
+
+Since `2.4.3`, `shenyu.client.springCloud.props.port` can be non-configured if you like.
+
+The following log appears when the startup is successful:
+
+```shell
+2021-02-10 14:03:51.301 INFO 2860 --- [ main] o.s.s.concurrent.ThreadPoolTaskExecutor : Initializing ExecutorService 'applicationTaskExecutor'
+2021-02-10 14:03:51.669 INFO 2860 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : springCloud client register success: {"appName":"springCloud-test","context":"/springcloud","path":"/springcloud/order/save","pathDesc":"","rpcType":"springCloud","ruleName":"/springcloud/order/save","enabled":true}
+2021-02-10 14:03:51.676 INFO 2860 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : springCloud client register success: {"appName":"springCloud-test","context":"/springcloud","path":"/springcloud/order/path/**","pathDesc":"","rpcType":"springCloud","ruleName":"/springcloud/order/path/**","enabled":true}
+2021-02-10 14:03:51.682 INFO 2860 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : springCloud client register success: {"appName":"springCloud-test","context":"/springcloud","path":"/springcloud/order/findById","pathDesc":"","rpcType":"springCloud","ruleName":"/springcloud/order/findById","enabled":true}
+2021-02-10 14:03:51.688 INFO 2860 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : springCloud client register success: {"appName":"springCloud-test","context":"/springcloud","path":"/springcloud/order/path/**/name","pathDesc":"","rpcType":"springCloud","ruleName":"/springcloud/order/path/**/name","enabled":true}
+2021-02-10 14:03:51.692 INFO 2860 --- [pool-1-thread-1] o.d.s.client.common.utils.RegisterUtils : springCloud client register success: {"appName":"springCloud-test","context":"/springcloud","path":"/springcloud/test/**","pathDesc":"","rpcType":"springCloud","ruleName":"/springcloud/test/**","enabled":true}
+2021-02-10 14:03:52.806 WARN 2860 --- [ main] ockingLoadBalancerClientRibbonWarnLogger : You already have RibbonLoadBalancerClient on your classpath. It will be used by default. As Spring Cloud Ribbon is in maintenance mode. We recommend switching to BlockingLoadBalancerClient instead. In order to use it, set the value of `spring.cloud.loadbalancer.ribbon.enabled` to `false` or remove spring-cloud-starter-netflix-ribbon from your project.
+2021-02-10 14:03:52.848 WARN 2860 --- [ main] iguration$LoadBalancerCaffeineWarnLogger : Spring Cloud LoadBalancer is currently working with default default cache. You can switch to using Caffeine cache, by adding it to the classpath.
+2021-02-10 14:03:52.921 INFO 2860 --- [ main] o.s.c.n.eureka.InstanceInfoFactory : Setting initial instance status as: STARTING
+2021-02-10 14:03:52.949 INFO 2860 --- [ main] com.netflix.discovery.DiscoveryClient : Initializing Eureka in region us-east-1
+2021-02-10 14:03:53.006 INFO 2860 --- [ main] c.n.d.provider.DiscoveryJerseyProvider : Using JSON encoding codec LegacyJacksonJson
+2021-02-10 14:03:53.006 INFO 2860 --- [ main] c.n.d.provider.DiscoveryJerseyProvider : Using JSON decoding codec LegacyJacksonJson
+2021-02-10 14:03:53.110 INFO 2860 --- [ main] c.n.d.provider.DiscoveryJerseyProvider : Using XML encoding codec XStreamXml
+2021-02-10 14:03:53.110 INFO 2860 --- [ main] c.n.d.provider.DiscoveryJerseyProvider : Using XML decoding codec XStreamXml
+2021-02-10 14:03:53.263 INFO 2860 --- [ main] c.n.d.s.r.aws.ConfigClusterResolver : Resolving eureka endpoints via configuration
+2021-02-10 14:03:53.546 INFO 2860 --- [ main] com.netflix.discovery.DiscoveryClient : Disable delta property : false
+2021-02-10 14:03:53.546 INFO 2860 --- [ main] com.netflix.discovery.DiscoveryClient : Single vip registry refresh property : null
+2021-02-10 14:03:53.547 INFO 2860 --- [ main] com.netflix.discovery.DiscoveryClient : Force full registry fetch : false
+2021-02-10 14:03:53.547 INFO 2860 --- [ main] com.netflix.discovery.DiscoveryClient : Application is null : false
+2021-02-10 14:03:53.547 INFO 2860 --- [ main] com.netflix.discovery.DiscoveryClient : Registered Applications size is zero : true
+2021-02-10 14:03:53.547 INFO 2860 --- [ main] com.netflix.discovery.DiscoveryClient : Application version is -1: true
+2021-02-10 14:03:53.547 INFO 2860 --- [ main] com.netflix.discovery.DiscoveryClient : Getting all instance registry info from the eureka server
+2021-02-10 14:03:53.754 INFO 2860 --- [ main] com.netflix.discovery.DiscoveryClient : The response status is 200
+2021-02-10 14:03:53.756 INFO 2860 --- [ main] com.netflix.discovery.DiscoveryClient : Starting heartbeat executor: renew interval is: 30
+2021-02-10 14:03:53.758 INFO 2860 --- [ main] c.n.discovery.InstanceInfoReplicator : InstanceInfoReplicator onDemand update allowed rate per min is 4
+2021-02-10 14:03:53.761 INFO 2860 --- [ main] com.netflix.discovery.DiscoveryClient : Discovery Client initialized at timestamp 1612937033760 with initial instances count: 0
+2021-02-10 14:03:53.762 INFO 2860 --- [ main] o.s.c.n.e.s.EurekaServiceRegistry : Registering application SPRINGCLOUD-TEST with eureka with status UP
+2021-02-10 14:03:53.763 INFO 2860 --- [ main] com.netflix.discovery.DiscoveryClient : Saw local status change event StatusChangeEvent [timestamp=1612937033763, current=UP, previous=STARTING]
+2021-02-10 14:03:53.765 INFO 2860 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient : DiscoveryClient_SPRINGCLOUD-TEST/host.docker.internal:springCloud-test:8884: registering service...
+2021-02-10 14:03:53.805 INFO 2860 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8884 (http) with context path ''
+2021-02-10 14:03:53.807 INFO 2860 --- [ main] .s.c.n.e.s.EurekaAutoServiceRegistration : Updating port to 8884
+2021-02-10 14:03:53.837 INFO 2860 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient : DiscoveryClient_SPRINGCLOUD-TEST/host.docker.internal:springCloud-test:8884 - registration status: 204
+2021-02-10 14:03:54.231 INFO 2860 --- [ main] o.d.s.e.s.ShenyuTestSpringCloudApplication : Started ShenyuTestSpringCloudApplication in 6.338 seconds (JVM running for 7.361)
+```
+
+## Test
+
+The `shenyu-examples-springcloud` project will automatically register interface methods annotated with `@ShenyuSpringCloudClient` in the Apache ShenYu gateway after successful startup.
+
+Open PluginList -> rpc proxy -> springCloud to see the list of plugin rule configurations:
+
+
+
+Use PostMan to simulate HTTP to request your SpringCloud service:
+
+
+
+Use IDEA HTTP Client Plugin to simulate HTTP to request your SpringCloud service[local:no Shenyu proxy]:
+
+
+
+Use IDEA HTTP Client Plugin to simulate HTTP to request your SpringCloud service[Shenyu proxy]:
+
+
diff --git a/versioned_docs/version-2.6.1/quick-start/quick-start-tars.md b/versioned_docs/version-2.6.1/quick-start/quick-start-tars.md
new file mode 100644
index 00000000000..5302f435ae6
--- /dev/null
+++ b/versioned_docs/version-2.6.1/quick-start/quick-start-tars.md
@@ -0,0 +1,118 @@
+---
+title: Quick start with Tars
+description: Quick start with Tars
+---
+
+This document introduces how to quickly access the Apache ShenYu Gateway using Tars. You can get the code example of this document by clicking [here](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-tars) .
+
+## Environment to prepare
+
+
+Please refer to the deployment to select a way to start shenyu-admin. For example, start the Apache ShenYu gateway management system through [local deployment](../deployment/deployment-local) .
+
+After successful startup, you need to open the Sofa plugin on in the BasicConfig `->` Plugin.
+
+
+
+If you are a startup gateway by means of source, can be directly run the ShenyuBootstrapApplication of shenyu-bootstrap module.
+
+> Note: Before starting, make sure the gateway has added dependencies.
+
+
+
+`shenyu-bootstrap` need to import tars dependencies:
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-tars
+ ${project.version}
+
+
+
+ com.tencent.tars
+ tars-client
+ 1.7.2
+
+```
+
+## Run the shenyu-examples-tars project
+
+Download [shenyu-examples-tars](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-tars) .
+
+Modify `host` in `application.yml` to be your local IP
+
+Modify config `src/main/resources/ShenyuExampleServer.ShenyuExampleApp.config.conf`:
+
+* It is recommended to make clear the meaning of the main configuration items of config, [refer to the development guide](https://github.com/TarsCloud/TarsJava/blob/master/docs/tars_java_user_guide.md)
+* bind IP in config should pay attention to providing cost machine
+* local=..., Indicates the open port that the native machine connects to the tarsnode. If there is no tarsnode, this configuration can be dropped
+* `locator`: Indicates the address (frame address) of the main control center, which is used to obtain the IP list according to the service name, If Registry is not required to locate the service, this configuration can be dropped
+* `node=tars.tarsnode.ServerObj@xxxx`, Indicates the address of the connected tarsnode. If there is no tarsnode locally, this configuration can be removed
+
+More config configuration instructions, Please refer to [TARS Official Documentation](https://github.com/TarsCloud/TarsJava/blob/master/docs/tars_java_user_guide.md)
+
+Execute the `org.apache.shenyu.examples.tars.ShenyuTestTarsApplication` main method to start project.
+
+**Note:** The `configuration file address` needs to be specified in the startup command when the service starts **-Dconfig=xxx/ShenyuExampleServer.ShenyuExampleApp.config.conf**
+
+If the `-Dconfig` parameter is not added, the configuration may throw the following exceptions:
+
+```text
+com.qq.tars.server.config.ConfigurationException: error occurred on load server config
+ at com.qq.tars.server.config.ConfigurationManager.loadServerConfig(ConfigurationManager.java:113)
+ at com.qq.tars.server.config.ConfigurationManager.init(ConfigurationManager.java:57)
+ at com.qq.tars.server.core.Server.loadServerConfig(Server.java:90)
+ at com.qq.tars.server.core.Server.(Server.java:42)
+ at com.qq.tars.server.core.Server.(Server.java:38)
+ at com.qq.tars.spring.bean.PropertiesListener.onApplicationEvent(PropertiesListener.java:37)
+ at com.qq.tars.spring.bean.PropertiesListener.onApplicationEvent(PropertiesListener.java:31)
+ at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
+ at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
+ at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
+ at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:127)
+ at org.springframework.boot.context.event.EventPublishingRunListener.environmentPrepared(EventPublishingRunListener.java:76)
+ at org.springframework.boot.SpringApplicationRunListeners.environmentPrepared(SpringApplicationRunListeners.java:53)
+ at org.springframework.boot.SpringApplication.prepareEnvironment(SpringApplication.java:345)
+ at org.springframework.boot.SpringApplication.run(SpringApplication.java:308)
+ at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226)
+ at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215)
+ at org.apache.shenyu.examples.tars.ShenyuTestTarsApplication.main(ShenyuTestTarsApplication.java:38)
+Caused by: java.lang.NullPointerException
+ at java.io.FileInputStream.(FileInputStream.java:130)
+ at java.io.FileInputStream.(FileInputStream.java:93)
+ at com.qq.tars.common.util.Config.parseFile(Config.java:211)
+ at com.qq.tars.server.config.ConfigurationManager.loadServerConfig(ConfigurationManager.java:63)
+ ... 17 more
+The exception occurred at load server config
+```
+
+The following log appears when the startup is successful:
+
+```shell
+[SERVER] server starting at tcp -h 127.0.0.1 -p 21715 -t 60000...
+[SERVER] server started at tcp -h 127.0.0.1 -p 21715 -t 60000...
+[SERVER] server starting at tcp -h 127.0.0.1 -p 21714 -t 3000...
+[SERVER] server started at tcp -h 127.0.0.1 -p 21714 -t 3000...
+[SERVER] The application started successfully.
+The session manager service started...
+[SERVER] server is ready...
+2021-02-09 13:28:24.643 INFO 16016 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 55290 (http) with context path ''
+2021-02-09 13:28:24.645 INFO 16016 --- [ main] o.d.s.e.tars.ShenyuTestTarsApplication : Started ShenyuTestTarsApplication in 4.232 seconds (JVM running for 5.1)
+2021-02-09 13:28:24.828 INFO 16016 --- [pool-2-thread-1] o.d.s.client.common.utils.RegisterUtils : tars client register success: {"appName":"127.0.0.1:21715","contextPath":"/tars","path":"/tars/helloInt","pathDesc":"","rpcType":"tars","serviceName":"ShenyuExampleServer.ShenyuExampleApp.HelloObj","methodName":"helloInt","ruleName":"/tars/helloInt","parameterTypes":"int,java.lang.String","rpcExt":"{\"methodInfo\":[{\"methodName\":\"helloInt\",\"params\":[{},{}],\"returnType\":\"java.lang.Integer\"},{\"methodName\":\"hello\",\"params\":[{},{}],\"returnType\":\"java.lang.String\"}]}","enabled":true}
+2021-02-09 13:28:24.837 INFO 16016 --- [pool-2-thread-1] o.d.s.client.common.utils.RegisterUtils : tars client register success: {"appName":"127.0.0.1:21715","contextPath":"/tars","path":"/tars/hello","pathDesc":"","rpcType":"tars","serviceName":"ShenyuExampleServer.ShenyuExampleApp.HelloObj","methodName":"hello","ruleName":"/tars/hello","parameterTypes":"int,java.lang.String","rpcExt":"{\"methodInfo\":[{\"methodName\":\"helloInt\",\"params\":[{},{}],\"returnType\":\"java.lang.Integer\"},{\"methodName\":\"hello\",\"params\":[{},{}],\"returnType\":\"java.lang.String\"}]}","enabled":true}
+```
+
+
+## Test
+
+The `shenyu-examples-tars` project will automatically register interface methods annotated with `@ShenyuTarsClient` in the Apache ShenYu gateway after successful startup.
+
+Open PluginList -> rpc proxy -> tars to see the list of plugin rule configurations:
+
+
+
+Use PostMan to simulate HTTP to request your tars service:
+
+
+
diff --git a/versioned_docs/version-2.6.1/quick-start/quick-start-websocket.md b/versioned_docs/version-2.6.1/quick-start/quick-start-websocket.md
new file mode 100644
index 00000000000..754086e8c99
--- /dev/null
+++ b/versioned_docs/version-2.6.1/quick-start/quick-start-websocket.md
@@ -0,0 +1,152 @@
+---
+title: Quick start with Websocket
+description: Websocket quick start
+---
+
+This document introduces how to quickly access the Apache ShenYu gateway using Websocket.
+
+
+## Environment to prepare
+
+> Refer to [local deployment](../deployment/deployment-local) to deploy the Shenyu gateway.
+
+1. Deploy the `shenyu-admin` service.
+
+- After successful launch, you need to set the `Websocket` plugin to be enabled in the page's basic configuration `->`Plugin Management.
+
+
+
+2. Deploy the `shenyu-bootstrap` service.
+- After starting, `shenyu-bootstrap` will synchronize the data via the `websocket` protocol according to the address configured in `shenyu.sync.websocket.url`.
+
+> Note: Before starting, make sure that the gateway has introduced the relevant dependency, which is introduced by default.
+
+Import the gateway proxy plugin for `Websocket` and add the following dependencies to the gateway's `pom.xml` file.
+
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-websocket
+ ${project.version}
+
+```
+
+
+
+## Run the shenyu-examples-websocket project
+
+1. Download [shenyu-examples-websocket](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-websocket/shenyu-example-spring-annotation-websocket) (`native-websocket` and `reactive-websocket` can refer to the subprojects under [shenyu-examples-websocket](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-websocket)).
+
+2. Run main method of `org.apache.shenyu.examples.websocket.TestAnnotationWebsocketApplication` to start this project.
+- The examples project will synchronize the websocket service information to `shenyu-admin` via the `http` protocol according to the address configured in `shenyu.register.serverLists`, and then to `shenyu-bootstrap` by `shenyu-admin`.
+
+log info as follows after starting:
+
+```shell
+2022-08-09 23:37:34.994 INFO 61398 --- [or_consumer_-21] o.a.s.r.client.http.utils.RegisterUtils : metadata client register success: {"appName":"ws-annotation","contextPath":"/ws-annotation","path":"/ws-annotation/myWs","rpcType":"websocket","ruleName":"/ws-annotation/myWs","enabled":true,"pluginNames":[],"registerMetaData":false,"timeMillis":1660059454701}
+2022-08-09 23:37:35.019 INFO 61398 --- [or_consumer_-18] o.a.s.r.client.http.utils.RegisterUtils : uri client register success: {"protocol":"ws://","appName":"ws-annotation","contextPath":"/ws-annotation","rpcType":"websocket","host":"192.168.1.3","port":8001}
+```
+
+
+
+## Test
+
+1. The `shenyu-examples-websocket` project will automatically register the interface methods annotated with `@ShenyuSpringWebSocketClient` to the gateway and add selectors and rules after successful start, you can see the information of `shenyu-examples-websocket` service registration by visiting `shenyu-admin` page -> PluginList -> Proxy -> Websocket to see the `shenyu-examples-websocket` service registration information, if not, you can refer to [Websocket plugin](../plugin-center/proxy/websocket-plugin.md) to add the configuration manually.
+
+
+
+2. The following test code (see attachment) simulates the request method of the `Websocket` protocol to request your `Websocket` service.
+
+
+
+
+
+## Annexes
+
+**websocket debugging code**
+
+- Create a file called websocket.html and copy the following code into the file.
+- Open websocket.html with Chrome.
+
+```html
+
+
+
+
+ Shenyu WebSocket Test
+
+
+
+
+
+
+
+
+
+
+
+
+```
diff --git a/versioned_docs/version-2.6.1/user-guide/_category_.json b/versioned_docs/version-2.6.1/user-guide/_category_.json
new file mode 100644
index 00000000000..2e41e63c016
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "User Guide",
+ "position": 5
+}
diff --git a/versioned_docs/version-2.6.1/user-guide/admin-usage/_category_.json b/versioned_docs/version-2.6.1/user-guide/admin-usage/_category_.json
new file mode 100644
index 00000000000..f0c5b1288f2
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/admin-usage/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Admin Usage",
+ "position": 1
+}
diff --git a/versioned_docs/version-2.6.1/user-guide/admin-usage/api-document.md b/versioned_docs/version-2.6.1/user-guide/admin-usage/api-document.md
new file mode 100644
index 00000000000..8fc5dee3a97
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/admin-usage/api-document.md
@@ -0,0 +1,86 @@
+---
+title: API Document Management
+keywords: ["api doc Document"]
+description: API document management
+---
+
+## 1. Design Notes
+
+When the front and back end are jointly debugged, it is usually necessary for the back end to give documents to detail the input and output of the interface;
+
+After the backend development is complete, you need to test whether the access gateway is successful.
+
+In order to reduce the sense of fragmentation and improve the user experience of front-end and back-end development, it is necessary to see the API documentation in shenyu-admin and test the API directly.
+
+## 2. How to use
+
+The brief introduce is as follows.
+- Back-end development produces API documents in shenyu-admin.
+> Three methods of `remotely pulling swagger`, `manual filling`, and `client registration` are already supported. From the perspective of functional integrity and user experience, `remotely pulling swagger` is currently recommended, and the latter two methods will be in Continuous function enhancement in later versions.
+- The frontend looks at the API documentation in shenyu-admin and starts development.
+> During joint debugging, developers (including front-end and backend) may use the testing function in shenyu-admin to request APIs directly.
+
+## 3. Set the global environment address
+
+In actual use, you may have multiple gateway addresses (such as production environment, test environment, or public network environment, intranet environment), you can manage them in `Apache ShenYu` Gateway Management System --> BasicConfig --> Dictionary, Set multiple gateway addresses.
+
+
+
+> DictionaryType: Fill in the value must be `apidocEnv`;
+>
+> DictionaryCode: The identifier of the gateway address has no actual meaning. It is recommended to use `ENV_LABEL_` as a prefix, such as `ENV_LABEL_OFFLINE`;
+>
+> DictionaryName: Indicates the gateway type, such as filling in `test environment`, `production environment`. This value will appear on the API documentation details page;
+>
+> DictionaryValue: Indicates the gateway address, such as http://127.0.0.1:9195. This value will appear on the API documentation details page;
+>
+> DictionaryDescribe: Give a brief description of what scenario the gateway address is used for. This value will appear on the API documentation details page;
+>
+> Sort: The numerical value determines the display order of the gateway address;
+>
+> Status: open or close。
+
+## 4. Support Multiple Ways to Aggregate API Documents
+
+### 4.1 Add API Document Manually
+
+Clicking the menu "Document -> API Document" to create api.
+
+##### Create Project
+
+If you have not created a project or you want to classify the new API into a new project, you need to create a project.
+
+
+
+##### Add API Documentation
+
+
+
+### 4.2 Remotely pull the swagger registration API Document.
+
+Automatically register API documentation by remotely pulling swager documentation. Please refer to [Remote pull swagger registration API document](../api-doc/swagger-apidoc.md)
+
+### 4.3 Shenyu Client Annotation Registration API Documentation
+
+Automatically register API documents through Shenyu client annotations. Please refer to [Client Registration API Documentation](../api-doc/shenyu-annotation-apidoc.md)
+> This method is recommended if you do not expect to view the full interface documentation details. When you choose this automatic registration method, please turn off the registration method of remote automatic pull swagger, otherwise there will be conflicts.
+
+## 5. Publish API
+
+If the API has never been published and the user has not used the shenyu-client, shenyu-admin will automatically expose the API described in the API document to the gateway.
+
+
+
+After clicking Save, you'll see that the registration data for the API is inserted below the selectors and rules. As shown below:
+
+
+
+## 6. Offline API(optional)
+
+> Special Note: After clicking Offline, the API will still be visible in the API document list, but it will be deleted from the proxy plug-in and metadata management list. Before you republish the API, the gateway will not proxy the API. When you pass through the gateway When requesting this API, an exception will be reported.
+
+
+
+## 7. API Debug
+
+
diff --git a/versioned_docs/version-2.6.1/user-guide/admin-usage/data-permission.md b/versioned_docs/version-2.6.1/user-guide/admin-usage/data-permission.md
new file mode 100644
index 00000000000..6619373e605
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/admin-usage/data-permission.md
@@ -0,0 +1,53 @@
+---
+title: Data Permission Management
+keywords: ["user data permission"]
+description: user data permission
+---
+## Design Notes
+
+In order to achieve the different selector / rule represented by the plugin managed by different business units, the need for the plugin selector / rule data security for the user to control
+When the user does not configure data permissions, it has all the data permissions, as long as the permissions are configured, the data permissions will be controlled. As shown in the following picture.
+
+
+
+
+## How to use
+
+The Brief introduce is as follows.
+- Users with administrative user resouce permissions (including the admin user) create a new user.
+- Users with administrative user data resouce permissions (including admin user) click `ConfigureDataPermission` to manage the user's data permissions.
+> Make sure the data exists in the plugin list before doing so. If not, you will have any data to configure.
+
+Now, let's look how to operation step by step:
+
+### Create User
+
+Clicking the menu "System Manage -> User" to create user, like this:
+
+
+### Edit Date
+
+#### Add Plugin Data
+
+Adding data in the plugin list, this article uses `divide` as an example, like:
+
+
+#### Configure Resource Permission
+
+Giving the `divide` plugin permission to the `default` role.
+
+
+The `default` role has none permissions.The user can't login who we set `default` role to. So we must edit the permissions.
+
+#### Configure Data Permission
+
+When we create the common users, we can edit data permissions by the `ConfigureDataPermission` button.
+
+
+
+The datas in this list are the same as the plugin list.
+
+## New User Login
+
+When the user login, he just can see the data given to him.
+
diff --git a/versioned_docs/version-2.6.1/user-guide/admin-usage/dictionary-management.md b/versioned_docs/version-2.6.1/user-guide/admin-usage/dictionary-management.md
new file mode 100644
index 00000000000..91b6989ebcf
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/admin-usage/dictionary-management.md
@@ -0,0 +1,32 @@
+---
+title: Dictionary Management
+keywords: ["dict"]
+description: dict management explanation
+---
+
+## Explanation
+
+This document will introduce the use of dictionary management in the Apache ShenYu background management system. Dictionary management is primarily used to maintain and manage common data dictionaries.
+
+Please refer to the `deployment` document, choose a way to start `shenyu-admin`. For example, [local deployment](../../deployment/deployment-local). After startup, visit `http://localhost:9095`, the default username and password are: `admin` and `123456` .
+
+The current usage scenario is in the [pluginHandle](./plugin-handle-explanation), when the data type is selected as the `dropdown`:
+
+
+
+In dictionary management, you can add dictionary types for other places:
+
+
+
+- DictionaryType: The field name used in the `pluginHandle` .
+- DictionaryCode: Identify dictionary data.
+- DictionaryName: The name of the `handle` field when adding plugins, selectors or rules.
+- DictionaryValue: The actual value of the dictionary data.
+- DictionaryDescribe: Description.
+- Sort: Dictionary data order.
+
+e.g. `degradeRuleGrade` is one of fields of Sentinel's `handle` json. When it adds rules, it automatically looks up all the general dictionaries of `type='degradeRuleGrade'` in the `shenyu_dict` table as a select-box when you edit the General rules field.
+
+
+
+
diff --git a/versioned_docs/version-2.6.1/user-guide/admin-usage/plugin-handle-explanation.md b/versioned_docs/version-2.6.1/user-guide/admin-usage/plugin-handle-explanation.md
new file mode 100644
index 00000000000..82eb4af0c95
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/admin-usage/plugin-handle-explanation.md
@@ -0,0 +1,51 @@
+---
+title: Plugin Config
+keywords: ["plugin"]
+description: plugin handle explanation
+---
+
+## Explanation
+
+This document will introduce the use of plugins in the `shenyu-admin` , including plugin management and plugin handle management.
+
+Please refer to the `deployment` document, choose a way to start `shenyu-admin`. For example, [local deployment](../../deployment/deployment-local). After startup, visit `http://localhost:9095`, the default username and password are: `admin` and `123456` .
+
+## Plugin management
+
+In the plugin management, you can manage all plugins in a unified manner, such as turning off or turning on plugins:
+
+
+
+You can also set configuration information for some plugins, such as setting a registry for `Dubbo` plugin:
+
+
+
+## Plugin handle management
+
+In plugin handle management, you can add `handle` fields to plugin, selector, and rule.
+
+For example, add a string type field `path` and a digital type field `timeout` to the rule list of the `SpringCloud` plugin.
+
+1. add/edit the `handle` field in the `shenyu-admin`-> BasicConfig -> PluginHandle :
+
+
+
+2. Fill in the field information:
+
+
+
+- PluginName: Drop down to select which plugin needs to add the `handle` field.
+- Field: Add the name of the field.
+- Describe: Field description.
+- DataType: Field data type.
+ - If the `DropDown` is selected, the drop-down selection of the input box on the rule addition page is to go to the dictionary table to find all the available options through the field name to select, so you need to config the selection in [Dictionary Management](./dictionary-management).
+- FieldType: This field belongs to selector, rule or plugin.
+- Sort: Sequence number.
+- Required: Is this field required.
+- DefaultValue: Specify a default value for this field.
+- Placeholder: The message that appears when the user fills in the field.
+- Rule (RegExp): The verification rule when the user fills in the field。
+
+3. When adding a rule in the PluginList -> rpc proxy -> `SpringCloud` -> you can enter `path` and `timeout` :
+
+
diff --git a/versioned_docs/version-2.6.1/user-guide/admin-usage/role-management.md b/versioned_docs/version-2.6.1/user-guide/admin-usage/role-management.md
new file mode 100644
index 00000000000..e3fa8f40b0e
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/admin-usage/role-management.md
@@ -0,0 +1,45 @@
+---
+title: Role Management
+keywords: ["user role resource"]
+description: user role resource permission management
+---
+
+This article focuses on the `admin` console to manage `admin` operation permissions through user-associated roles, roles that give permissions to resources such as menus and buttons.
+
+
+## Resource
+
+Add Menus and Buttons Resource in "System Manage >> Resouce".
+
+
+
+The admin user shows all menus and buttons of the `Shenyu` gateway. If you need to customize adding and removing, add the menu first and under the corresponding menu, add the button. Edit the menu by clicking on the small edit icon on the right side of the menu.
+
+
+## Role
+
+You can associate roles and resource permissions through the menu bar "System Administration >> Role Management". By default, two roles are created, one for super administrator and one for normal user. The super administrator is the admin user, which cannot be changed, and the normal user role can change its resource properties. By editing the corresponding role, you can give the role the appropriate menu and button permissions.
+
+
+## User
+
+You can manage the users logged into admin through the menu bar "System Administration >> User Management". The default user is admin, which has all menu and data permissions, cannot be changed or deleted, and can only change password or username.
+You can add a user by pressing the "Add Data" button. The user role is selected to manage the menu and button permissions that the user sees after logging in. When a user selects more than one role, the maximum set of all roles is taken together. After changing a user's role permissions, users who are already logged in can simply refresh the page to get the changed permissions.
+
+The following is an example of how the new user's permissions.
+
+- editor default user role permission
+
+
+
+- Add new roles and give the appropriate resource permissions
+
+
+
+- Create new users and give them the appropriate roles
+
+
+
+- User login to view their menu and button permissions
+
+
diff --git a/versioned_docs/version-2.6.1/user-guide/admin-usage/selector-and-rule.md b/versioned_docs/version-2.6.1/user-guide/admin-usage/selector-and-rule.md
new file mode 100644
index 00000000000..e2ad2e058eb
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/admin-usage/selector-and-rule.md
@@ -0,0 +1,336 @@
+---
+title: Selector And Rule Config
+keywords: ["Selector", "Rule"]
+description: detailed explanation of selector and rule
+---
+
+## Features
+
+This document will introduce the use of selectors and rules in the Apache ShenYu background management system. For the concept and design of selectors and rules, please refer to `Flow Control`.
+
+
+Please refer to the `deployment` document, choose a way to start `shenyu-admin`. For example, [local deployment](../../deployment/deployment-local). After startup, visit `http://localhost:9095`, the default username and password are: `admin` and `123456` .
+
+## Selector
+
+All plugins are displayed in the PluginList, and selectors and rules can be added to each plugin:
+
+
+
+For example, add a selector to the `divide` plugin:
+
+
+
+* selector detailed explanation：
+
+ * Name: create your selector with a distinguish name.
+ * Type: Choose request matching strategy.
+ * `custom`: Only handle requests that meet the following matching conditions.
+ * `full`: Handle all requests.
+ * MatchType: Condition combination type.
+ * `and`： Need to meet all conditions.
+ * `or`: Meet any of the conditions.
+ * Conditions：
+ * uri: filter request with uri.
+ * header: filter request with request header.
+ * query: filter request with query string.
+ * ip: filter request with your real ip.
+ * host: filter request with your real host.
+ * post: not recommend to use.
+ * cookie: filter request with cookie.
+ * req_method: filter request with request method.
+ * condition match:
+ * match : fuzzy string matching，recommend to combine with uri，support path-matching.（/test/**).
+ * = : matches only if they are equal.
+ * regEx : regex matching，match characters in regex expression.
+ * contains: when it contains the specified value, it matches.
+ * TimeBefore: before the specified time.
+ * TimeAfter: after the specified time.
+ * exclude: the inverse of the method of `match`.
+ * startsWith: when its prefix is equal to the specified value, it matches. In certain scenarios, `match` can be replaced (such as `/test/` instead of `/test/**`) for better performance.
+ * endsWith: when its suffix is equal to the specified value, it matches.
+ * pathPattern: it's an optimized version of `match`, which has better performance than `match`, but does not support writing `**` in the middle of the path (such as `/api/**/xxx`).
+ * Continued: whether the subsequent selector is still executed.
+ * PrintLogs: it will print the matching log with the open option enabled.
+ * Enable: whether to enable the plugin.
+ * Order：the smaller will have high priority to execute among multi-selectors.
+ * Handler: The operation when the request matches the selector.
+* the above picture means: when the prefix of the request uri is `/http`, it will redirect to this service `127.0.0.1:8080`.
+* selector advice : combine `uri` condition and `startsWith` prefix（/contextPath/）as the first request filter.
+* selector(the same for rule) match condition fuzzy string matching rule:
+ * `?` matches one character
+ * `*` matches zero or more characters
+ * `**` matches zero or more directories in a path
+
+## Rule
+
+
+
+* when the request was passed by the selector, then it will be processed by the rule, the final filter.
+* rule is the final confirmation about how to execute request logically.
+* rule detailed explanation：
+ * Name：create your rule with a distinguish name.
+
+ * MatchType: you can combine these conditions with 'and' , 'or' operators.
+
+ * Conditions：
+
+ * uri: filter request with uri.
+ * header: filter request with request header.
+ * query: filter request with query string.
+ * ip: filter request with your real ip.
+ * host: filter request with your real host.
+ * post: not recommend to use.
+ * cookie: filter request with cookie.
+ * req_method: filter request with request method.
+
+ * condition match:
+ * match : fuzzy string matching，recommend to combine with uri，support path-matching.（/test/**).
+ * = : matches only if they are equal.
+ * regEx : regex matching，match characters in regex expression.
+ * contains: when it contains the specified value, it matches.
+ * TimeBefore: before the specified time.
+ * TimeAfter: after the specified time.
+ * exclude: Same function as `match`, flow selection is opposite.
+ * startsWith: when its prefix is equal to the specified value, it matches. In certain scenarios, `match` can be replaced (such as `/test/` instead of `/test/**`) for better performance.
+ * endsWith: when its suffix is equal to the specified value, it matches.
+ * pathPattern: it's an optimized version of `match`, which has better performance than `match`, but does not support writing `**` in the middle of the path (such as `/api/**/xxx`).
+
+ * PrintLogs: it will print the matching log with the open option enabled.
+
+ * Enable: whether to enable the plugin.
+
+ * Order：the smaller will have high priority to execute among multi-rules.
+
+ * handle: The operation when the request matches the rule.
+* above picture means: when the request `uri` equals to `/http/order/save`, it will execute based on this rule，load strategy is `random`.
+* rule advice: combine `uri` condition with `match` the real `uri path` condition as the final filter.
+* combine selector means ：when the request `uri` is `/http/order/save`, it will be redicted to `127.0.0.1:8080` by `random` method.
+
+
+## Match Strategy
+
+Matching mode refers to the matching mode between multiple conditions when a selector or rule is matched. Currently, `and` and `or` are supported.
+
+
+* `and`
+
+ `and` indicates that a selector or rule can be matched only if more than one condition is met.
+
+ The example below shows that a request must meet both the condition `uri = /http/order/findById` and the condition `id = 100` to match this rule.
+
+ For example, a real request `http://localhost:9195/http/order/findById?id=100` satisfies both conditions, this rule can be matched.
+
+
+
+
+
+* `or`
+
+ `or` indicates that one of the conditions matches a selector or rule.
+
+ The example below shows that a request matches this rule if it meets either the condition `uri = /http/order/findById` or the condition `id = 100`.
+
+ For example, a real request `http://localhost:9195/http/order/findById?id=99` satisfies the first condition `uri = /http/order/findById`, so it can also match this rule.
+
+
+
+
+
+## Condition Parameter Data
+
+Conditional parameter Settings in selectors and rules are explained again. Suppose the following is a request header for an `Http` request:
+
+```shell
+GET http://localhost:9195/http/order/findById?id=100
+Accept: application/json
+Cookie: shenyu=shenyu_cookie
+MyHeader: custom-header
+```
+
+In `ShenYu` you can set different conditional parameters to get real data from the request information.
+
+- If the condition parameter is `uri`, then the actual data retrieved is `/http/order/findById`;
+- If the condition parameter is `header`, the field name is `MyHeader`, then the actual data retrieved is `custom-header`;
+- If the condition parameter is `query`, the field name is `id`, then the actual data retrieved is `100`;
+- If the condition parameter is `ip`, then the actual data retrieved is `0:0:0:0:0:0:0:1`;
+- If the condition parameter is `host`, then the actual data retrieved is `0:0:0:0:0:0:0:1`;
+- If the condition parameter is `post`, the field name is `contextPath`, then the actual data retrieved is `/http`;
+- If the condition parameter is `cookie`, the field name is `shenyu`, then the actual data retrieved is `shenyu_cookie`;
+- If the condition parameter is `req_method`, then the actual data retrieved is `GET`;
+
+* `uri`(recommended)
+
+ * `uri` matches are based on the `uri` in the path you requested, and there is almost no change in the front end when accessing the gateway.
+
+ * When using `match`, the principle is the same as `SpringMVC` fuzzy matching.
+
+ * In selectors, it is recommended to use prefixes in `URI` for matching, while in rules, specific paths are used for matching.
+
+ * When using this matching method, fill in the value of the matching field, as shown in the figure `/http/**`.
+
+ 
+
+* `header`
+
+ * The `header` is matched against the field values in your `http` request header.
+
+ * When using this matching method, you need to fill in the field name and field value. The examples in the figure are `MyHeader` and `custom-header` respectively
+
+ 
+
+* `query`
+
+ * This matches the query parameters in your `uri`, such as `/test?id=1`, then the matching method can be selected.
+
+ * When using this matching method, you need to fill in the field name and field value. The examples in the figure are `id` and 1 respectively.
+
+ 
+
+* `ip`
+
+ * This is matched against the `http` caller's `ip`.
+
+ * Especially in waf plugin, if an `ip` address is found to be attacked, you can add a matching condition, fill in the `ip`, deny the `ip` access.
+
+ * If you use nginx proxy before ShenYu, you can get the right ip with refering to [parsing-ip-and-host](../../developer/custom-parsing-ip-and-host)
+
+ * When using this matching method, fill in the value of the matching field, as shown in the example `192.168.236.75`.
+
+ 
+
+
+* `host`
+
+ * This is matched against the `http` caller's `host`.
+
+ * Especially in waf plugin, if an `host` address is found to be attacked, you can add a matching condition, fill in the `host`, deny the `host` access.
+
+ * If you use nginx proxy before ShenYu, you can get the right ip with refering to [parsing-ip-and-host](../../developer/custom-parsing-ip-and-host)
+
+ * When using this matching method, fill in the value of the matching field, as shown in the example `localhost`.
+
+ 
+
+* `post`
+
+ * To get condition parameters from the request context(`org.apache.shenyu.plugin.api.context.ShenyuContext`), reflection is required to get the value of the field, which is not recommended.
+
+ * When using this matching method, the field name and value need to be specified. The examples in the figure are `contextPath` and `/http` respectively.
+
+ 
+
+
+* `cookie`
+
+ * This is matched against the `Cookie` in the `http` caller's request header as a condition parameter.
+
+ * When using this matching method, you need to fill in the field name and field value. The examples in the figure are `shenyu` and `shenyu_cookie` respectively.
+
+ 
+
+* `req_method`
+
+ * This matches the request form of the `http` caller, such as `GET`, `POST`, etc.
+
+ * When using this matching method, fill in the value of the matching field, as shown in the example `GET`.
+
+ 
+
+For a more in-depth understanding of condition parameter fetching, read the source code, package name is `org.apache.shenyu.plugin.base.condition.data`:
+
+|Condition Parameter | Class |
+|:------------------------ |:----- |
+|`uri` |`URIParameterData` |
+|`header` |`HeaderParameterData` |
+|`query` |`QueryParameterData` |
+|`ip` |`IpParameterData` |
+|`host` |`HostParameterData` |
+|`post` |`PostParameterData` |
+|`cookie` |`CookieParameterData` |
+|`req_method` |`RequestMethodParameterData` |
+
+
+## Condition Match Strategy
+
+Condition parameters allow you to retrieve the actual data of the request. How the real data matches the conditional data preset by the selector or rule is realized through the condition match strategy.
+
+
+* `match`
+
+ `match` supports fuzzy matching (`/**`). Request `/http/order/findById` will match if your selector condition is set as follows.
+
+ 
+
+* `=`
+
+ `=` means that the requested real data is equal to the preset condition data. If your selector condition is set to request uri equal to `/http/order/findById`, then request`/http/order/findById?id=1` can match it.
+
+ 
+
+* `regex`
+
+ `regex` means that the requested real data can meet the preset condition of the regular expression to match successfully. Suppose your rule conditions are sets as follows: the request parameter contains an `id` and is a three-digit number. So request `/http/order/findById?id=900` will match.
+
+ 
+
+* `contains`
+
+ `contains` means that the requested real data contains the default condition data. Suppose your rule condition is set as follows: request uri contains `findById`. Request `/http/order/findById?id=1` will match.
+
+ 
+
+* `TimeBefore`
+
+ `TimeBefore` indicates that the request time will be matched before the preset condition time. Suppose your rule conditions are sets as follows: request parameters contain `date` and `date` is less than `2021-09-26 06:12:10`. Request `/http/order/findById?id=100&date=2021-09-22 06:12:10` will match.
+
+ 
+
+* `TimeAfter`
+
+ `TimeAfter` indicates that the request time will be matched before the preset condition time. Suppose your rule conditions are sets as follows: request parameters contain `date` and `date` is greater than `2021-09-26 06:12:10`. Request `/http/order/findById?id=100&date=2021-09-22 06:12:10` will match.
+
+ 
+
+* `exclude`
+
+ `exclude` is the inverse of the method of `match`, and some functions of `match` are also available, but it is a matching filter. If your selector condition is set as follows, the request `/http/order/findById` will filter this.
+
+ 
+
+* `startsWith`
+
+ `startsWith` indicates that the prefix of the requested real data is equal to the preset condition data. Suppose your rule conditions are sets as follows: the prefix in the request `uri` is equal to `/http/`, the request `/http/order/findById?id=1` can be matched.
+
+ 
+
+* `endsWith`
+
+ `endsWith` indicates that the suffix of the requested real data is equal to the preset condition data. Suppose your rule conditions are sets as follows: request `uri` suffix equals `Id`. Then the request `/http/order/findById?id=1` can be matched.
+
+ 
+
+* `pathPattern`
+
+ Like `match`, `pathPattern` supports fuzzy matching (`/**`). If your rule conditions are sets as follows, then the request `/http/order/findById` can be matched;
+
+ Notice: writing `**` in the middle of the path (such as `/api/**/xxx`) is not supported!
+
+ 
+
+If you want to further understand conditions matching strategy, please read the source code, the package name is `org.apache.shenyu.plugin.base.condition.judge`:
+
+| Match Strategy | Class |
+|:---------------|:----- |
+| `match` |`MatchPredicateJudge` |
+| `=` |`EqualsPredicateJudge` |
+| `regex` |`RegexPredicateJudge` |
+| `contains` |`ContainsPredicateJudge` |
+| `TimeBefore` |`TimerBeforePredicateJudge` |
+| `TimeAfter` |`TimerAfterPredicateJudge` |
+| `exclude` |`ExcludePredicateJudge` |
+| `startsWith` |`StartsWithPredicateJudge` |
+| `endsWith` |`EndsWithPredicateJudge` |
+| `pathPattern` |`PathPatternPredicateJudge` |
+
+The examples in this article illustrate the use of selectors and rules. The Settings of specific conditions need to be selected according to actual conditions.
diff --git a/versioned_docs/version-2.6.1/user-guide/api-doc/_category_.json b/versioned_docs/version-2.6.1/user-guide/api-doc/_category_.json
new file mode 100644
index 00000000000..ae4f3bab406
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/api-doc/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "API Document Aggregation",
+ "position": 6
+}
diff --git a/versioned_docs/version-2.6.1/user-guide/api-doc/shenyu-annotation-apidoc.md b/versioned_docs/version-2.6.1/user-guide/api-doc/shenyu-annotation-apidoc.md
new file mode 100644
index 00000000000..5343291aa1f
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/api-doc/shenyu-annotation-apidoc.md
@@ -0,0 +1,38 @@
+---
+title: The client registers the API documentation
+keywords: ["api doc register"]
+description: The client registers the API documentation
+---
+
+This article describes how to expose the `API documentation` to the `Apache ShenYu` gateway.
+
+Before accessing, please start `shenyu-admin` correctly.
+
+## Export API Documentation to shenyu-admin
+
+You can refer to any of the example codes below [shenyu-examples](https://github.com/apache/shenyu/tree/master/shenyu-examples).
+
+The only thing you need to do is to add `@ApiModule` and `@ApiDoc` annotations to your service, here is an example from `shenyu-examples-http`:
+
+```java
+@RestController
+@RequestMapping("/order")
+@ShenyuSpringMvcClient("/order")
+@ApiModule(value = "order")
+public class OrderController {
+
+ @GetMapping("/findById")
+ @ShenyuSpringMvcClient("/findById")
+ @ApiDoc(desc = "findById")
+ public OrderDTO findById(@RequestParam("id") final String id) {
+ return build(id, "hello world findById");
+ }
+
+ private OrderDTO build(final String id, final String name) {
+ OrderDTO orderDTO = new OrderDTO();
+ orderDTO.setId(id);
+ orderDTO.setName(name);
+ return orderDTO;
+ }
+}
+```
diff --git a/versioned_docs/version-2.6.1/user-guide/api-doc/swagger-apidoc.md b/versioned_docs/version-2.6.1/user-guide/api-doc/swagger-apidoc.md
new file mode 100644
index 00000000000..2c9d17a0efb
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/api-doc/swagger-apidoc.md
@@ -0,0 +1,57 @@
+---
+title: Pull the swagger registration API document
+keywords: ["swagger api Interface Document Aggregation"]
+description: Remotely pull swagger registration API documentation
+---
+
+This article introduces how to aggregate the `Swagger API documentation` of each backend microservice to the `Apache ShenYu` gateway management system.
+
+## 1. Description
+
+Remotely pull swagger documents, currently only supports swagger2.0, and only supports Divide and SpringCloud proxy plug-ins.
+
+## 2. Environment Preparation
+
+### 2.1 Run `shenyu-admin`
+
+Please refer to the `deployment` document, choose a way to run `shenyu-admin`.
+
+### 2.2 Enable the global switch for remotely pulling swagger documents.
+
+It is enabled by default. In the `Apache ShenYu` gateway management system --> BasicConfig --> Dictionary, find the data whose DictionaryType is `apidoc`, and modify the dictionary value: `true`.
+> 【Notice】DictionaryValue: `true` means the switch is on, `false` means it is off. If it is closed, `shenyu-admin` will not automatically pull the swagger documents of each microservice.
+
+
+
+## 3. Run the Sample Project
+
+3.1. Download [shenyu-examples-http-swagger2](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http-swagger2)
+
+3.2. Run `org.apache.shenyu.examples.http.ShenyuTestSwaggerApplication` main method to start the project.
+
+The examples project will synchronize the service startup information to `shenyu-admin` through the Shenyu client annotation (such as `@ShenyuSpringMvcClient`) according to the address configured by `shenyu.register.serverLists`, and then trigger `shenyu-admin` to remotely pull the swagger document And complete the analysis, and finally aggregate to produce a new API document.
+
+## 4. Demonstration Effect
+
+### 4.1 List of API Documents
+
+In `Apache ShenYu` Gateway Management System --> Document --> API Document, you can see the aggregated API documents.
+
+
+
+### 4.2 API Details Effect
+
+
+
+## 5. How to Automatically Update API Documentation
+
+### 5.1 Restart Project
+
+As in the example above, an automatic update of the API docs is triggered by starting the project.
+
+### 5.2 Modify the startup time of the proxy plugin selector.
+
+In the PlugiList --> Proxy --> selector, find the target service, and then modify the startup time.
+> Note: The startup time of the new setting must not be earlier than the original startup time, otherwise the API document will not be automatically pulled and refreshed.
+
+
diff --git a/versioned_docs/version-2.6.1/user-guide/discovery/_category_.json b/versioned_docs/version-2.6.1/user-guide/discovery/_category_.json
new file mode 100644
index 00000000000..7c0997e003e
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/discovery/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Discovery",
+ "position": 4
+}
diff --git a/versioned_docs/version-2.6.1/user-guide/discovery/discovery-mode.md b/versioned_docs/version-2.6.1/user-guide/discovery/discovery-mode.md
new file mode 100644
index 00000000000..80837a074b5
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/discovery/discovery-mode.md
@@ -0,0 +1,422 @@
+---
+title: Discovery
+keywords: [ "Discovery" ]
+description: Discovery
+---
+
+# Discovery
+
+## 1. Overview
+
+### 1.1 Module Name
+
+Discovery
+
+### 1.2 Design
+
+- Module Design Diagram
+
+
+
+
+
+- Database Design
+
+
+
+
+### 1.3 Module Functionality
+
+The Discovery module endows the ShenYu Gateway with the ability to actively perceive and respond to changes in the list of services being proxied.
+By actively listening to the admin service of the Discovery Gateway, the ShenYu Gateway can promptly track changes in the services being proxied.
+This functionality is designed to be flexible and can be configured at either **the selector level or the plugin level**, as needed.
+Currently, plugins that have incorporated the Discovery feature include TCP, Divide, Websocket and gRPC plugins.
+
+
+### 1.4 Listening Mode
+
+LOCAL, ZOOKEEPER, NACOS, EUREKA, ETCD
+
+- LOCAL Mode: Primarily relies on manual maintenance of the upstream list and pushing it to the gateway.
+- ZOOKEEPER Mode: Monitors changes in ephemeral nodes under a specified node in ZooKeeper to obtain data.
+- NACOS Mode: Listens for changes in instances under a specified service name in Nacos to obtain data.
+- EUREKA Mode: Listens for changes in instances under a specified service name in Eureka to obtain data.
+- ETCD Mode: Obtains data by monitoring changes in key-value pairs under specified nodes in etcd.
+
+### 1.5 Scope of Effect
+
+- Plugin Level: Impacts the entire plugin,
+and all selectors under that plugin will default to the current listening mode.
+- Selector Level: Applies to the current selector,
+allowing different selectors under the same plugin to use different listening modes.
+
+## 2. Usage
+
+### 2.1 Plugin-Level Configuration
+
+#### 2.1.1 Service Discovery Configuration
+
+- In plugins that support the Discovery module (currently, only the TCP plugin supports plugin-level discovery
+configuration on the admin console page; other plugins can configure plugin-level discovery through shenyu-client,
+as described in the "Using Shenyu-client" section below), click on `Discovery Configuration`. In the popup form,
+select the desired listening mode and fill in the service discovery name, registration server URL, registry configuration parameters, etc.:
+
+
+
+
+
+
+#### 2.1.2 Usage within Selectors
+
+- To add a new selector, click on `Add Selector`. In the new selector page, you will notice that the `Type` field enforces the previously configured plugin-level listening mode,
+indicating that the added selector will also adopt the same configuration.
+At this point, simply input the desired `ListeningNode`:
+
+ 
+
+- The `Handler` here refers to ShenYu's specified JSON format for transmitting upstream registration data,
+as shown below:
+ - url: URL of the upstream
+ - protocol: communication protocol of the upstream
+ - status: status of the upstream node (0 for healthy, 1 for unhealthy)
+ - weight: Used for load balancing calculations
+
+
+ ```json
+ {
+ "url": "127.0.0.1::6379",
+ "protocol": "tcp",
+ "status": 0,
+ "weight": 10
+ }
+ ```
+
+- If your service alias does not match ShenYu's defined JSON format,
+you can perform alias mapping in `Handler`.
+For example, as shown in the above image,
+if you need to change `status` to "healthy" while keeping other keys unchanged,
+follow these steps: create a new alias, map `status` to `healthy`,
+and retain the original JSON keys' format.
+- Configure the remaining properties for the selector according to the specific plugin's documentation.
+
+### 2.2 Selector-Level Configuration
+
+- In plugins that support the Discovery module, click on `Add Selector`.
+In the `Discovery Config` tab, configure the fields such as type,
+listening node, server URL list, and registry properties.
+This configuration only applies to the current selector and must be reconfigured each time a new selector is added.
+
+
+
+- For the Divide, gRPC, and Websocket plugins,
+the `Import Background Discovery Config` function on the selector creation page
+allows you to import and use the backend configuration if the service connecting to the ShenYu Gateway
+was configured with shenyu-discovery-related properties (see usage with shenyu-client).
+As shown in the following image, click `Import Background Discovery Config` to view the backend configuration:
+
+
+
+- If you confirm the import, clicking the `Import` button in the backend configuration popup will automatically populate the form with the backend service discovery properties.
+At this point, you only need to configure the listening node:
+
+
+
+> **Note**: If you confirm importing the backend configuration,
+the backend service discovery properties will be automatically filled in the form and will continue to use the previous discovery object.
+In this case, modifying service discovery properties in the form will be ineffective, and the backend configuration will be retained.
+
+- If you choose the LOCAL mode, there is no need to connect to a registry, and users must manually maintain the upstream list.
+
+
+## 3. Configuration in Different Modes
+
+### 3.1 Local Mode
+
+- Local mode only supports configuration at the **selector level**.
+There is no need to connect to a registry, and users must manually maintain the upstream list.
+This list is an editable table. Click the `Edit` button for each row in the table to modify each parameter of the upstream:
+
+
+
+### 3.2 ZooKeeper/Nacos/Eureka/Etcd Modes
+
+- In the ZooKeeper/Nacos/Eureka/Etcd modes, service discovery configuration is supported at both the plugin level and the selector level.
+- For each registry property under these modes, taking ZooKeeper as an example, users can go to `shenyu-admin` --> `BasicConfig` --> `Dictionary`,
+search for the dictionary name "zookeeper", and edit the dictionary values corresponding to the default properties
+(**Note**: You cannot modify the dictionary type and dictionary name).
+- In these modes, the gateway dynamically retrieves service instance information from the registry. Additions, removals, modifications,
+and other changes to service instances will be displayed in real-time in the upstream list.
+
+
+
+## 4. Using Shenyu-client
+
+### 4.1 Introduction
+
+- To use Shenyu-client, you need to depend on the corresponding mode's registry middleware: ZooKeeper, Nacos, Etcd, Eureka.
+These modes can automatically detect service up and down events through ShenYu Admin.
+- Additionally, if you are using the local mode, you will need to manually maintain the upstream list.
+- For detailed instructions on using Shenyu-client, refer to the Shenyu-client module documentation.
+
+### 4.2 Local Mode Example
+
+#### 4.2.1 Using Shenyu-client
+
+- Shenyu-client defaults to the Local mode, so there is no need for any special discovery configuration.
+It will automatically register the current service.
+- For services that are automatically registered, you can manually add, modify,
+or delete them in the upstream list on the page:
+
+
+
+#### 4.2.2 Without Using Shenyu-client
+
+
+- If you are not using Shenyu-client, you can manually add, modify,
+or delete service information on the `Discovery Config` tab under `Add Selector`:
+
+
+
+- Configure other selector information:
+
+
+
+- Configure rules:
+
+
+
+- Test Connection
+
+```text
+curl http://localhost:9195/http/hello
+
+hello! I'm Shenyu-Gateway System. Welcome!%
+```
+
+### 4.2 Zookeeper Mode Example
+
+(Taking the Divide plugin as an example)
+
+- Add Dependencies
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-discovery-zookeeper
+ ${project.version}
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-http
+
+
+```
+
+- Add the Following Configuration in application.yml
+
+```yaml
+shenyu:
+ discovery:
+ enable: true
+ type: zookeeper
+ serverList: ${your.zookeeper.ip}:{your.zookeeper.port}
+ registerPath: /shenyu/discovery/demo_http_common
+ props:
+ baseSleepTimeMilliseconds: 1000
+ maxRetries: 4
+ maxSleepTimeMilliseconds: 5000
+ connectionTimeoutMilliseconds: 60000
+ sessionTimeoutMilliseconds: 8
+```
+
+- Start the shenyu-examples-http service.
+- Once the service registration is successful,
+you can view the list of automatically registered service instances on the selector page:
+
+
+
+- Users can click on `Edit` in the service instance list to edit the service instance information
+(Note that in non-Local mode, the URL is maintained by the registry and cannot be manually edited):
+
+
+
+
+- Test Connection
+
+```text
+curl http://localhost:9195/http/hello
+
+hello! I'm Shenyu-Gateway System. Welcome!%
+```
+
+### 4.3 Etcd Mode Example
+
+- Add Dependencies
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-discovery-etcd
+ ${project.version}
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-http
+
+
+```
+
+- Add the Following Configuration in application.yml
+
+```yaml
+shenyu:
+ discovery:
+ enable: true
+ protocol: http://
+ type: etcd
+ serverList: http://${your.etcd.host}:${your.etcd.port}
+ registerPath: /shenyu/test/http_common
+ props:
+ etcdTimeout: 3000
+ etcdTTL: 5
+```
+
+- Start the shenyu-examples-http service. Similarly, on the selector page,
+you can see the list of automatically registered service instances and edit them as needed:
+
+
+- Test Connection
+
+```text
+curl http://localhost:9195/http/hello
+
+hello! I'm Shenyu-Gateway System. Welcome!%
+```
+
+### 4.4 Eureka Mode Example
+
+- Add Dependencies
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-discovery-eureka
+ ${project.version}
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-http
+
+
+```
+
+- Add the Following Configuration in application.yml
+ (in this context, `registerPath` can be understood as the name of the service to be monitored):
+
+```yaml
+shenyu:
+ discovery:
+ enable: true
+ protocol: http://
+ type: eureka
+ serverList: http://${your.eureka.host}:${your.eureka.port}/eureka
+ registerPath: shenyu_discovery_demo_http_common
+ props:
+ eurekaClientRefreshInterval: 10
+ eurekaClientRegistryFetchIntervalSeconds: 10
+```
+
+- Start the shenyu-examples-http service. Similarly, on the selector page,
+you can see the list of automatically registered service instances and edit them as needed:
+
+
+
+- Test Connection
+
+```text
+curl http://localhost:9195/http/hello
+
+hello! I'm Shenyu-Gateway System. Welcome!%
+```
+
+### 4.5 Nacos Mode Example
+
+- Add Dependencies
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-discovery-eureka
+ ${project.version}
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-http
+
+
+```
+
+- Add the Following Configuration in application.yml
+(Here, `registerPath` can also be understood as the name of the service to be monitored.)
+
+```yaml
+shenyu:
+ discovery:
+ enable: true
+ protocol: http://
+ type: nacos
+ serverList: ${your.nacos.host}:${your.nacos.port}
+ registerPath: shenyu_discovery_demo_http_common
+ props:
+ groupName: SHENYU_GROUP
+```
+
+- Start the shenyu-examples-http service. Similarly, on the selector page,
+you can view the list of automatically registered service instances and edit them as needed.
+
+
+
+- Test Connection
+
+```text
+curl http://localhost:9195/http/hello
+
+hello! I'm Shenyu-Gateway System. Welcome!%
+```
+
+> **Note**：Configuring service discovery using Shenyu-client essentially configures service discovery at the plugin level.
+Under the same service discovery mode, there is, in fact, only one discovery object
+(meaning you can only configure the same set of type, server URL, and service discovery parameters), while multiple listening nodes can be configured.
+
+
+
+
+> **Note**：In the Divide and gRPC plugins, you can modify the protocol by configuring the protocol in the application.yml file.
+The default protocol for the Websocket plugin is 'ws'.
+
+
+
+## 5. Considerations
+
+- In local mode, you can manually modify all parameters of the upstream on the service list page.
+- In non-local modes, you can manually modify parameters other than URL and start time.
+- Manually changing the status (open/close) and weight of service instances only affects the current plugin.
+- For the same plugin, when configuring discovery-related parameters through Shenyu-client in the backend, it essentially configures service discovery at the plugin level. Although you can manually add selectors on the console page to configure selector-level service discovery, in reality, there is only one discovery object (meaning you can only configure the same set of type, server URL, and service discovery parameters), while multiple listening nodes can be configured.
+
+
+
+## 6. Test Report
+
+[Test Report](https://www.yuque.com/eureca/pgotw1/hkqkk5laubspgwl3#UojLR)
+
+
+
+
diff --git a/versioned_docs/version-2.6.1/user-guide/kubernetes-controller/_category_.json b/versioned_docs/version-2.6.1/user-guide/kubernetes-controller/_category_.json
new file mode 100644
index 00000000000..47a0b85e937
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/kubernetes-controller/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Kubernetes Controller",
+ "position": 5
+}
diff --git a/versioned_docs/version-2.6.1/user-guide/kubernetes-controller/build-deploy.md b/versioned_docs/version-2.6.1/user-guide/kubernetes-controller/build-deploy.md
new file mode 100644
index 00000000000..c8ecdbd9df4
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/kubernetes-controller/build-deploy.md
@@ -0,0 +1,120 @@
+---
+title: Build And Deploy Kubernetes Controller
+description: Build And Deploy Kubernetes Controller
+---
+
+This article introduces how to use ShenYu Ingress Controller.
+
+## Construct
+
+It is recommended to refer to [Custom Deployment](../../deployment/deployment-custom.md) to build a custom gateway, add the shenyu-kubernetes-controller dependency to the Maven dependency of the gateway, and the gateway can integrate the kubernetes controller.
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-k8s
+ ${project.version}
+
+```
+
+You can also directly use the officially built docker image (TODO, unfinished)
+
+## deployment
+
+K8s deployment files can refer to:
+
+```yaml
+apiVersion: v1
+kind: Namespace
+metadata:
+ name: shenyu-ingress
+---
+apiVersion: v1
+automountServiceAccountToken: true
+kind: ServiceAccount
+metadata:
+ name: shenyu-ingress-controller
+ namespace: shenyu-ingress
+---
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+ name: shenyu-ingress-controller
+ namespace: shenyu-ingress
+ labels:
+ app: shenyu-ingress-controller
+ all: shenyu-ingress-controller
+spec:
+ replicas: 1
+ selector:
+ matchLabels:
+ app: shenyu-ingress-controller
+ template:
+ metadata:
+ labels:
+ app: shenyu-ingress-controller
+ spec:
+ containers:
+ - name: shenyu-ingress-controller
+ image: apache/shenyu-integrated-test-k8s-ingress:latest
+ ports:
+ - containerPort: 9195
+ imagePullPolicy: IfNotPresent
+ serviceAccountName: shenyu-ingress-controller
+---
+apiVersion: v1
+kind: Service
+metadata:
+ name: shenyu-ingress-controller
+ namespace: shenyu-ingress
+spec:
+ selector:
+ app: shenyu-ingress-controller
+ type: NodePort
+ ports:
+ - port: 9195
+ targetPort: 9195
+ nodePort: 30095
+---
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRole
+metadata:
+ name: shenyu-ingress-controller
+rules:
+- apiGroups:
+ - ""
+ resources:
+ - namespaces
+ - services
+ - endpoints
+ - secrets
+ - pods
+ verbs:
+ - get
+ - list
+ - watch
+- apiGroups:
+ - networking.k8s.io
+ resources:
+ - ingresses
+ verbs:
+ - get
+ - list
+ - watch
+---
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRoleBinding
+metadata:
+ name: shenyu-ingress-controller
+ namespace: shenyu-ingress
+roleRef:
+ apiGroup: rbac.authorization.k8s.io
+ kind: ClusterRole
+ name: shenyu-ingress-controller
+subjects:
+- kind: ServiceAccount
+ name: shenyu-ingress-controller
+ namespace: shenyu-ingress
+```
+
+Among them, Service can be changed to `LoadBalancer` type according to the actual situation.
diff --git a/versioned_docs/version-2.6.1/user-guide/kubernetes-controller/config.md b/versioned_docs/version-2.6.1/user-guide/kubernetes-controller/config.md
new file mode 100644
index 00000000000..3203e134b56
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/kubernetes-controller/config.md
@@ -0,0 +1,115 @@
+---
+title: Kubernetes Controller Config
+description: Kubernetes Controller Config
+---
+
+This article introduces Kubernetes Controller configuration.
+
+## Enable HTTPS
+
+To enable HTTPS, you need to configure the `sni protocol` in the `application.yml` file of the gateway:
+
+```yaml
+shenyu:
+ netty:
+ http:
+ sni:
+ enabled: true
+ mod: k8s #k8s mode applies
+ defaultK8sSecretNamespace: shenyu-ingress #The namespace of the default secret resource
+ defaultK8sSecretName: default-cert #default secret resource name
+```
+
+Among them, the default secret resource must be available, but it will not be actually used at present.
+
+## Ingress configuration
+
+ShenYu Kubernetes Controller implements the K8s native Ingress standard, see [K8s official documentation](https://kubernetes.io/docs/concepts/services-networking/ingress/) for the use of the native standard
+
+In addition, Apache ShenYu has expanded based on the Annotation field of Ingress, and the configuration is shown in the following tables:
+
+### General
+
+| Name | Default | Required | Description |
+| --------------------------- | ------ | -------- | ----- --- |
+| kubernetes.io/ingress.class | | Yes | Fill in shenyu |
+
+### Divide plugin (HTTP proxy)
+
+| Name | Default | Required | Description |
+| ------------------------------------- | ------ | ------- - | ------------------------------------------------ ------------ |
+| shenyu.apache.org/loadbalancer | random | No | Load balancing algorithm, optional hash, random, roundRobin, leastActive, p2c, shortestResponse |
+| shenyu.apache.org/retry | 3 | No | Number of failed retries |
+| shenyu.apache.org/timeout | 3000 | No | Backend request timeout, in milliseconds |
+| shenyu.apache.org/header-max-size | 10240 | No | The maximum size of the request header, unit byte |
+| shenyu.apache.org/request-max-size | 102400 | No | Maximum request body size, unit byte |
+
+### Dubbo plugin
+
+| Name | Default | Required or not | Description |
+| ---------------------------------------------- | -------- | --------------- | ------------------------------------------------------------ |
+| shenyu.apache.org/loadbalancer | random | No | Load balancing algorithm, optional hash, random, roundRobin, lastActive, p2c, shortestResponse |
+| shenyu.apache.org/retry | 3 | No | Number of failed retries |
+| shenyu.apache.org/timeout | 3000 | no | Backend request timeout in milliseconds |
+| shenyu.apache.org/header-max-size | 10240 | No | Maximum request header size in bytes |
+| shenyu.apache.org/request-max-size | 102400 | No | Maximum request body size in bytes |
+| shenyu.apache.org/upstreams-protocol | dubbo:// | No | Specify the protocol protocol used by upstream |
+| shenyu.apache.org/plugin-dubbo-enabled | | No | Determines if the dubbo plugin is enabled |
+| shenyu.apache.org/zookeeper-register-address | | Yes | Specify zookeeper address |
+| shenyu.apache.org/plugin-dubbo-app-name | | Yes | Specify the metadata application name |
+| shenyu.apache.org/plugin-dubbo-path | | Yes | Specify the request path for metadata |
+| shenyu.apache.org/plugin-dubbo-rpc-type | | Yes | Specify the rpc type for metadata (dubbo, sofa, tars, springCloud, motan, grpc) |
+| shenyu.apache.org/plugin-dubbo-service-name | | Yes | Specify the interface name for the metadata |
+| shenyu.apache.org/plugin-dubbo-method-name | | Yes | Specifies the method name for metadata |
+| shenyu.apache.org/plugin-dubbo-rpc-expand | | No | Specifies the rpc expansion parameter (json object) for the metadata |
+| shenyu.apache.org/plugin-dubbo-parameter-types | | Yes | Specify parameter types for metadata |
+
+### Motan plugin
+
+| Name | Default | Required or not | Description |
+| ---------------------------------------------- | ------- | --------------- | ------------------------------------------------------------ |
+| shenyu.apache.org/loadbalancer | random | No | Load balancing algorithm, optional hash, random, roundRobin, lastActive, p2c, shortestResponse |
+| shenyu.apache.org/retry | 3 | No | Number of failed retries |
+| shenyu.apache.org/timeout | 3000 | No | Back-end request timeout in milliseconds |
+| shenyu.apache.org/header-max-size | 10240 | No | Maximum request header size in bytes |
+| shenyu.apache.org/request-max-size | 102400 | No | Maximum request body size in bytes |
+| shenyu.apache.org/plugin-motan-enabled | No | Yes | Determines if the motan plugin is enabled |
+| shenyu.apache.org/zookeeper-register-address | | Yes | Specify zookeeper address |
+| shenyu.apache.org/plugin-motan-app-name | | Yes | Specify the metadata application name |
+| shenyu.apache.org/plugin-motan-path | | Yes | Specify the request path for metadata |
+| shenyu.apache.org/plugin-motan-rpc-type | | Yes | Specify the rpc type for metadata (dubbo, sofa, tars, springCloud, motan, grpc) |
+| shenyu.apache.org/plugin-motan-service-name | | Yes | Specify the interface name for the metadata |
+| shenyu.apache.org/plugin-motan-method-name | | Yes | Specifies the method name for metadata |
+| shenyu.apache.org/plugin-motan-rpc-expand | | No | Specifies the rpc extension parameter (json object) for the metadata |
+| shenyu.apache.org/plugin-motan-parameter-types | | Yes | Specify parameter types for metadata |
+
+### SpringCloud plugin
+
+
+
+| Name | Default | Required or not | Description |
+| ----------------------------------------------------- | ------- | --------------- | ------------------------------------------------------------ |
+| shenyu.apache.org/loadbalancer | random | No | Load balancing algorithm, optional hash, random, roundRobin, lastActive, p2c, shortestResponse |
+| shenyu.apache.org/retry | 3 | No | Number of failed retries |
+| shenyu.apache.org/timeout | 3000 | No | Backend request timeout in milliseconds |
+| shenyu.apache.org/header-max-size | 10240 | No | Maximum request header size in bytes |
+| shenyu.apache.org/request-max-size | 102400 | No | Maximum request body size in bytes |
+| shenyu.apache.org/plugin-spring-cloud-enabled | | Yes | Determines whether to start the springCloud plugin |
+| shenyu.apache.org/zookeeper-register-address | | Yes | Specify the zookeeper address |
+| shenyu.apache.org/plugin-spring-cloud-app-name | | Yes | Specify the metadata application name |
+| shenyu.apache.org/plugin-spring-cloud-path | | Yes | Specify the request path for metadata |
+| shenyu.apache.org/plugin-spring-cloud-rpc-type | | Yes | Specify the rpc type (dubbo, sofa, tars, springCloud, motan, grpc) of the metadata |
+| shenyu.apache.org/plugin-spring-cloud-service-name | | Yes | Specify the interface name for metadata |
+| shenyu.apache.org/plugin-spring-cloud-method-name | | Yes | Specifies the method name for metadata |
+| shenyu.apache.org/plugin-spring-cloud-rpc-expand | | No | Specifies the rpc extension parameter (json object) for the metadata |
+| shenyu.apache.org/plugin-spring-cloud-parameter-types | | Yes | Specify parameter types for metadata |
+
+### WebSocket plugin
+
+| Name | Default | Required or not | Description |
+| ---------------------------------- | ------- | --------------- | ------------------------------------------------------------ |
+| shenyu.apache.org/loadbalancer | random | No | Load balancing algorithm, optional hash, random, roundRobin, lastActive, p2c, shortestResponse |
+| shenyu.apache.org/retry | 3 | No | Number of failed retries |
+| shenyu.apache.org/timeout | 3000 | No | Back-end request timeout in milliseconds |
+| shenyu.apache.org/header-max-size | 10240 | No | Maximum request header size in bytes |
+| shenyu.apache.org/request-max-size | 102400 | No | Maximum size of request body in byte |
diff --git a/versioned_docs/version-2.6.1/user-guide/property-config/_category_.json b/versioned_docs/version-2.6.1/user-guide/property-config/_category_.json
new file mode 100644
index 00000000000..b9d81b58d3e
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/property-config/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Property Config",
+ "position": 2
+}
diff --git a/versioned_docs/version-2.6.1/user-guide/property-config/admin-property-config.md b/versioned_docs/version-2.6.1/user-guide/property-config/admin-property-config.md
new file mode 100644
index 00000000000..f3dd630d338
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/property-config/admin-property-config.md
@@ -0,0 +1,270 @@
+---
+title: Admin Property Config
+keywords: ["Config"]
+description: Admin Property Config
+---
+
+This paper mainly explains how to configure Apache ShenYu properties on the admin side.
+
+
+
+
+### Property Config
+
+```yaml
+shenyu:
+ register:
+ registerType: http #http #zookeeper #etcd #nacos #consul
+ serverLists: #localhost:2181 #http://localhost:2379 #localhost:8848
+ props:
+ sessionTimeout: 5000
+ connectionTimeout: 2000
+ checked: true
+ zombieCheckTimes: 5
+ scheduledTime: 10
+ nacosNameSpace: ShenyuRegisterCenter
+ sync:
+ websocket:
+ enabled: true
+ messageMaxSize: 10240
+ allowOrigins: ws://localhost:9095;ws://localhost:9195;
+# zookeeper:
+# url: localhost:2181
+# sessionTimeout: 5000
+# connectionTimeout: 2000
+# http:
+# enabled: true
+# nacos:
+# url: localhost:8848
+# namespace: 1c10d748-af86-43b9-8265-75f487d20c6c
+# username:
+# password:
+# acm:
+# enabled: false
+# endpoint: acm.aliyun.com
+# namespace:
+# accessKey:
+# secretKey:
+# etcd:
+# url: http://localhost:2379
+# consul:
+# url: http://localhost:8500
+ aes:
+ secret:
+ key: 2095132720951327
+ iv: 6075877187097700
+ ldap:
+ enabled: false
+ url: ldap://xxxx:xxx
+ bind-dn: cn=xxx,dc=xxx,dc=xxx
+ password: xxxx
+ base-dn: ou=xxx,dc=xxx,dc=xxx
+ object-class: person
+ login-field: cn
+ jwt:
+ expired-seconds: 86400000
+ shiro:
+ white-list:
+ - /
+ - /favicon.*
+ - /static/**
+ - /index**
+ - /plugin
+ - /platform/**
+ - /websocket
+ - /configs/**
+ - /shenyu-client/**
+ - /error
+ - /actuator/health
+ - /swagger-ui.html
+ - /webjars/**
+ - /swagger-resources/**
+ - /v2/api-docs
+ - /csrf
+ swagger:
+ enable: true
+```
+
+
+### Property Detail
+
+##### shenyu.register config
+
+
+This section describes configurations related to client access. For details about client access principles, see: [Application Client Access](../../design/register-center-design) , for client access configuration, see: [Application Client Access Config](docs/user-guide/property-config/register-center-access.md) .
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|registerType |String | http | Yes | Which mode to use for registry. Currently, http, zookeeper, etcd, consul and nacos are supported.|
+|serverLists |String | null | No |Configure the address of the registry. If `http` is used, you do not need to enter this parameter. In clustering, multiple addresses are separated by commas (,).|
+|props | | | | The value of the property varies according to the registerType.|
+
+
+- `props` config
+
+The value of the attribute varies according to the registerType.
+
+When the registerType is `http`, the supported properties are as follows.
+
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|checked |boolean | false | No |is checked|
+|zombieCheckTimes |int | 5 | No |how many times does it fail to detect the service.|
+|scheduledTime |int | 10 | No | timed detection interval time|
+
+When the registerType is `zookeeper`, the supported properties are as follows.
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|sessionTimeout | int | 30000 | No |session timeout(millisecond)|
+|connectionTimeout | int | 3000 | No |connection timeout(millisecond)|
+
+When the registerType is `etcd`, no properties are provided for the time being.
+
+When the registerType is `nacos`, the supported properties are as follows.
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|nacosNameSpace | String | null | Yes |namespace|
+|username | String | "" | No |username|
+|password | String | "" | No |password|
+|accessKey | String | "" | No |accessKey|
+|secretKey | String | "" | No |secretKey|
+
+When the registerType is `consul`, the supported properties are as follows.
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|delay | int | 1 | No |The interval of each polling of monitoring metadata, in seconds, the default value is 1 second.|
+|wait-time | int | 55 | No |# wait-time: The waiting time for each polling of metadata monitoring, in seconds, the default value is 55 second .|
+|metadata-path | String | `shenyu/register` | No |Metadata path name, default is `shenyu/register`.|
+
+
+When the registerType is `apollo`, the supported properties are as follows.
+
+| Name | Type | Default | Required | Description |
+|:--------------|:-------|:-------:|:--------:|:---------------------|
+| appId | String | null | Yes | Apollo appId |
+| namespace | String | null | Yes | Apollo namespace |
+| portalUrl | String | null | Yes | Apollo portalUrl |
+| env | String | null | Yes | Apollo env |
+| clusterName | String | null | Yes | Apollo clusterName |
+| token | String | null | Yes | Apollo token |
+
+
+##### shenyu.sync config
+
+The Admin System and the Apache ShenYu gateway use data synchronization configurations.
+
+
+The following properties are configured for data synchronization using `websocket` :
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|enabled | boolean | true | No |whether to enable websocket for data synchronization.|
+|messageMaxSize | int | 0 | No |Set the `websocket` max buffer size in bytes.|
+|allowOrigins | String | "" | No |Set allowed `origins`, multiple parameters separated by `;`.|
+
+The following properties are configured for data synchronization using `zookeeper` :
+
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|url | String | null | Yes |zookeeper server url|
+|sessionTimeout | int | null | Yes |session timeout(millisecond)|
+|connectionTimeout | int | null | Yes |connection timeout(millisecond)|
+
+
+The following properties are configured for data synchronization using `http long polling` :
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|enabled | boolean | true | No |whether to enable.|
+|refreshInterval | int | 5(minute) | No |Periodically fetch data from the database and load it into memory.|
+|notifyBatchSize | int | 100 | No |notify clients in batches|
+
+
+The following properties are configured for data synchronization using `nacos` :
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|url | String | null | 是 |nacos url|
+|namespace | String | null | Yes |namespace|
+|username | String | null | No |username|
+|password | String | null | No |password|
+|acm | | | No |aliyun ACM service configuration|
+
+- `acm` config
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|enabled | boolean | false | No |whether to enable|
+|endpoint | String | null | No |ACM service address|
+|namespace | String | null | No |namespace|
+|accessKey | String | null | No |accessKey|
+|secretKey | String | null | No |secretKey|
+
+
+The following properties are configured for data synchronization using `etcd` :
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|url | String | null | Yes |etcd url|
+
+
+
+The following properties are configured for data synchronization using `consul` :
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|url | String | null | Yes |consul url|
+
+
+##### shenyu.aes.secret config
+
+aes secret properties:
+
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|key | String | `2095132720951327` | No |key|
+|iv | String | null | No |iv|
+
+
+##### shenyu.ldap config
+
+Spring ldap properties:
+
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|enabled | boolean | true | No |whether to enable|
+|url | String | null | No |ldap url|
+|bind-dn | String | null | No | UserDn |
+|password | String | null | No |password|
+|base-dn | String | null | No | searchBase |
+|object-class | String | `person` | No | filter |
+|login-field | String | `cn` | No | searchBase|
+|connectTimeout | int | 3000 | No |connect timeout(millisecond)|
+|readTimeout | int | 3000 | No |read timeout(millisecond)|
+
+
+##### shenyu.jwt config
+
+`jwt` properties:
+
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+| expired-seconds | long | 24 *60* 60 * 1000L | No |expiration time(millisecond)|
+
+
+##### shenyu.shiro config
+
+`shiro` properties:
+
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+| white-list | List | null | No |white list|
diff --git a/versioned_docs/version-2.6.1/user-guide/property-config/client-property-config.md b/versioned_docs/version-2.6.1/user-guide/property-config/client-property-config.md
new file mode 100644
index 00000000000..be863f087fb
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/property-config/client-property-config.md
@@ -0,0 +1,106 @@
+---
+title: Client Property Config
+keywords: ["Config"]
+description: Client Property Config
+---
+
+This paper mainly explains how to configure the properties of Apache ShenYu when the client accesses the gateway.
+
+
+Set the `shenyu` property in your microservice, for example, in [shenyu-examples-http](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http) :
+
+
+
+### Property Config
+
+```yaml
+shenyu:
+ client:
+ registerType: http #zookeeper #etcd #nacos #consul #apollo
+ serverLists: http://localhost:9095 #localhost:2181 #http://localhost:2379 #localhost:8848 #localhost:8080
+ props:
+ contextPath: /http
+ appName: http
+ port: 8189
+ nacosNameSpace: ShenyuRegisterCenter
+```
+
+
+### Property Detail
+
+##### shenyu.client config
+
+This section describes configurations related to client access. For details about client access principles, see: [Application Client Access](../../design/register-center-design) , for client access configuration, see: [Application Client Access Config](register-center-access.md) .
+
+
+
+| Name | Type | Default | Required | Description |
+|:-------------|:-------|:-------:|:--------:|:----------------------------------------------------------------------------------------------------------|
+| registerType | String | http | Yes | Which mode to use for registry. Currently, http, zookeeper, etcd, consul ,apollo and nacos are supported. |
+| serverLists | String | null | No | Configure the address of the registry. In clustering, multiple addresses are separated by commas (,). |
+| props | | | | The value of the property varies according to the registerType. |
+
+
+
+- `props` config
+
+When microservices are built by different protocols, the property configuration is slightly different. The general attributes are as follows:
+
+
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|contextPath |String | null | Yes |The route prefix of the microservice in the gateway.|
+|appName |String | null | Yes |microservice name. `springcloud` service don't set, please set `spring.application.name`.|
+|host |String | null | Yes | microservice address|
+|port |int | null | Yes | microservice port|
+|isFull |boolean | false | No | Whether to proxy the all service, currently just applies to `springmvc`/ `springcloud`|
+|ipAndPort |String | null | No | Service IP and port address, currently just applies to `gRPC` Proxy.|
+|shutdownWaitTime |int | 3000 | No | shutdown wait time(millisecond)|
+|delayOtherHooksExecTime |int | 2000 | No | `hook` execute time(millisecond)|
+|applicationShutdownHooksClassName |String | `java.lang.ApplicationShutdownHooks` | No | `hook` execute class name|
+|applicationShutdownHooksFieldName |String | `hooks` | No | `hook` execute field name |
+
+
+The value of the property varies according to the `registerType`.
+
+When the registerType is `nacos`, there has no other properties.
+
+
+
+When the registerType is `zookeeper`, the supported properties are as follows.
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|sessionTimeout | int | 30000 | No |session time out(millisecond)|
+|connectionTimeout | int | 3000 | No |connection time out(millisecond)|
+
+When the registerType is `etcd`, the supported properties are as follows.
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|etcdTimeout | int | 30000 | No |etcd time out(millisecond)|
+|etcdTTL | int | 5 | No |client lease time to live(second)|
+
+When the registerType is `nacos`, the supported properties are as follows.
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|nacosNameSpace | String | null | Yes |namespace |
+|username | String | "" | No |username|
+|password | String | "" | No |password|
+|accessKey | String | "" | No |accessKey|
+|secretKey | String | "" | No |secretKey|
+
+When the registerType is `apollo`, the supported properties are as follows.
+
+| Name | Type | Default | Required | Description |
+|:------------|:-------|:--------:|:--------:|:------------|
+| appId | String | "shenyu" | Yes | appId |
+| env | String | "" | Yes | env |
+| clusterName | String | "" | Yes | clusterName |
+| namespace | String | "" | Yes | namespace |
+| token | String | "" | Yes | token |
+| portalUrl | String | "" | Yes | portalUrl |
+
+When the registerType is `consul`, no other property configuration is provided. please set `spring.cloud.consul` for the configuration.
diff --git a/versioned_docs/version-2.6.1/user-guide/property-config/gateway-property-config.md b/versioned_docs/version-2.6.1/user-guide/property-config/gateway-property-config.md
new file mode 100644
index 00000000000..d7b90e98dee
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/property-config/gateway-property-config.md
@@ -0,0 +1,634 @@
+---
+title: Gateway Property Config
+keywords: ["Config"]
+description: Gateway Property Config
+---
+
+This paper mainly explains how to configure `Apache ShenYu` properties on the gateway side.
+
+
+
+### Property Config
+
+```yaml
+shenyu:
+ selectorMatchCache:
+ ## selector L1 cache
+ cache:
+ enabled: false
+ initialCapacity: 10000 # initial capacity in cache
+ maximumSize: 10000 # max size in cache
+ ## selector L2 cache, use trie as L2 cache
+ trie:
+ enabled: false
+ cacheSize: 128 # the number of plug-ins
+ matchMode: antPathMatch
+ ruleMatchCache:
+ ## rule L1 cache
+ cache:
+ enabled: true
+ initialCapacity: 10000 # initial capacity in cache
+ maximumSize: 65536 # max size in cache
+ ## rule L2 cache, use trie as L2 cache
+ trie:
+ enabled: false
+ cacheSize: 1024 # the number of selectors
+ matchMode: antPathMatch
+ netty:
+ http:
+ webServerFactoryEnabled: true
+ selectCount: 1
+ workerCount: 4
+ accessLog: false
+ serverSocketChannel:
+ soRcvBuf: 87380
+ soBackLog: 128
+ soReuseAddr: true
+ connectTimeoutMillis: 30000
+ writeBufferHighWaterMark: 65536
+ writeBufferLowWaterMark: 32768
+ writeSpinCount: 16
+ autoRead: false
+ allocType: "pooled"
+ messageSizeEstimator: 8
+ singleEventExecutorPerGroup: true
+ socketChannel:
+ soKeepAlive: false
+ soReuseAddr: true
+ soLinger: -1
+ tcpNoDelay: true
+ soRcvBuf: 87380
+ soSndBuf: 16384
+ ipTos: 0
+ allowHalfClosure: false
+ connectTimeoutMillis: 30000
+ writeBufferHighWaterMark: 65536
+ writeBufferLowWaterMark: 32768
+ writeSpinCount: 16
+ autoRead: false
+ allocType: "pooled"
+ messageSizeEstimator: 8
+ singleEventExecutorPerGroup: true
+ instance:
+ enabled: false
+ registerType: zookeeper #etcd #consul
+ serverLists: localhost:2181 #http://localhost:2379 #localhost:8848
+ props:
+# httpclient:
+# strategy: webClient
+# connectTimeout: 45000
+# responseTimeout: 3000
+# readerIdleTime: 3000
+# writerIdleTime: 3000
+# allIdleTime: 3000
+# readTimeout: 3000
+# writeTimeout: 3000
+# wiretap: false
+# keepAlive: false
+# pool:
+# type: ELASTIC
+# name: proxy
+# maxConnections: 16
+# acquireTimeout: 45000
+# maxIdleTime: 3000
+# proxy:
+# host:
+# port:
+# username:
+# password:
+# nonProxyHostsPattern:
+# ssl:
+# useInsecureTrustManager: true
+# keyStoreType: PKCS12
+# keyStorePath: classpath:keystore.p12
+# keyStorePassword: 123456
+# keyStoreProvider:
+# keyPassword: 123456
+# trustedX509Certificates:
+# handshakeTimeout:
+# closeNotifyFlushTimeout:
+# closeNotifyReadTimeout:
+# defaultConfigurationType:
+ sync:
+ websocket:
+ urls: ws://localhost:9095/websocket
+ allowOrigin: ws://localhost:9195
+# zookeeper:
+# url: localhost:2181
+# sessionTimeout: 5000
+# connectionTimeout: 2000
+# http:
+# url: http://localhost:9095
+# nacos:
+# url: localhost:8848
+# namespace: 1c10d748-af86-43b9-8265-75f487d20c6c
+# username:
+# password:
+# acm:
+# enabled: false
+# endpoint: acm.aliyun.com
+# namespace:
+# accessKey:
+# secretKey:
+# etcd:
+# url: http://localhost:2379
+# consul:
+# url: http://localhost:8500
+# waitTime: 1000
+# watchDelay: 1000
+ cross:
+ enabled: true
+ allowedHeaders:
+ allowedMethods: "*"
+ allowedAnyOrigin: false
+ allowedOrigin:
+ # format : schema://prefix spacer domain
+ # Access-Control-Allow-Origin: "http://a.apache.org,http://b.apache.org"
+ spacer: "."
+ domain: apache.org
+ prefixes:
+ - a # a.apache.org
+ - b # b.apache.org
+ origins:
+ - c.apache.org
+ - d.apache.org
+ - http://e.apache.org
+ originRegex: ^http(|s)://(.*\.|)abc.com$
+ allowedExpose: ""
+ maxAge: "18000"
+ allowCredentials: true
+ switchConfig:
+ local: true
+ file:
+ enabled: true
+ maxSize : 10
+ exclude:
+ enabled: false
+ paths:
+ - /favicon.ico
+ fallback:
+ enabled: false
+ paths:
+ - /fallback/hystrix
+ - /fallback/resilience4j
+ health:
+ enabled: false
+ paths:
+ - /actuator/health
+ - /health_check
+ alert:
+ enabled: true
+ admins: localhost:9095
+ extPlugin:
+ path:
+ enabled: true
+ threads: 1
+ scheduleTime: 300
+ scheduleDelay: 30
+ scheduler:
+ enabled: false
+ type: fixed
+ threads: 16
+ upstreamCheck:
+ enabled: false
+ timeout: 3000
+ healthyThreshold: 1
+ unhealthyThreshold: 1
+ interval: 5000
+ printEnabled: true
+ printInterval: 60000
+ ribbon:
+ serverListRefreshInterval: 10000
+ metrics:
+ enabled: false
+ name : prometheus
+ host: 127.0.0.1
+ port: 8090
+ jmxConfig:
+ props:
+ jvm_enabled: true
+ sharedPool:
+ enable: true
+ prefix: "shenyu-shared"
+ corePoolSize: 200
+ maximumPoolSize: 2000
+ keepAliveTime: 60000
+ maxWorkQueueMemory: 1073741824 # 1GB
+ maxFreeMemory: 268435456 # 256MB
+```
+
+### Property Detail
+
+
+
+##### shenyu.matchCache config
+
+* selector match cache
+
+| Field | Type | Default | Required | Description |
+|-----------------|---------|---------|----------|-----------------------------------|
+| enabled | Boolean | false | No | Whether to enable selector cache. |
+| initialCapacity | Integer | 10000 | No | selector initial capacity |
+| maximumSize | Integer | 10000 | No | selector max size |
+
+* selector trie cache
+
+| Field | Type | Default | Required | Description |
+|--------------|---------|--------------|----------|-----------------------------------------------------------------------------------|
+| enabled | Boolean | false | No | Whether to enable selector trie cache |
+| cacheSize | Integer | 512 | No | trie cache size |
+| matchMode | String | antPathMatch | Yes | path match mode, shenyu support two match modes, `antPathMatch` and `pathPattern` |
+
+
+* rule match cache
+
+| Field | Type | Default | Required | Description |
+|-----------------|---------|---------|----------|-------------------------------|
+| enabled | Boolean | false | No | Whether to enable rule cache. |
+| initialCapacity | Integer | 10000 | No | selector initial capacity |
+| maximumSize | Integer | 10000 | No | selector max size |
+
+* rule trie cache
+
+| Field | Type | Default | Required | Description |
+|--------------|---------|--------------|----------|-----------------------------------------------------------------------------------|
+| enabled | Boolean | false | No | Whether to enable rule trie cache |
+| cacheSize | Integer | 512 | No | trie cache size |
+| matchMode | String | antPathMatch | Yes | path match mode, shenyu support two match modes, `antPathMatch` and `pathPattern` |
+
+
+shenyu trie match support two match mode, we suggest use `pathPattern` as default match mode
+
+> pathPattern: org.springframework.web.util.pattern.PathPatternParser
+> antPathMatch: org.springframework.util.AntPathMatcher
+
+when you mark `matchRestful` as true, we suggest mark all cache to `false` to avoid cache conflict.
+
+##### shenyu.NettyTcpProperties config
+
+The apache shenyu reactor-netty config.
+
+| Name | Type | Default | Required | Description |
+|:------------------------------|:--------|:-------:|:--------:|:------------------------------------------------------------------------------------------------------------------------------------------|
+| webServerFactoryEnabled | Boolean | true | No | Whether to enable custom parameters. True-enable. False-NettyReactiveWebServerFactory Can be configured by yourself. |
+| selectCount | Integer | 1 | No | Number of netty selectors. |
+| workerCount | Integer | 4 | No | Number of netty workers. |
+| accessLog | Boolean | false | No | netty request parameters. |
+| **ServerSocketChannelConfig** | | | | |
+| soRcvBuf | Integer | -- | No | Socket config, the size of the socket receive buffer. The default value is system dependent. |
+| soBackLog | Integer | 128 | No | Socket config, maximum length of the accept queue. |
+| soReuseAddr | Boolean | true | No | Socket config, allow reuse of local addresses. The default value in reactor-netty is true. |
+| connectTimeoutMillis | Integer | 30000 | No | Netty config, the connect timeout of the channel in milliseconds. |
+| writeBufferHighWaterMark | Integer | 65536 | No | Netty config, the high water mark of the write buffer. |
+| writeBufferLowWaterMark | Integer | 32768 | No | Netty config, the low water mark of the write buffer. |
+| writeSpinCount | Integer | 16 | No | Netty config, the maximum loop count for a write operation. |
+| autoRead | Boolean | false | No | Netty config, channel read method will be invoked automatically so that a user application doesn't need to call it at all. The default value in reactor-netty is false, and can only be false. |
+| allocType | String | pooled | No | Netty config, set the ByteBufAllocator which is used for the channel to allocate buffers. |
+| messageSizeEstimator | Integer | 8 | No | Netty config, message size estimator, estimate ByteBuf,ByteBufHolder and FileRegion size. |
+| singleEventExecutorPerGroup | Boolean | true | No | Netty config, single thread execute the event of ChannelPipeline. |
+| **SocketChannelConfig** | | | | |
+| soKeepAlive | Boolean | false | No | Socket config, enable tcp keepalive. |
+| soReuseAddr | Boolean | true | No | Socket config, allow reuse of local addresses. The default value in reactor-netty is true. |
+| soLinger | Integer | -1 | No | Socket config, the delay time for closing the socket. |
+| tcpNoDelay | Boolean | true | No | Socket config, enable Nagle algorithm. |
+| soRcvBuf | Integer | -- | No | Socket config, the size of the socket receive buffer. The default value is system dependent. |
+| soSndBuf | Integer | -- | No | Socket config, the size of the socket send buffer. The default value is system dependent. |
+| ipTos | Integer | 0 | No | IP config, the Type of Service (ToS) octet in the Internet Protocol (IP) header. |
+| allowHalfClosure | Boolean | false | No | Netty config, Sets whether the channel should not close itself when its remote peer shuts down output to make the connection half-closed. |
+| connectTimeoutMillis | Integer | 30000 | No | Netty config, the connect timeout of the channel in milliseconds. |
+| writeBufferHighWaterMark | Integer | 65536 | No | Netty config, the high water mark of the write buffer. |
+| writeBufferLowWaterMark | Integer | 32768 | No | Netty config, the low water mark of the write buffer. |
+| writeSpinCount | Integer | 16 | No | Netty config, the maximum loop count for a write operation. |
+| autoRead | Boolean | false | No | Netty config, channel read method will be invoked automatically so that a user application doesn't need to call it at all. The default value in reactor-netty is false, and can only be false. |
+| allocType | String | pooled | No | Netty config, set the ByteBufAllocator which is used for the channel to allocate buffers. |
+| messageSizeEstimator | Integer | 8 | No | Netty config, message size estimator, estimate ByteBuf,ByteBufHolder and FileRegion size. |
+| singleEventExecutorPerGroup | Boolean | true | No | Netty config, single thread execute the event of ChannelPipeline. |
+
+##### shenyu.register config
+
+This is the relevant configuration for the `ShenYu` gateway to register to the registration center. For the configuration of the registration center, please refer to [Register Center Instance Config](register-center-instance.md).
+
+| Name | Type | Default | Required | Description |
+| :----------- | :-----: | :------------: | :------: | :----------------------------------------------------------- |
+| enabled | boolean | false | Yes | Whether to start. |
+| registerType | String | zookeeper | Yes | Which registry to use, currently supports zookeeper, etcd. |
+| serverLists | String | localhost:2181 | Yes | The address of the register center. If using clusters, separate with `,`. |
+| props | | | | When using different register types, the attribute values are different. |
+
+- `props` config
+
+When using different register center, the attribute values are different.
+
+When the registerType is `zookeeper`, the supported properties are as follows.
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|sessionTimeout | int | 30000 | No |session time out(millisecond).|
+|connectionTimeout | int | 3000 | No |connection time out(millisecond).|
+
+When the registerType is `etcd`, the supported properties are as follows.
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|etcdTimeout | int | 30000 | No |etcd time out(millisecond).|
+|etcdTTL | int | 5 | No |client lease time to live(second).|
+
+##### shenyu.httpclient config
+
+This is the HttpClient configuration used to send proxy requests after proxying the Http and SpringCloud protocols in the `ShenYu` gateway.
+
+| Name | Type | Default | Required | Description |
+| :-------------- | :-----: | :-------: | :------: | :----------------------------------------------------------- |
+| strategy | String | webClient | No | Type of http client, defaults to webClient. - webClient: use by WebClientPlugin - netty: use by NettyHttpClientPlugin. |
+| connectTimeout | int | 45000 | No | Connection timeout (millisecond), the default value is 45000. |
+| responseTimeout | int | 3000 | No | The response timeout (millisecond), the default value is 3000. |
+| readerIdleTime | int | 3000 | No | The reader idle timeout (millisecond), the default value is 3000. |
+| writerIdleTime | int | 3000 | No | The writer idle timeout (millisecond), the default value is 3000. |
+| allIdleTime | int | 3000 | No | The all idle timeout (millisecond), the default value is 3000. |
+| readTimeout | int | 3000 | No | Read timeout (millisecond), the default value is 3000. |
+| writeTimeout | int | 3000 | No | Write timeout (millisecond), the default value is 3000. |
+| wiretap | Boolean | false | No | Enables wiretap debugging for Netty HttpClient, the default value is 'false'. |
+| keepAlive | Boolean | false | No | Enable or Disable Keep-Alive support for the outgoing request, the default value is 'false'. |
+| pool | | | | HttpClient connection pool config. |
+| proxy | | | | HttpClient proxy config. |
+| ssl | | | | HttpClient ssl config. |
+
+- `pool` config
+
+HttpClient connection pool configuration:
+
+| Name | Type | Default | Required | Description |
+| :------------- | :----: | :-------------------------------: | :------: | :----------------------------------------------------------- |
+| type | String | ELASTIC | No | Type of pool for HttpClient to use, defaults to ELASTIC. - ELASTIC: The connection pool can be cached and grown on demand - FIXED: The connection pool cache and reuse a fixed maximum The number of connections. - DISABLED: The connection pool will always create a new connection. |
+| name | String | proxy | No | The channel pool map name, defaults to proxy. |
+| maxConnections | int | the maximum value of 2*CPU and 16 | No | Only for type FIXED, the maximum number of connections before starting pending acquisition on existing ones. the default value is available number of processors*2. (but with a minimum value of 16). |
+| acquireTimeout | int | 45000 | No | Only for type FIXED, the maximum time in millis to wait for acquiring. the default value is 45000. |
+| maxIdleTime | int | NULL | No | After which the channel will be closed, if NULL there is no max idle time. |
+
+- `proxy` config
+
+Netty HttpClient proxy configuration:
+
+| Name | Type | Default | Required | Description |
+| :------------------- | :----: | :-----: | :------: | :----------------------------------------------------------- |
+| host | String | null | No | Hostname for proxy configuration of Netty HttpClient. |
+| port | String | null | No | Port for proxy configuration of Netty HttpClient. |
+| username | String | null | No | Username for proxy configuration of Netty HttpClient. |
+| password | String | null | No | Password for proxy configuration of Netty HttpClient. |
+| nonProxyHostsPattern | String | null | No | Regular expression (Java) for a configured list of hosts. that should be reached directly, bypassing the proxy. |
+
+- `SSL` config
+
+Gateway routing can support routing to http and https back-end services at the same time. The following is the SSL-related configuration:
+
+| Name | Type | Default | Required | Description |
+| :----------------------- | :-----: | :-----: | :------: | :----------------------------------------------------------- |
+| useInsecureTrustManager | Boolean | false | No | Installs the netty InsecureTrustManagerFactory. This is insecure and not suitable for production. |
+| keyStoreType | String | PKCS12 | No | SSL key store type. |
+| keyStorePath | String | | No | SSL key store path. |
+| keyStorePassword | String | | No | SSL key store pass word. |
+| keyStoreProvider | String | | No | SSL Keystore provider for netty httpClient and webclient. |
+| keyPassword | String | | No | SSL key pass word. |
+| trustedX509Certificates | String | Null | No | Trusted certificates for verifying the remote endpoint's certificate.(Use `,` to separate multiple values) |
+| handshakeTimeout | int | 10000 | No | SSL handshake timeout. Default to 10000 ms |
+| closeNotifyFlushTimeout | int | 3000 | No | SSL close_notify flush timeout. Default to 3000 ms. |
+| closeNotifyReadTimeout | int | 0 | No | SSL close_notify read timeout. Default to 0 ms. |
+| defaultConfigurationType | String | TCP | No | The default ssl configuration type. Defaults to TCP. - H2: SslProvider will be set depending on OpenSsl.isAlpnSupported(), SslProvider.HTTP2_CIPHERS, ALPN support, HTTP/1.1 and HTTP/2 support. - TCP: [`SslProvider`](https://netty.io/4.1/api/io/netty/handler/ssl/SslProvider.html?is-external=true) will be set depending on `OpenSsl.isAvailable()`. - NONE: There will be no default configuration. |
+
+##### Filter Configuration
+
+- `shenyu.file` config
+
+File filter properties.
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+| enabled | Boolean | false | No | enable file size filtering |
+| maxSize | Integer | 10 | No | upload file maxSize （MB） |
+
+
+- `shenyu.cross` config
+
+Cross filter properties:
+
+
+|Name | | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|:---------------------------:|
+| enabled | | Boolean | false | No | allow cross-domain requests |
+| allowedHeaders | | String | x-requested-with, authorization, Content-Type, Authorization, credential, X-XSRF-TOKEN, token, username, client | No | allowedHeaders, Use "," split in multiple cases. the new "allowedHeaders" will append to "Access-Control-Allow-Headers" based on the default value and remove the reduplicative header. |
+| allowedMethods | | String | "*" | No | allowedMethods |
+| allowedAnyOrigin | | Boolean | false | No | Whether to allow any Origin, if it is true, directly set the `Access-Control-Allow-Origin` to the same value as the Origin, that is, `request.getHeaders().getOrigin()`, and discard the `allowedOrigin` configuration. |
+| allowedOrigin | | AllowedOriginConfig | - | No | Set the allowed request sources. |
+| | spacer | String | "" | No | Set the allowed subdomains, need to use with `domain`, `prefixes`. |
+| | domain | String | "" | No | Set the allowed subdomains, need to use with `spacer`, `prefixes`. |
+| | prefixes | Set | [] | No | Set the allowed subdomains, need to use with `spacer`, `domain`. |
+| | origins | Set | null | No | Set the domain names that are allowed to be accessed, which can be used separately. |
+| | originRegex | String | "" | No | Set up access to domains that allow regular matching, available separately. |
+| allowedExpose | | String | "" | No | allowedExpose |
+| maxAge | | String | "18000" | No | maxAge (ms) |
+| allowCredentials | | Boolean | true | No | allowCredentials |
+
+
+- `shenyu.exclude` config
+
+Exculde filter properties.
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+| enabled | Boolean | false | No | whether to enable `exclude filter` and reject the specified request to pass through the gateway. |
+| paths | Array | null | Yes | Requests matching this list can not pass through the gateway (support Path-Matching). |
+
+- `shenyu.fallback` config
+
+Related configuration of fallback response.
+
+| Name | Type | Default | Required | Description |
+| :------ | :------ | :-----: | :------: | :---------------------------------------- |
+| enabled | Boolean | false | No | Whether to turn on the fallback response. |
+| paths | Array | [] | Yes | Address of the service fallback request. |
+
+- `shenyu.health` config
+
+Configuration related to service health status.
+
+| Name | Type | Default | Required | Description |
+| :------ | :------ |:----------------------------------------:| :------: | :-------------------------------------- |
+| enabled | Boolean | false | No | Whether to turn on health detection. |
+| paths | Array | `"/actuator/health"` 、`"/health_check"` | No | Set up service health monitoring paths. |
+
+- `shenyu.local` config
+
+Local forwarding-related configuration.
+
+| Name | Type | Default | Required | Description |
+| :-------- | :------ | :-----: | :------: | :----------------------------------------------------------- |
+| enabled | Boolean | false | No | Whether to enable local forwarding. |
+| sha512Key | String | "" | Yes | Secret key, according to the secret key to determine whether the need for local forwarding. |
+
+##### shenyu.switchConfig config
+
+The apache shenyu switch configuration.
+
+| Name | Type | Default | Required | Description |
+| :---- | :------ | :-----: | :------: | :----------------------------------------------------------- |
+| local | Boolean | true | No | Whether to open local mode, if so, local operation data, default open. |
+
+##### shenyu.sync config
+
+The apache shenyu gateway and the Admin System use data synchronization configurations.
+
+
+The following properties are configured for data synchronization using `websocket` :
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+| urls | String | null | Yes | The websocket server address of `Admin`, separate multiple addresses with `,`. |
+| allowOrigin | String | "" | No | Set the allowed `origins`, with multiple parameters separated by `;`. |
+
+
+
+The following properties are configured for data synchronization using `zookeeper` :
+
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|url | String | null | Yes |zookeeper server url.|
+|sessionTimeout | int | null | Yes |session timeout (millisecond).|
+|connectionTimeout | int | null | Yes |connection timeout (millisecond).|
+
+
+
+The following properties are configured for data synchronization using `http long polling` :
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+| url | String | null | Yes | `Admin` server address. |
+
+
+
+The following properties are configured for data synchronization using `nacos` :
+
+|Name | | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:---------|:---------------------------:|
+|url | | String | null | Yes |nacos url|
+|namespace | | String | null | Yes |namespace|
+|username | | String | null | No |username|
+|password | | String | null | No |password|
+|acm | | Object | - | No |aliyun ACM service configuration.|
+| |enabled | boolean | false | No |whether to enable.|
+| |endpoint | String | null | No |ACM service address.|
+| |namespace | String | null | No |namespace.|
+| |accessKey | String | null | No |accessKey.|
+| |secretKey | String | null | No |secretKey.|
+
+The following properties are configured for data synchronization using `apollo` :
+
+| Name | | Type | Default | Required | Description |
+|:------------|:----|:------:|:-------:|:---------|:-----------:|
+| namespace | | String | null | Yes | namespace |
+| appId | | String | null | Yes | appId |
+| token | | String | null | Yes | token |
+| clusterName | | String | default | Yes | cluster |
+| portalUrl | | String | null | Yes | portalUrl |
+| meta | | String | null | Yes | meta |
+| env | | String | null | Yes | env |
+
+
+
+The following properties are configured for data synchronization using `etcd` :
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|url | String | null | Yes |`etcd` server url.|
+
+
+
+The following properties are configured for data synchronization using `consul` :
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|url | String | null | Yes |`consul` server url.|
+| waitTime | int | null | Yes | the timeout period for requesting consul service to pull configuration information (milliseconds). |
+|watchDelay | int | null | Yes |Synchronization interval (milliseconds).|
+
+##### shenyu.extPlugin config
+
+The apache shenyu supports dynamic loading of custom plug-ins with the following configuration
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+| enabled | Boolean | true | No | open dynamic loading of custom plug-ins. |
+| path | String | | False | custom plugins path, if not config, the path is /ext/lib. |
+| threads | Integer | 1 | False | threads for dynamic loading custom plug-ins. |
+| scheduleTime | Integer | 300 | False | schedule time (s) for dynamic loading custom plug-ins. |
+| scheduleDelay | Integer | 30 | False | schedule delay when app startup. |
+
+##### shenyu.scheduler config
+
+Scheduler config for apache shenyu scheduler thread model.
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+| enabled | Boolean | false | No | Whether to turn on Scheduler Thread Model. |
+| type | String | fixed | False | fixed Thread Pool or elastic Scheduler Thread Model. |
+| threads | Integer | Math.max((Runtime.getRuntime().availableProcessors() << 1) + 1, 16) | False | threads for fixed Thread Pool. |
+
+##### shenyu.upstreamCheck config
+
+UpstreamCheck config is the configuration used by apache shenyu to detect upstream.
+
+|Name | Type | Default | Required | Description |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+| enabled | Boolean | false | No | Whether to turn on upstreamCheck. |
+| timeout | Integer | 3000 | No | timeout (ms). |
+| healthyThreshold | Integer | 1 | No | healthyThreshold. |
+| unhealthyThreshold | Integer | 1 | No | unhealthyThreshold. |
+| interval | Integer | 5000 | No | schedule time (ms) for checked. |
+| printEnabled | Boolean | true | No | Whether to turn on print logs. |
+| printInterval | Integer | 60000 | No | schedule time (ms) for print logs. |
+
+##### shenyu.ribbon config
+
+The apache shenyu polling interval configuration.
+
+| Name | Type | Default | Required | Description |
+| :------------------------ | :------ | :-----: | :------: | :----------------------------------------------------------- |
+| serverListRefreshInterval | Integer | 10000 | No | Adjust the refresh interval parameter, refer to`com.netflix.client.config.CommonClientConfigKey#ServerListRefreshInterval`. |
+
+##### shenyu.metrics config
+
+The apache shenyu metrics config，the gateway is used to monitor its own operational status.
+
+| Name | | Type | Default | Required | Description |
+| :-------- | :---------- | :-----: | :-----: | :------- | ------------------------------------------------------------ |
+| enabled | | Boolean | false | No | Whether to enable metrics, true means enable. |
+| name | | String | "" | No | name. |
+| host | | String | "" | No | IP exposed by the gateway service to the collection service. |
+| port | | Integer | Null | No | Port exposed by the gateway service to the collection service. |
+| jmxConfig | | String | "" | No | jmx config. |
+| props | | - | | No | properties. |
+| | jvm_enabled | Boolean | Null | No | Turn on jvm's monitoring metrics. |
+
+##### shenyu.sharedPool config
+
+The apache shenyu shared thread pool configuration.
+
+| Name | Type | Default | Required | Description |
+| :----------------- | ------- | :---------------------------------------------- | :------: | :-------------------------------------------------: |
+| enabled | Boolean | false | No | Whether to enable shared thread pooling. |
+| prefix | String | "shenyu-shared" | No | Thread pool name prefix. |
+| corePoolSize | Integer | 200 | No | Number of core threads in the thread pool. |
+| maximumPoolSize | Integer | Integer.MAX_VALUE | No | Maximum number of threads in the thread pool. |
+| keepAliveTime | Long | 60000L | No | Excess idle thread keepAlive time, in milliseconds. |
+| maxWorkQueueMemory | Long | 80% of the current JVM maximum available memory | No | Maximum memory used (byte). |
+| maxFreeMemory | Integer | 无 | No | Maximum remaining memory (byte). |
+
+##### shenyu.alert config
+
+The apache shenyu alert notice configuration.
+
+| Name | Type | Default | Required | Description |
+| :----------------- | ------- |:------------------------------------------------| :------: |:-------------------------------------------------:|
+| enabled | Boolean | false | No | Whether to enable alarm message. |
+| admins | String | "localhost:9095" | No | Report alarm message to shenyu admin server list. |
+
diff --git a/versioned_docs/version-2.6.1/user-guide/property-config/register-center-access.md b/versioned_docs/version-2.6.1/user-guide/property-config/register-center-access.md
new file mode 100644
index 00000000000..e3f23d21ed0
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/property-config/register-center-access.md
@@ -0,0 +1,109 @@
+---
+title: Application Client Access Config
+keywords: ["register center"]
+description: register center access
+---
+
+> *Notice*
+> After ShenYu version 2.6.1, the ShenYu register just support http type, and the middleware register type has been removed.
+> So, please use the http register type to register your service.
+> ShenYu Register Center isn't microservice register center, it just register metadata, selector data, rule data to shenyu-admin, and then shenyu-admin will sync data to shenyu-gateway.
+
+Application client access means to access your microservice to ShenYu gateway, currently supports HTTP, Dubbo, Spring Cloud, gRPC, Motan, Sofa, Tars and other protocols access. Currently, ShenYu just support HTTP register type.
+
+This article describes how to configure the application client to access the Apache ShenYu gateway. For related principles, see [Application Client Access](../../design/register-center-design) in the design document .
+
+
+
+
+### Http Registry Config
+
+#### shenyu-admin config
+
+Set the register type to '`Http` in the `yml` file. The configuration information is as follows:
+
+```yaml
+shenyu:
+ register:
+ registerType: http
+ props:
+ checked: true # is checked
+ zombieCheckTimes: 5 # how many times does it fail to detect the service
+ scheduledTime: 10 # timed detection interval time
+```
+
+
+
+
+#### shenyu-client config
+
+The following shows the configuration information registered through `Http` when the `Http` service accesses the `Apache ShenYu` gateway as a client. Other clients (such as `Dubbo` and `Spring Cloud`) can be configured in the same way.
+
+```yaml
+shenyu:
+ register:
+ registerType: http
+ serverLists: http://localhost:9095
+ props:
+ username: admin
+ password: 123456
+ client:
+ http:
+ props:
+ contextPath: /http
+ appName: http
+ port: 8188
+ isFull: false
+# registerType : register type, set http
+# serverList: when register type is http，set shenyu-admin address list，pls note 'http://' is necessary.
+# port: your project port number; apply to springmvc/tars/grpc
+# contextPath: your project's route prefix through shenyu gateway, such as /order ，/product etc，gateway will route based on it.
+# appName：your project name,the default value is`spring.application.name`.
+# isFull: set true means providing proxy for your entire service, or only a few controller. apply to springmvc/springcloud
+```
+
+
+
+
+### Register different type API at same time
+
+> follow example use the http and dubbo.
+
+the `yml` configuration like follow:
+
+```yaml
+shenyu:
+ register:
+ registerType: http
+ serverLists: localhost:9195
+ props:
+ username: admin
+ password: 123456
+ client:
+ http:
+ props:
+ contextPath: /http
+ appName: http
+ port: 8188
+ isFull: false
+ dubbo:
+ props:
+ contextPath: /dubbo
+ appName: dubbo
+ port: 28080
+ props:
+ nacosNameSpace: ShenyuRegisterCenter
+# registerType : register type, set nacos
+# serverList: when register type is nacos, add nacos address list
+# http.port: your project port number; apply to springmvc
+# http.contextPath: your project's route prefix through shenyu gateway, such as /order ，/product etc，gateway will route based on it.
+# http.appName：your project name,the default value is`spring.application.name`.
+# http.isFull: set true means providing proxy for your entire service, or only a few controller. apply to springmvc/springcloud
+# dubbo.contextPath: your project dubbo service's context path
+# dubbo.port: your project dubbo rpc port
+# dubbo.appName: your project dubbo application name
+# nacosNameSpace: nacos namespace
+```
+
+In conclusion, this paper mainly describes how to connect your microservices (currently supporting `Http`, `Dubbo`, `Spring Cloud`, `gRPC`, `Motan`, `Sofa`, `Tars` and other protocols) to the `Apache ShenYu` gateway. the Apache ShenYu gateway support registry has `Http` This paper introduces the different ways to register configuration information when `Http` service is used as the client to access `Apache ShenYu` gateway.
+
diff --git a/versioned_docs/version-2.6.1/user-guide/property-config/register-center-instance.md b/versioned_docs/version-2.6.1/user-guide/property-config/register-center-instance.md
new file mode 100644
index 00000000000..0e41c573766
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/property-config/register-center-instance.md
@@ -0,0 +1,72 @@
+---
+title: Register Center Instance Config
+keywords: ["register center"]
+description: Register Instance
+---
+
+This document will introduce how to register the gateway instance to the registry. The `Apache ShenYu` gateway currently supports registration to `zookeeper` , `etcd` and `consul`.
+
+### Add Maven dependency
+
+First, introduce the following dependencies in the gateway's `pom.xml` file.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-registry
+ ${project.version}
+
+
+```
+
+### Use zookeeper
+
+> Please pay attention! From ShenYu 2.5.0, ShenYu will no longer support Zookeeper 3.4.x or below version. If you're already using Zookeeper, You need to use Zookeeper with a higher version and initialize the data.
+
+Add the following configuration to the gateway's `yml` file:
+
+```yaml
+registry:
+ enabled: true
+ registerType: zookeeper
+ serverLists: localhost:2181 #config with your zk address, used by the cluster environment, separated with (,).
+ props:
+ sessionTimeout: 3000 #Optional, default 3000
+ connectionTimeout: 3000 #Optional, default 3000
+```
+
+### Use etcd
+
+Add the following configuration to the gateway's `yml` file:
+
+```yaml
+registry:
+ enabled: true
+ registerType: etcd
+ serverLists: http://localhost:2379 #config with your etcd address, used by the cluster environment, separated with (,).
+ props:
+ etcdTimeout: 3000 #Optional, default 3000
+ etcdTTL: 5 #Optional, default 5
+```
+
+### Use apollo
+
+Add the following configuration to the gateway's `yml` file:
+
+```yaml
+registry:
+ enabled: true
+ registerType: apollo
+ serverLists: http://localhost:8080
+ props:
+ env: dev
+ appId: shenyu
+ namespace: application
+ clusterName: default
+ token: 0fff5645fc74ee5e0d63a6389433c8c8afc0beea31eed0279ecc1c8961d12da9
+ portalUrl: http://localhost:8070
+```
+
+
+> After the configuration is complete, start the gateway and it will successfully register to the corresponding registration center.
diff --git a/versioned_docs/version-2.6.1/user-guide/property-config/use-data-sync.md b/versioned_docs/version-2.6.1/user-guide/property-config/use-data-sync.md
new file mode 100644
index 00000000000..4aef68576a6
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/property-config/use-data-sync.md
@@ -0,0 +1,378 @@
+---
+title: Data Synchronization Config
+keywords: ["Data Synchronization"]
+description: use different data-sync strategy
+---
+
+This document focuses on how to use different data synchronization strategies. Data synchronization refers to the strategy used to synchronize data to ShenYu gateway after shenyu-admin background operation data. ShenYu gateway currently supports ZooKeeper, WebSocket, HTTP Long Polling, Nacos, Etcd and Consul for data synchronization.
+
+
+
+
+For details about the data synchronization principles, see [Data Synchronization Design](../../design/data-sync) in the design document.
+
+### WebSocket Synchronization Config（default strategy, recommend）
+
+* `Apache ShenYu` gateway config
+
+ Add these dependencies in `pom.xml`：
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-sync-data-websocket
+ ${project.version}
+
+```
+
+
+
+
+Add these config values in yaml file:
+
+```yaml
+shenyu:
+ sync:
+ websocket :
+ # urls: address of shenyu-admin，multi-address will be separated with (,).
+ urls: ws://localhost:9095/websocket
+ allowOrigin: ws://localhost:9195
+```
+
+
+
+* `shenyu-admin` config
+
+ Add these config values in yaml file:
+
+```yml
+shenyu:
+ sync:
+ websocket:
+ enabled: true
+```
+
+
+
+After the connection is established, the data will be fully obtained once, and the subsequent data will be updated and added increments, with good performance. It also supports disconnection (default: `30` seconds). This mode is recommended for data synchronization and is the default data synchronization strategy of ShenYu.
+
+### Zookeeper Synchronization Config
+
+> Please pay attention! From ShenYu 2.5.0, ShenYu will no longer support Zookeeper 3.4.x or below version. If you're already using Zookeeper, You need to use Zookeeper with a higher version and initialize the data.
+
+* `Apache ShenYu` gateway config
+
+ Add these dependencies in `pom.xml`：
+
+ ```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-sync-data-zookeeper
+ ${project.version}
+
+ ```
+
+
+
+
+Add these config values in yaml file:
+
+
+```yaml
+shenyu:
+ sync:
+ zookeeper:
+ url: localhost:2181
+ #url: config with your zk address, used by the cluster environment, separated with (,).
+ sessionTimeout: 5000
+ connectionTimeout: 2000
+```
+
+
+
+
+* `shenyu-admin` config
+
+Add these config values in yaml file:
+
+
+```yaml
+shenyu:
+ sync:
+ zookeeper:
+ url: localhost:2181
+ #url: config with your zk address, used by the cluster environment, separated with (,).
+ sessionTimeout: 5000
+ connectionTimeout: 2000
+```
+
+
+
+
+
+It is a good idea to use ZooKeeper synchronization mechanism with high timeliness, but we also have to deal with the unstable environment of ZK, cluster brain splitting and other problems.
+
+
+
+### HTTP Long Polling Synchronization Config
+
+* `Apache ShenYu` gateway config
+
+Add these dependencies in `pom.xml`：
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-sync-data-http
+ ${project.version}
+
+```
+
+
+
+
+Add these config values in yaml file:
+
+```yaml
+shenyu:
+ sync:
+ http:
+ url: http://localhost:9095
+ #url: config your shenyu-admin ip and port，cluster IP by split by (,)
+```
+
+
+
+
+* `shenyu-admin` config
+
+ Add these config values in yaml file:
+
+```yaml
+shenyu:
+ sync:
+ http:
+ enabled: true
+```
+
+
+
+
+HTTP long-polling makes the gateway lightweight, but less time-sensitive. It pulls according to the group key, if the data is too large, it will have some influences, a small change under a group will pull the entire group.
+
+
+
+### Nacos Synchronization Config
+
+* `Apache ShenYu` gateway config
+
+
+Add these dependencies in `pom.xml`：
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-sync-data-nacos
+ ${project.version}
+
+```
+
+
+
+
+Add these config values in yaml file:
+
+```yaml
+shenyu:
+ sync:
+ nacos:
+ url: localhost:8848
+ # url: config with your nacos address, please use (,) to split your cluster environment.
+ namespace: 1c10d748-af86-43b9-8265-75f487d20c6c
+ username:
+ password:
+ acm:
+ enabled: false
+ endpoint: acm.aliyun.com
+ namespace:
+ accessKey:
+ secretKey:
+ # other configure，please refer to the naocs website.
+```
+
+
+
+
+* `shenyu-admin` config
+
+ Add these config values in yaml file:
+
+```yaml
+shenyu:
+ sync:
+ nacos:
+ url: localhost:8848
+ namespace: 1c10d748-af86-43b9-8265-75f487d20c6c
+ username:
+ password:
+ acm:
+ enabled: false
+ endpoint: acm.aliyun.com
+ namespace:
+ accessKey:
+ secretKey:
+ # url: config with your nacos address, pls use (,) to split your cluster environment.
+ # other configure，pls refer to the naocs website.
+```
+
+
+
+
+### Etcd Synchronization Config
+
+* `Apache ShenYu` gateway config
+
+ Add these dependencies in `pom.xml`：
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-sync-data-etcd
+ ${project.version}
+
+
+ io.grpc
+ grpc-grpclb
+
+
+ io.grpc
+ grpc-netty
+
+
+
+```
+
+
+
+Add these config values in yaml file:
+
+```yaml
+shenyu:
+ sync:
+ etcd:
+ url: http://localhost:2379
+ #url: config with your etcd address, used by the cluster environment, separated with (,).
+```
+
+
+
+
+* `shenyu-admin` config
+
+ Add these config values in yaml file:
+
+```yaml
+shenyu:
+ sync:
+ etcd:
+ url: http://localhost:2379
+ #url: config with your etcd address, used by the cluster environment, separated with (,).
+```
+
+
+
+
+### Consul Synchronization Config
+
+* `Apache ShenYu` gateway config
+
+Add these dependencies in `pom.xml`：
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-sync-data-consul
+ ${project.version}
+
+```
+
+
+
+
+Add these config values in yaml file:
+
+```yaml
+shenyu:
+ sync:
+ consul:
+ url: http://localhost:8500
+ waitTime: 1000 # query wait time
+ watchDelay: 1000 # Data synchronization interval
+```
+
+
+
+
+* `shenyu-admin` config
+
+ Add these config values in yaml file:
+
+```yaml
+shenyu:
+ sync:
+ consul:
+ url: http://localhost:8500
+```
+
+
+
+### Apollo Synchronization Config
+
+Apollo just support Java [8,17), if you want to use apollo as data sync center, please make sure your JDK version is between [8,17).
+
+* `Apache ShenYu` gateway config
+
+Download the corresponding version of the jar package from `https://repo1.maven.org/maven2/org/apache/shenyu/shenyu-spring-boot-starter-sync-data-apollo/`, and then put the jar package into the `/lib` directory.
+
+Add these config values in yaml file:
+
+```yaml
+shenyu:
+ sync:
+ apollo:
+ appId: shenyu
+ meta: http://localhost:8080
+ env: dev
+ clusterName: test
+ namespace: application
+```
+
+* `Apache ShenYu Admin` config
+
+Download the corresponding version of the jar package from `https://repo1.maven.org/maven2/org/apache/shenyu/shenyu-admin-listener-apollo/`, and then put the jar package into the `/lib` directory.
+
+
+```yaml
+shenyu:
+ sync:
+ apollo:
+ meta: http://localhost:8080
+ appId: shenyu
+ portalUrl: http://localhost:8070
+ env: dev
+ clusterName: test
+ namespace: application
+ token: 0fff5645fc74ee5e0d63a6389433c8c8afc0beea31eed0279ecc1c8961d12da9
+```
+
+
+
+
+> After the data synchronization strategy of Apache ShenYu gateway and shenyu-admin is reconfigured, the microservice needs to be restarted.
+> the Apache ShenYu gateway and shenyu-admin must use the same synchronization strategy.
diff --git a/versioned_docs/version-2.6.1/user-guide/proxy/_category_.json b/versioned_docs/version-2.6.1/user-guide/proxy/_category_.json
new file mode 100644
index 00000000000..fce38607773
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/proxy/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Quick Connect to Your Service",
+ "position": 4
+}
diff --git a/versioned_docs/version-2.6.1/user-guide/proxy/dubbo-proxy.md b/versioned_docs/version-2.6.1/user-guide/proxy/dubbo-proxy.md
new file mode 100644
index 00000000000..2af957035f7
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/proxy/dubbo-proxy.md
@@ -0,0 +1,437 @@
+---
+title: Dubbo Proxy
+keywords: ["Dubbo"]
+description: Dubbo Client Access
+---
+
+This document is intended to help the `Dubbo` service access the `Apache ShenYu` gateway. The `Apache ShenYu` gateway uses the `Dubbo` plugin to handle `dubbo` service.
+
+Support Alibaba Dubbo(< 2.7.x) and Apache Dubbo (>=2.7.x).
+
+Before the connection, start `shenyu-admin` correctly, start `Dubbo` plugin, and add related dependencies on the gateway and `Dubbo` application client. Refer to the previous [Quick start with Dubbo](../../quick-start/quick-start-dubbo) .
+
+For details about client access configuration, see [Application Client Access Config](../property-config/register-center-access.md) .
+
+For details about data synchronization configurations, see [Data Synchronization Config](../property-config/use-data-sync.md) .
+
+## Add dubbo plugin in gateway
+
+Add these dependencies in gateway's `pom.xml`.
+
+Alibaba dubbo user, configure the dubbo version and registry center with yours.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-alibaba-dubbo
+ ${project.version}
+
+
+
+ com.alibaba
+ dubbo
+ 2.6.5
+
+
+ org.apache.curator
+ curator-client
+ 4.0.1
+
+
+ org.apache.curator
+ curator-framework
+ 4.0.1
+
+
+ org.apache.curator
+ curator-recipes
+ 4.0.1
+
+```
+
+Apache dubbo user, configure the dubbo version and registry center with yours.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-apache-dubbo
+ ${project.version}
+
+
+
+
+ org.apache.dubbo
+ dubbo
+ 2.7.5
+
+
+
+ org.apache.dubbo
+ dubbo-registry-nacos
+ 2.7.5
+
+
+ com.alibaba.nacos
+ nacos-client
+ 1.1.4
+
+
+
+
+
+ org.apache.curator
+ curator-client
+ 4.0.1
+
+
+ org.apache.curator
+ curator-framework
+ 4.0.1
+
+
+ org.apache.curator
+ curator-recipes
+ 4.0.1
+
+
+```
+
+* restart gateway service.
+
+## Dubbo service access gateway
+
+Dubbo integration with gateway, please refer to : [shenyu-examples-dubbo](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-dubbo) .
+
+* Alibaba Dubbo User
+ * SpringBoot
+
+ Add these dependencies:
+
+ ```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-alibaba-dubbo
+ ${shenyu.version}
+
+ ```
+
+ * Spring
+
+ Add these dependencies：
+
+ ```xml
+
+ org.apache.shenyu
+ shenyu-client-alibaba-dubbo
+ ${shenyu.version}
+
+ ```
+
+ Inject these properties into your Spring beans XML file：
+
+ ```xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ```
+
+* Apache Dubbo User
+
+ * SpringBoot
+
+ Add these dependencies:
+
+ ```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-apache-dubbo
+ ${shenyu.version}
+
+ ```
+
+ Add these in your client project's application.yml:
+
+ ```yml
+ dubbo:
+ registry:
+ address: dubbo register address
+ port: dubbo service port
+
+ shenyu:
+ register:
+ registerType: shenyu service register type #http #zookeeper #etcd #nacos #consul
+ serverLists: shenyu service register address #http://localhost:9095 #localhost:2181 #http://localhost:2379 #localhost:8848
+ client:
+ dubbo:
+ props:
+ contextPath: /your contextPath
+ appName: your app name
+ ```
+
+ * Spring
+
+ Add these dependencies:
+
+ ```xml
+
+ org.apache.shenyu
+ shenyu-client-apache-dubbo
+ ${shenyu.version}
+
+ ```
+
+ Injecct these properties into your Spring beans XML file:
+
+ ```xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ```
+
+ Add these in your client project's application.yml:
+
+ ```yml
+ dubbo:
+ registry:
+ address: dubbo register address
+ port: dubbo service port
+ ```
+
+## Dubbo configuration
+
+* Enable `dubbo` option in `shenyu-admin`.
+* Configure your registry address in `dubbo`.
+
+```yaml
+{"register":"zookeeper://localhost:2181"} or {"register":"nacos://localhost:8848"}
+```
+
+### Configure the interface with gateway
+
+* you can add the annotation `@ShenyuDubboClient` to your dubbo service implementation class, so that the interface method will be configured with gateway.
+
+* Start your provider. After successful startup, go to PluginList -> rpc Proxy -> dubbo in the backend management system. You will see auto-registered selectors and rules information.
+
+### Dubbo user request and parameter explanation.
+
+* Communicate with dubbo service through Http transport protocol.
+* Apache ShenYu gateway need a route prefix which configured when accessing the project.
+
+```yaml
+# for example: you have an order service and it has a interface, registry address: /order/test/save
+
+# now we can communicate with gateway through POST request http://localhost:9195/order/test/save
+
+# localhost:9195 is gateway's ip port，default port is 9195 ，/order is the contextPath you set through gateway.
+```
+
+* parameter deliver:
+ * communicate with gateway through body or json of http post request.
+ * more parameter types, please refer to the interface definition in [shenyu-examples-dubbo](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-dubbo) and parameter passing
+ method.
+* Single java bean parameter type (`default`).
+* Multi-parameter type support, add this config value in gateway's yaml file:
+
+```yaml
+shenyu:
+ dubbo:
+ parameter: multi
+```
+
+* Support for customized multi-parameter type
+* Create a new implementation class `MyDubboParamResolveService` in your gateway project of `org.apache.shenyu.web.dubbo.DubboParamResolveService`.
+
+```java
+public interface DubboParamResolveService {
+
+ /**
+ * Build parameter pair.
+ * this is Resolve http body to get dubbo param.
+ *
+ * @param body the body
+ * @param parameterTypes the parameter types
+ * @return the pair
+ */
+ Pair buildParameter(String body, String parameterTypes);
+}
+```
+
+* `body` is the json string in http request.
+* `parameterTypes`: the list of method parameter types that are matched，split with `,`.
+* in Pair，left is parmeter type，right is parameter value, it's the standard of dubbo generalization calls.
+* Inject your class into Spring bean, cover the default implementation.
+
+```java
+@Bean
+public DubboParamResolveService myDubboParamResolveService() {
+ return new MyDubboParamResolveService();
+}
+```
+
+## Service governance
+
+* Tag route
+ * Add `Dubbo_Tag_Route` when send request, the current request will be routed to the provider of the specified tag, which is only valid for the current request.
+* Explicit Target
+ * Set the `url` property in the annotation `@ShenyuDubboClient`.
+ * Update the configuration in Admin.
+ * It's valid for all request.
+* Param valid and ShenyuException
+ * Set `validation="shenyuValidation"`.
+ * When `ShenyuException` is thrown in the interface, exception information will be returned. It should be noted that `ShenyuException` is thrown explicitly.
+
+ ```java
+ @Service(validation = "shenyuValidation")
+ public class TestServiceImpl implements TestService {
+
+ @Override
+ @ShenyuDubboClient(path = "/test", desc = "test method")
+ public String test(@Valid HelloServiceRequest name) throws ShenyuException {
+ if (true){
+ throw new ShenyuException("Param binding error.");
+ }
+ return "Hello " + name.getName();
+ }
+ }
+ ```
+
+ * Request param
+
+ ```java
+ public class HelloServiceRequest implements Serializable {
+
+ private static final long serialVersionUID = -5968745817846710197L;
+
+ @NotEmpty(message = "name cannot be empty")
+ private String name;
+
+ @NotNull(message = "age cannot be null")
+ private Integer age;
+
+ public String getName() {
+ return name;
+ }
+
+ public void setName(String name) {
+ this.name = name;
+ }
+
+ public Integer getAge() {
+ return age;
+ }
+
+ public void setAge(Integer age) {
+ this.age = age;
+ }
+ }
+ ```
+
+ * Send request
+
+ ```json
+ {
+ "name": ""
+ }
+ ```
+
+ * Response
+
+ ```json
+ {
+ "code": 500,
+ "message": "Internal Server Error",
+ "data": "name cannot be empty,age cannot be null"
+ }
+ ```
+
+ * Error message
+
+ ```json
+ {
+ "code": 500,
+ "message": "Internal Server Error",
+ "data": "Param binding error."
+ }
+ ```
+
+
+## Http --> Gateway --> Dubbo Provider
+
+It basically switches from HTTP request to Dubbo protocol, then invoke Dubbo service and return to the result.
+Two things need to notice after intgeration with gateway, one is the added annoation `@ShenyuDubboClient`, another is a path used to speicify the request path.
+And you added a config value of `contextPath`.
+
+If you have a function like this, the config value in contextPath is `/dubbo`
+
+```java
+ @Override
+ @ShenyuDubboClient(path = "/insert", desc = "insert data")
+ public DubboTest insert(final DubboTest dubboTest) {
+ return dubboTest;
+ }
+```
+
+So our request path is: http://localhost:9195/dubbo/insert, localhost:9195 is the gateway's domain name,if you changed before,so does with yours here..
+
+`DubboTest` is a java bean object，has 2 parameters, id and name, so we can transfer the value's json type through request body.
+
+```
+{"id":"1234","name":"XIAO5y"}
+```
+
+If your interface has no parameter, then the value is:
+
+```
+{}
+```
+
+If the interface has multiple parameters, refer to the multi-parameter type support described above.
diff --git a/versioned_docs/version-2.6.1/user-guide/proxy/grpc-proxy.md b/versioned_docs/version-2.6.1/user-guide/proxy/grpc-proxy.md
new file mode 100644
index 00000000000..6a05c604c18
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/proxy/grpc-proxy.md
@@ -0,0 +1,197 @@
+---
+title: gRPC Proxy
+keywords: ["gRPC"]
+description: gRPC access shenyu gateway
+---
+
+This document is intended to help the `gRPC` service access the `Apache ShenYu` gateway. The `Apache ShenYu` gateway uses the `gRPC` plugin to handle `gRPC` service.
+
+Before the connection, start `shenyu-admin` correctly, start `gRPC` plugin, and add related dependencies on the gateway and `gRPC` application client. Refer to the previous [Quick start with gRPC](../quick-start/quick-start-grpc) .
+
+For details about client access configuration, see [Application Client Access Config](../property-config/register-center-access.md) .
+
+For details about data synchronization configurations, see [Data Synchronization Config](../property-config/use-data-sync.md) .
+
+## Add gRPC plugin in gateway
+
+Add the following dependencies in the gateway's `pom.xml` file:
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-grpc
+ ${project.version}
+
+
+```
+
+* Restart the gateway service.
+
+## gRPC service access gateway
+
+You can refer to：[shenyu-examples-grpc](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-grpc) .
+
+1. In the microservice built by `gRPC`, add the following dependencies:
+
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-grpc
+ ${shenyu.version}
+
+
+ guava
+ com.google.guava
+
+
+
+```
+
+Execute command to generate java code in `shenyu-examples-grpc` project.
+
+```shell
+mvn protobuf:compile
+mvn protobuf:compile-custom
+```
+
+2. Add the following configuration to application.yaml:
+
+```yaml
+shenyu:
+ register:
+ registerType: http #zookeeper #etcd #nacos #consul
+ serverLists: http://localhost:9095 #localhost:2181 #http://localhost:2379 #localhost:8848
+ props:
+ username: admin
+ password: 123456
+ client:
+ grpc:
+ props:
+ contextPath: /grpc
+ appName: grpc
+ ipAndPort: 127.0.0.1:38080
+ port: 38080
+```
+
+3. Add `@ShenyuGrpcClient` Annotation on the `gRPC` service interface implementation class. Start your service provider, after successful registration, in the background management system go to PluginList -> rpc proxy -> gRPC, you will see automatic registration of selectors and rules information.
+
+Example:
+
+```java
+ @Override
+ @ShenyuGrpcClient(path = "/echo", desc = "echo")
+ public void echo(EchoRequest request, StreamObserver responseObserver) {
+ System.out.println("Received: " + request.getMessage());
+ EchoResponse.Builder response = EchoResponse.newBuilder()
+ .setMessage("ReceivedHELLO")
+ .addTraces(Trace.newBuilder().setHost(getHostname()).build());
+ responseObserver.onNext(response.build());
+ responseObserver.onCompleted();
+ }
+
+```
+
+## User Request
+
+You can request your gRPC service by Http. The `Apache ShenYu` gateway needs to have a route prefix that you access to configure `contextPath`.
+
+
+
+If your `proto` file is defined as follows:
+
+
+```protobuf
+message EchoRequest {
+ string message = 1;
+}
+```
+
+So the request parameters look like this:
+
+```json
+{
+ "data": [
+ {
+ "message": "hello grpc"
+ }
+ ]
+}
+```
+
+The parameters are currently passed in `json` format, and the name of `key` defaults to `data`, which you can reset in `GrpcConstants.JSON_DESCRIPTOR_PROTO_FIELD_NAME`; The `value` is passed in according to the `proto` file you define.
+
+
+the Apache ShenYu can support streaming calls to `gRPC` service, passing multiple arguments in the form of an array.
+
+If your `proto` file is defined as follows:
+
+```protobuf
+message RequestData {
+ string text = 1;
+}
+```
+
+The corresponding method call request parameters are as follows:
+
+- `UNARY`
+
+```json
+{
+ "data": [
+ {
+ "text": "hello grpc"
+ }
+ ]
+}
+```
+
+- `CLIENT_STREAMING`
+
+```json
+{
+ "data": [
+ {
+ "text": "hello grpc"
+ },
+ {
+ "text": "hello grpc"
+ },
+ {
+ "text": "hello grpc"
+ }
+ ]
+}
+```
+
+- `SERVER_STREAMING`
+
+
+```json
+{
+ "data": [
+ {
+ "text": "hello grpc"
+ }
+ ]
+}
+```
+
+- `BIDI_STREAMING`
+
+```json
+{
+ "data": [
+ {
+ "text": "hello grpc"
+ },
+ {
+ "text": "hello grpc"
+ },
+ {
+ "text": "hello grpc"
+ }
+ ]
+}
+```
diff --git a/versioned_docs/version-2.6.1/user-guide/proxy/http-proxy.md b/versioned_docs/version-2.6.1/user-guide/proxy/http-proxy.md
new file mode 100644
index 00000000000..9dc9783e685
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/proxy/http-proxy.md
@@ -0,0 +1,262 @@
+---
+title: Http Proxy
+keywords: ["Http"]
+description: Integrate Http with shenyu gateway
+---
+
+
+This document is intended to help the `Http` service access the `Apache ShenYu` gateway. The `Apache ShenYu` gateway uses the `Divide` plugin to handle `Http` requests.
+
+Before the connection, start `shenyu-admin` correctly, start `Divide` plugin, and add related dependencies on the gateway and `Http` application client. Refer to the previous [Quick start with Http](../../quick-start/quick-start-http) .
+
+For details about client access configuration, see [Application Client Access Config](../property-config/register-center-access.md) .
+
+For details about data synchronization configurations, see [Data Synchronization Config](../property-config/use-data-sync.md) .
+
+## Add divide plugin in gateway
+
+* Add the following dependencies to the gateway's `pom.xml` file:
+
+ ```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-divide
+ ${project.version}
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-httpclient
+ ${project.version}
+
+ ```
+
+## Http request access gateway (for springMvc)
+
+* SpringBoot
+
+ Please refer this：[shenyu-examples-http](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http)
+
+ 1. Add the following dependencies to the `pom.xml` file in your `Http` service:
+
+ ```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-springmvc
+ ${shenyu.version}
+
+ ```
+
+ 2. Add the following configuration to application.yaml:
+
+ ```yaml
+ shenyu:
+ register:
+ registerType: http #zookeeper #etcd #nacos #consul
+ serverLists: http://localhost:9095 #localhost:2181 #http://localhost:2379 #localhost:8848
+ props:
+ username: admin
+ password: 123456
+ client:
+ http:
+ props:
+ contextPath: /http
+ appName: http
+ # port: 8189
+ ```
+
+* SpringMvc
+
+ Please refer this：[shenyu-examples-springmvc](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-springmvc)
+
+ Add the following dependencies to the `pom.xml` file in your `Http` service:
+
+ ```xml
+
+ org.apache.shenyu
+ shenyu-client-springmvc
+ ${shenyu.version}
+
+ ```
+
+ Add the following to the `XML` file defined by your `bean` :
+
+ ```xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ```
+
+ Add this annotation `@ShenyuSpringMvcClient` in your `controller` interface.
+
+ You can apply the annotation to class-level in a controller. The name of the `path` variable is prefix and `/**` will apply proxy for entire interfaces.
+
+
+Example(1)
+
+The following indicates that `/test/payment`, `/test/findByUserId` will be proxy by the gateway.
+
+```java
+ @RestController
+ @RequestMapping("/test")
+ @ShenyuSpringMvcClient(path = "/test/**")
+ public class HttpTestController {
+
+ @PostMapping("/payment")
+ public UserDTO post(@RequestBody final UserDTO userDTO) {
+ return userDTO;
+ }
+
+ @GetMapping("/findByUserId")
+ public UserDTO findByUserId(@RequestParam("userId") final String userId) {
+ UserDTO userDTO = new UserDTO();
+ userDTO.setUserId(userId);
+ userDTO.setUserName("hello world");
+ return userDTO;
+ }
+ }
+```
+
+
+
+Example(2)
+
+
+The following indicates that `/order/save` is proxied by the gateway, while `/order/findById` is not.
+
+
+```java
+ @RestController
+ @RequestMapping("/order")
+ @ShenyuSpringMvcClient(path = "/order")
+ public class OrderController {
+
+ @PostMapping("/save")
+ @ShenyuSpringMvcClient(path = "/save")
+ public OrderDTO save(@RequestBody final OrderDTO orderDTO) {
+ orderDTO.setName("hello world save order");
+ return orderDTO;
+ }
+
+ @GetMapping("/findById")
+ public OrderDTO findById(@RequestParam("id") final String id) {
+ OrderDTO orderDTO = new OrderDTO();
+ orderDTO.setId(id);
+ orderDTO.setName("hello world findById");
+ return orderDTO;
+ }
+ }
+```
+
+example (3)：This is a simplified way to use it, just need a simple annotation to register to the gateway using metadata.
+Special note: currently only supports `@RequestMapping, @GetMapping, @PostMapping, @DeleteMapping, @PutMapping` annotations, and only valid for the first path in `@XXXMapping`
+
+```java
+ @RestController
+ @RequestMapping("new/feature")
+ public class NewFeatureController {
+
+ /**
+ * no support gateway access api.
+ *
+ * @return result
+ */
+ @RequestMapping("/gateway/not")
+ public EntityResult noSupportGateway() {
+ return new EntityResult(200, "no support gateway access");
+ }
+
+ /**
+ * Do not use shenyu annotation path. used request mapping path.
+ *
+ * @return result
+ */
+ @RequestMapping("/requst/mapping/path")
+ @ShenyuSpringCloudClient
+ public EntityResult requestMappingUrl() {
+ return new EntityResult(200, "Do not use shenyu annotation path. used request mapping path");
+ }
+
+ /**
+ * Do not use shenyu annotation path. used post mapping path.
+ *
+ * @return result
+ */
+ @PostMapping("/post/mapping/path")
+ @ShenyuSpringCloudClient
+ public EntityResult postMappingUrl() {
+ return new EntityResult(200, "Do not use shenyu annotation path. used post mapping path");
+ }
+
+ /**
+ * Do not use shenyu annotation path. used post mapping path.
+ *
+ * @return result
+ */
+ @GetMapping("/get/mapping/path")
+ @ShenyuSpringCloudClient
+ public EntityResult getMappingUrl() {
+ return new EntityResult(200, "Do not use shenyu annotation path. used get mapping path");
+ }
+ }
+
+```
+
+* Start your project, your service interface is connected to the gateway, go to the `shenyu-admin` management system plugin list `->` HTTP process `->` Divide, see automatically created selectors and rules.
+
+
+## Http request access gateway(other framework)
+
+* First, find `divide` plugin in `shenyu-admin`, add selector, and rules, and filter traffic matching.
+* If you don't know how to configure, please refer to [Selector Detailed Explanation](../admin-usage/selector-and-rule).
+* You can also develop your customized http-client，refer to [multi-language Http client development](../../developer/developer-shenyu-client)。
+
+## User request
+
+* Send the request as before, only two points need to notice.
+* Firstly, the domain name that requested before in your service, now need to replace with gateway's domain name.
+* Secondly, `Apache ShenYu` Gateway needs a route prefix which comes from `contextPath`, it configured during the integration with gateway, you can change it freely in `divide` plugin of `shenyu-admin`, if you are familiar with it.
+ * for example, if you have an `order` service, and it has an interface, the request url: `http://localhost:8080/test/save`
+
+ * Now need to change to: `http://localhost:9195/order/test/save`
+
+ * We can see `localhost:9195` is your gateway's `ip` port，default port number is `9195` ，`/order` is your `contextPath` which you configured with gateway.
+
+ * Other parameters doesn't change in request method.
+
+
+* Then you can visit, very easy and simple.
diff --git a/versioned_docs/version-2.6.1/user-guide/proxy/motan-proxy.md b/versioned_docs/version-2.6.1/user-guide/proxy/motan-proxy.md
new file mode 100644
index 00000000000..d1bf0cadd54
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/proxy/motan-proxy.md
@@ -0,0 +1,107 @@
+---
+title: Motan Proxy
+description: Motan Proxy
+---
+
+This document is intended to help the `Motan` service access the `Apache ShenYu` gateway. The `Apache ShenYu` gateway uses the `Motan` plugin to handle `motan` service.
+
+Before the connection, start `shenyu-admin` correctly, start `Motan` plugin, and add related dependencies on the gateway and `Motan` application client. Refer to the previous [Quick start with Motan](../quick-start/quick-start-motan) .
+
+For details about client access configuration, see [Application Client Access Config](../property-config/register-center-access.md) .
+
+For details about data synchronization configurations, see [Data Synchronization Config](../property-config/use-data-sync.md) .
+
+## Add motan plugin in gateway
+
+Add the following dependencies to the gateway's `pom.xml` file:
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-motan
+ ${project.version}
+
+
+ com.weibo
+ motan-core
+ 1.1.9
+
+
+ com.weibo
+ motan-registry-zookeeper
+ 1.1.9
+
+
+ com.weibo
+ motan-transport-netty4
+ 1.1.9
+
+
+ com.weibo
+ motan-springsupport
+ 1.1.9
+
+```
+
+* Restart your gateway service.
+
+## Motan service access gateway
+
+Please refer to: [shenyu-examples-motan](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-motan)
+
+1. In the microservice built by `Motan`, add the following dependencies:
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-motan
+ ${shenyu.version}
+
+```
+
+2. Add the following configuration to the `application.yaml` configuration file:
+
+```yaml
+shenyu:
+ register:
+ registerType: http #zookeeper #etcd #nacos #consul
+ serverLists: http://localhost:9095 #localhost:2181 #http://localhost:2379 #localhost:8848
+ props:
+ username: admin
+ password: 123456
+ client:
+ motan:
+ props:
+ contextPath: /motan
+ ipAndPort: motan
+ appName: motan
+ port: 8081
+ package-path: org.apache.shenyu.examples.motan.service
+ basicServiceConfig:
+ exportPort: 8002
+motan:
+ registry:
+ protocol: zookeeper
+ address: 127.0.0.1:2181
+```
+
+
+3. Add `@ShenyuMotanClient` annotation to the method of `Motan` service interface implementation class, start your service provider, after successful registration, go to PluginList -> rpc proxy -> motan in the background management system, you will see automatic registration of selectors and rules information.
+
+Example:
+
+```java
+@MotanService(export = "demoMotan:8002")
+public class MotanDemoServiceImpl implements MotanDemoService {
+ @Override
+ @ShenyuMotanClient(path = "/hello")
+ public String hello(String name) {
+ return "hello " + name;
+ }
+}
+```
+
+## User Request
+
+You can request your `motan` service by Http. The `Apache ShenYu` gateway needs to have a route prefix which is the `contextPath` configured by the access gateway. For example: `http://localhost:9195/motan/hello` .
diff --git a/versioned_docs/version-2.6.1/user-guide/proxy/sofa-rpc-proxy.md b/versioned_docs/version-2.6.1/user-guide/proxy/sofa-rpc-proxy.md
new file mode 100644
index 00000000000..e9494c921c9
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/proxy/sofa-rpc-proxy.md
@@ -0,0 +1,187 @@
+---
+title: Sofa Proxy
+keywords: ["Sofa"]
+description: sofa access shenyu gateway
+---
+
+This document is intended to help the `Sofa` service access the `Apache ShenYu` gateway. The `Apache ShenYu` gateway uses the `Sofa` plugin to handle `sofa` service.
+
+Before the connection, start `shenyu-admin` correctly, start `Sofa` plugin, and add related dependencies on the gateway and `Sofa` application client. Refer to the previous [Quick start with Sofa](../quick-start/quick-start-sofa) .
+
+For the use of the plugin, see：[Sofa Plugin](../../plugin-center/proxy/sofa-plugin.md)
+
+For details about client access configuration, see [Application Client Access Config](../property-config/register-center-access.md) .
+
+For details about data synchronization configurations, see [Data Synchronization Config](../property-config/use-data-sync.md) .
+
+## Add sofa plugin in gateway
+
+> In the current version, this dependency has been introduced by default.
+
+1. Add the following dependencies in the gateway's `pom.xml` file：
+
+ ```xml
+
+ com.alipay.sofa
+ sofa-rpc-all
+ 5.7.6
+
+
+ net.jcip
+ jcip-annotations
+
+
+
+
+ org.apache.curator
+ curator-client
+ 4.0.1
+
+
+ org.apache.curator
+ curator-framework
+ 4.0.1
+
+
+ org.apache.curator
+ curator-recipes
+ 4.0.1
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-sofa
+ ${project.version}
+
+ ```
+
+2. Restart the gateway service.
+
+## Sofa service access gateway
+
+Please refer to：[shenyu-examples-sofa](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-sofa)
+
+1. Based on the `springboot` project，Introduce the following dependencies：
+
+ ```xml
+
+ com.alipay.sofa
+ rpc-sofa-boot-starter
+ ${rpc-sofa-boot-starter.version}
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-sofa
+ ${shenyu.version}
+
+ ```
+
+2. Configure in application.yml
+
+```yaml
+com:
+ alipay:
+ sofa:
+ rpc:
+ registry-address: zookeeper://127.0.0.1:2181 # consul # nacos
+ bolt-port: 8888
+shenyu:
+ register:
+ registerType: http #zookeeper #etcd #nacos #consul
+ serverLists: http://localhost:9095 #localhost:2181 #http://localhost:2379 #localhost:8848
+ props:
+ username: admin
+ password: 123456
+ client:
+ sofa:
+ props:
+ contextPath: /sofa
+ ipAndPort: sofa
+ appName: sofa
+ port: 8888
+```
+
+3. Configure the service interface exposed by the sofa service in the xml file in the resources.
+
+```xml
+
+
+
+
+
+
+
+
+```
+
+4. Add the `@ShenyuSofaClient` annotation to the interface
+
+```java
+@ShenyuSofaClient("/demo")
+@Service
+public class SofaClientMultiParamServiceImpl implements SofaClientMultiParamService {
+
+ @Override
+ @ShenyuSofaClient("/findByIdsAndName")
+ public SofaSimpleTypeBean findByIdsAndName(final List ids, final String name) {
+ return new SofaSimpleTypeBean(ids.toString(), "hello world shenyu sofa param findByIdsAndName ：" + name);
+ }
+}
+```
+
+5. Start the `sofa` service, and after successful registration:
+- Go to `PluginList -> Proxy -> Sofa` in the backend management system, you will see the information of auto-registered selectors and rules.
+- Go to `BasicConfig -> Metadata` and search by app name . You will see the metadata of sofa, each `sofa` interface method, will correspond to a metadata.
+
+## User request and parameter description
+
+- The gateway can be requested by means of `http` to request your `sofa` service.
+ - ShenYu gateway needs to have a routing prefix, this routing prefix is for you to access the project for configuration `contextPath` .
+
+> For example, if you have an `order` service, it has an interface and its registration path `/order/test/save`
+>
+> Now it's to request the gateway via post：`http://localhost:9195/order/test/save`
+>
+> Where `localhost:9195` is the IP port of the gateway, default port is `9195`, `/order` is the `contextPath` of your sofa access gateway configuration.
+
+
+* Parameter passing：
+ - Access the gateway through http post，and pass through body and json.
+ - For more parameter type transfer, please refer to the interface definition in [shenyu-examples-sofa](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-sofa) and the parameter transfer method.
+
+* Single java bean parameter type (default)
+* Customize multi-parameter support:
+* In the gateway project you built, add a new class `MySofaParamResolveService`, implements `org.apache.shenyu.plugin.api.sofa.SofaParamResolveService` .
+
+ ```java
+ public interface SofaParamResolveService {
+
+ /**
+ * Build parameter pair.
+ * this is Resolve http body to get sofa param.
+ *
+ * @param body the body
+ * @param parameterTypes the parameter types
+ * @return the pair
+ */
+ Pair buildParameter(String body, String parameterTypes);
+ }
+ ```
+
+* `body` is the json string passed by body in http.
+* `parameterTypes`: list of matched method parameter types, If there are multiple, use `,` to separate.
+* In Pair，left is the parameter type，and right is the parameter value. This is the standard for sofa generalization calls.
+* Register your class as a String bean and override the default implementation.
+
+ ```java
+ @Bean
+ public SofaParamResolveService mySofaParamResolveService() {
+ return new MySofaParamResolveService();
+ }
+ ```
+
+
diff --git a/versioned_docs/version-2.6.1/user-guide/proxy/spring-cloud-proxy.md b/versioned_docs/version-2.6.1/user-guide/proxy/spring-cloud-proxy.md
new file mode 100644
index 00000000000..62e5bf93871
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/proxy/spring-cloud-proxy.md
@@ -0,0 +1,300 @@
+---
+title: Spring Cloud Proxy
+keywords: ["Spring Cloud"]
+description: springCloud with shenyu gateway
+---
+
+This document is intended to help the `Spring Cloud` service access the `Apache ShenYu` gateway. The `Apache ShenYu` gateway uses the `springCloud` plugin to handle `Spring Cloud` service.
+
+Before the connection, start `shenyu-admin` correctly, start `springCloud` plugin, and add related dependencies on the gateway and `springCloud` application client. Refer to the previous [Quick start with Spring Cloud](../quick-start/quick-start-springcloud) .
+
+For details about client access configuration, see [Application Client Access Config](../property-config/register-center-access.md) .
+
+For details about data synchronization configurations, see [Data Synchronization Config](../property-config/use-data-sync.md) .
+
+
+## Add springcloud plugin in gateway
+
+* add these dependencies in gateway's pom.xml:
+
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-springcloud
+ ${project.version}
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-httpclient
+ ${project.version}
+
+
+
+
+ org.springframework.cloud
+ spring-cloud-commons
+ 2.2.0.RELEASE
+
+```
+
+* If you use `eureka` as SpringCloud registry center.
+
+ add these dependencies:
+
+ ```xml
+
+ org.springframework.cloud
+ spring-cloud-starter-netflix-eureka-client
+ 2.2.0.RELEASE
+
+ ```
+
+add these config values in gateway's yaml file:
+
+ ```yaml
+ eureka:
+ client:
+ serviceUrl:
+ defaultZone: http://localhost:8761/eureka/ #your eureka address
+ instance:
+ prefer-ip-address: true
+ ```
+
+* if you use `nacos` as Spring Cloud registry center.
+
+ add these dependencies:
+
+ ```xml
+
+ com.alibaba.cloud
+ spring-cloud-starter-alibaba-nacos-discovery
+ 2.1.0.RELEASE
+
+ ```
+
+add these config values in gateway's yaml file:
+
+ ```yaml
+ spring:
+ cloud:
+ nacos:
+ discovery:
+ server-addr: 127.0.0.1:8848 # your nacos address
+ ```
+
+Special note: Please ensure that the spring Cloud registry service discovery configuration is enabled
+
+* Configuration method
+
+```yml
+spring:
+ cloud:
+ discovery:
+ enabled: true
+```
+
+* code method
+
+```java
+@SpringBootApplication
+@EnableDiscoveryClient
+public class ShenyuBootstrapApplication {
+
+ /**
+ * Main Entrance.
+ *
+ * @param args startup arguments
+ */
+ public static void main(final String[] args) {
+ SpringApplication.run(ShenyuBootstrapApplication.class, args);
+ }
+}
+```
+
+* restart your gateway service.
+
+## SpringCloud service access gateway
+
+Please refer to [shenyu-examples-springcloud](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-springcloud)
+
+* Add the following dependencies to your `Spring Cloud` microservice :
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-springcloud
+ ${shenyu.version}
+
+```
+
+* Add the annotation `@ShenyuSpringCloudClient` in your `controller` interface. you can apply the annotation to class-level in a controller.the name of the path variable is prefix and '/**' will apply proxy for entire interfaces.
+
+* example (1)：both `/test/payment` and `/test/findByUserId` will be handled by gateway.
+
+ ```java
+ @RestController
+ @RequestMapping("/test")
+ @ShenyuSpringCloudClient(path = "/test/**")
+ public class HttpTestController {
+
+ @PostMapping("/payment")
+ public UserDTO post(@RequestBody final UserDTO userDTO) {
+ return userDTO;
+ }
+
+ @GetMapping("/findByUserId")
+ public UserDTO findByUserId(@RequestParam("userId") final String userId) {
+ UserDTO userDTO = new UserDTO();
+ userDTO.setUserId(userId);
+ userDTO.setUserName("hello world");
+ return userDTO;
+ }
+ }
+```
+
+example (2)：`/order/save` will be handled by gateway, and `/order/findById` won't.
+
+ ```java
+ @RestController
+ @RequestMapping("/order")
+ @ShenyuSpringCloudClient(path = "/order")
+ public class OrderController {
+
+ @PostMapping("/save")
+ @ShenyuSpringMvcClient(path = "/save")
+ public OrderDTO save(@RequestBody final OrderDTO orderDTO) {
+ orderDTO.setName("hello world save order");
+ return orderDTO;
+ }
+
+ @GetMapping("/findById")
+ public OrderDTO findById(@RequestParam("id") final String id) {
+ OrderDTO orderDTO = new OrderDTO();
+ orderDTO.setId(id);
+ orderDTO.setName("hello world findById");
+ return orderDTO;
+ }
+ }
+```
+
+example (3)： `isFull`：`true` represents that all service will be represented by the gateway.
+
+```yaml
+shenyu:
+ register:
+ registerType: http #zookeeper #etcd #nacos #consul
+ serverLists: http://localhost:9095 #localhost:2181 #http://localhost:2379 #localhost:8848
+ props:
+ username: admin
+ password: 123456
+ client:
+ springCloud:
+ props:
+ contextPath: /springcloud
+ isFull: true
+# port: 8884
+# registerType : service registre type, see the application client access document
+# serverList: server list, see the application client access document
+# contextPath: route prefix for your project in ShenYu gateway.
+# isFull: set true to proxy your all service and false to proxy some of your controllers
+```
+
+ ```java
+ @RestController
+ @RequestMapping("/order")
+ public class OrderController {
+
+ @PostMapping("/save")
+ @ShenyuSpringMvcClient(path = "/save")
+ public OrderDTO save(@RequestBody final OrderDTO orderDTO) {
+ orderDTO.setName("hello world save order");
+ return orderDTO;
+ }
+
+ @GetMapping("/findById")
+ public OrderDTO findById(@RequestParam("id") final String id) {
+ OrderDTO orderDTO = new OrderDTO();
+ orderDTO.setId(id);
+ orderDTO.setName("hello world findById");
+ return orderDTO;
+ }
+ }
+```
+
+example (4)：This is a simplified way to use it, just need a simple annotation to register to the gateway using metadata.
+Special note: currently only supports `@RequestMapping, @GetMapping, @PostMapping, @DeleteMapping, @PutMapping` annotations, and only valid for the first path in `@XXXMapping`.
+
+```java
+ @RestController
+ @RequestMapping("new/feature")
+ public class NewFeatureController {
+
+ /**
+ * no support gateway access api.
+ *
+ * @return result
+ */
+ @RequestMapping("/gateway/not")
+ public EntityResult noSupportGateway() {
+ return new EntityResult(200, "no support gateway access");
+ }
+
+ /**
+ * Do not use shenyu annotation path. used request mapping path.
+ *
+ * @return result
+ */
+ @RequestMapping("/requst/mapping/path")
+ @ShenyuSpringCloudClient
+ public EntityResult requestMappingUrl() {
+ return new EntityResult(200, "Do not use shenyu annotation path. used request mapping path");
+ }
+
+ /**
+ * Do not use shenyu annotation path. used post mapping path.
+ *
+ * @return result
+ */
+ @PostMapping("/post/mapping/path")
+ @ShenyuSpringCloudClient
+ public EntityResult postMappingUrl() {
+ return new EntityResult(200, "Do not use shenyu annotation path. used post mapping path");
+ }
+
+ /**
+ * Do not use shenyu annotation path. used post mapping path.
+ *
+ * @return result
+ */
+ @GetMapping("/get/mapping/path")
+ @ShenyuSpringCloudClient
+ public EntityResult getMappingUrl() {
+ return new EntityResult(200, "Do not use shenyu annotation path. used get mapping path");
+ }
+ }
+
+```
+
+* After successfully registering your service, go to the backend management system PluginList -> rpc proxy -> springCloud ', you will see the automatic registration of selectors and rules information.
+
+
+
+## User Request
+
+* Send the request as before, only two points need to notice.
+
+* firstly,the domain name that requested before in your service, now need to replace with gateway's domain name.
+
+* secondly, Apache ShenYu gateway needs a route prefix which comes from `contextPath`, it configured during the integration with gateway, you can change it freely in divide plugin of `shenyu-admin`, if your familiar with it.
+
+> For example, your have an `order` service and it has a interface, the request url: `http://localhost:8080/test/save` .
+>
+> Now need to change to：`http://localhost:9195/order/test/save` .
+>
+> We can see `localhost:9195` is the gateway's ip port, default port number is `9195` , `/order` is the `contextPath` in your config yaml file.
+>
+> The request of other parameters doesn't change. Then you can visit, very easy and simple.
+
diff --git a/versioned_docs/version-2.6.1/user-guide/proxy/tars-proxy.md b/versioned_docs/version-2.6.1/user-guide/proxy/tars-proxy.md
new file mode 100644
index 00000000000..8f1fec4853b
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/proxy/tars-proxy.md
@@ -0,0 +1,98 @@
+---
+title: Tars Proxy
+description: Tars Proxy
+---
+
+This document is intended to help the `Tars` service access the `Apache ShenYu` gateway. The `Apache ShenYu` gateway uses the `tars` plugin to handle `tars` service.
+
+Before the connection, start `shenyu-admin` correctly, start `tars` plugin, and add related dependencies on the gateway and `tars` application client. Refer to the previous [Quick start with Tars](../quick-start/quick-start-tars) .
+
+For details about client access configuration, see [Application Client Access Config](../property-config/register-center-access.md) .
+
+For details about data synchronization configurations, see [Data Synchronization Config](../property-config/use-data-sync.md)).
+
+
+## Add tars plugin in gateway
+
+
+Add the following dependencies to the gateway's `pom.xml` file:
+
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-tars
+ ${project.version}
+
+
+
+ com.tencent.tars
+ tars-client
+ 1.7.2
+
+
+```
+
+* Restart your gateway service.
+
+## Tars service access gateway
+
+Please refer to： [shenyu-examples-tars](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-tars)
+
+1. In the microservice built by `Tars`, add the following dependencies:
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-tars
+ ${shenyu.version}
+
+```
+
+2. Add the following configuration to the `application.yaml` configuration file:
+
+```yaml
+shenyu:
+ register:
+ registerType: http #zookeeper #etcd #nacos #consul
+ serverLists: http://localhost:9095 #localhost:2181 #http://localhost:2379 #localhost:8848
+ props:
+ username: admin
+ password: 123456
+ client:
+ tars:
+ props:
+ contextPath: /tars
+ appName: tars
+ port: 21715
+ host: 192.168.41.103
+```
+
+3. Add `@ShenyuTarsService` Annotation on the tars service interface implementation class and `@ShenyuTarsClient` on the method, start your service provider, and register successfully. In the background management system, enter PluginList -> rpc proxy -> tars, you will see the automatic registration of selectors and rules information.
+
+Example:
+
+```java
+ @TarsServant("HelloObj")
+ @ShenyuTarsService(serviceName = "ShenyuExampleServer.ShenyuExampleApp.HelloObj")
+ public class HelloServantImpl implements HelloServant {
+ @Override
+ @ShenyuTarsClient(path = "/hello", desc = "hello")
+ public String hello(int no, String name) {
+ return String.format("hello no=%s, name=%s, time=%s", no, name, System.currentTimeMillis());
+ }
+
+ @Override
+ @ShenyuTarsClient(path = "/helloInt", desc = "helloInt")
+ public int helloInt(int no, String name) {
+ return 1;
+ }
+ }
+
+```
+
+## User Request
+
+You can request your tars service by Http. The `Apache ShenYu` gateway needs to have a route prefix which is the `contextPath` configured by the access gateway. For example: `http://localhost:9195/tars/hello` .
+
diff --git a/versioned_docs/version-2.6.1/user-guide/proxy/websocket-proxy.md b/versioned_docs/version-2.6.1/user-guide/proxy/websocket-proxy.md
new file mode 100644
index 00000000000..b91592c755a
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/proxy/websocket-proxy.md
@@ -0,0 +1,89 @@
+---
+title: Websocket Proxy
+description: Websocket Proxy
+---
+
+This document is intended to help the `Websocket` service access the `Apache ShenYu` gateway. The `Apache ShenYu` gateway uses the `Websocket` plugin to handle `Websocket` service.
+
+Before the connection, start `shenyu-admin` correctly, start `Websocket` plugin, and add related dependencies on the gateway and `Websocket` application client. Refer to the previous [Quick start with Websocket](../quick-start/quick-start-websocket) .
+
+For details about client access configuration, see [Application Client Access Config](../property-config/register-center-access.md) .
+
+For details about data synchronization configurations, see [Data Synchronization Config](../property-config/use-data-sync.md)).
+
+## Add Websocket plugin in gateway
+
+Add the following dependencies to the gateway's `pom.xml` file , which is introduced by default：
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-plugin-websocket
+ ${project.version}
+
+```
+
+* Restart your gateway service.
+
+## Websocket service access gateway
+
+> Please refer to： [shenyu-examples-websocket](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-websocket), Contains examples of the three implementations of `annotation websocket`、`spring native websocket`、`spring reactive websocket`
+
+1. In the `Websocket` service, add the following dependencies:
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-client-websocket
+ ${shenyu.version}
+
+```
+
+2. Add the following configuration to the `application.yaml` configuration file:
+
+```yaml
+shenyu:
+ register:
+ registerType: http
+ serverLists: http://localhost:9095 # shenyu-admin ip and port
+ props:
+ username: admin
+ password: 123456
+ client:
+ websocket:
+ props:
+ contextPath: /ws-annotation
+ appName: ws-annotation
+ port: 8001 # need to be consistent with the service port
+```
+
+3. Add `@ShenyuSpringWebSocketClient` annotation to the `Websocket` service interface implementation class, start your service and after successful registration, go to `Client List -> Proxy -> Websocket` in the `shenyu-admin` management system and you will see the auto-registered selector and rule information.
+
+示例：
+
+```java
+@ShenyuSpringWebSocketClient("/myWs")
+@ServerEndpoint("/myWs")
+public class WsServerEndpoint {
+ @OnOpen
+ public void onOpen(final Session session) {
+ LOG.info("connect successful");
+ }
+
+ @OnClose
+ public void onClose(final Session session) {
+ LOG.info("connect closed");
+ }
+
+ @OnMessage
+ public String onMsg(final String text) {
+ return "server send message：" + text;
+ }
+}
+```
+
+## User Request
+
+You need to request your `Websocket` service via the `ws` protocol. The `Apache ShenYu` gateway will configure a routing prefix which is the `contextPath` in the access gateway configuration file. For example: `ws://localhost:9195/ws-annotation/myWs`, after which you can establish a connection to send and receive messages normally.
+
diff --git a/versioned_docs/version-2.6.1/user-guide/sdk-usage/_category_.json b/versioned_docs/version-2.6.1/user-guide/sdk-usage/_category_.json
new file mode 100644
index 00000000000..f2539153751
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/sdk-usage/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Shenyu-Sdk Usage",
+ "position": 3
+}
diff --git a/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-consul.md b/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-consul.md
new file mode 100644
index 00000000000..f98f156c38d
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-consul.md
@@ -0,0 +1,204 @@
+---
+title: Using Consul with Shenyu-SDK
+keywords: ["Using Shenyu-Sdk", "Consul"]
+description: Using Shenyu-Sdk
+---
+
+## Background explanation
+
+Shenyu offers Shenyu-Sdk to make it easy for services to quickly integrate with the Shenyu gateway. By simply depending on the SDK and doing some simple configuration, client services can call the gateway's exposed APIs as if they were calling local interfaces.
+
+
+
+The registration center supported by the gateway for client access includes (nacos, eureka, etcd, zookeeper, consul), and the following is the relevant guide for using **Zookeeper** registration center when `shenyu-bootstrap` and `application client` are used.
+
+## Environment preparation
+
+Refer to `Deployment` guide, and choose a way to start `shenyu-admin` and `shenyu-bootstrap`.
+
+## shenyu-bootstrap
+
+### Maven dependency
+
+In the gateway's `pom.xml` file, introduce the following dependencies.
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-registry
+ ${project.version}
+
+```
+
+### Edit the configuration file
+
+Add the following configuration to the gateway's `yml` configuration file.
+
+```yaml
+shenyu:
+ register:
+ enabled: true
+ registerType: consul
+ serverLists: localhost
+ props:
+ delay: 1
+ wait-time: 55
+ instanceId: shenyu-gateway
+ hostName: localhost
+ tags: test1,test2
+ preferAgentAddress: false
+ enableTagOverride: false
+
+# registerType: service registration type, fill in consul
+# serverLists: consul client agent address (sidecar deployment mode (single machine or cluster), can also be the address of consul server agent (can only connect to one consul server agent node, if it is a cluster, then there will be a single point of failure problem))
+# delay: the polling interval of each metadata monitoring, unit: second, default 1 second
+# wait-time: the waiting time of a single request for metadata monitoring (long polling mechanism), unit: second, default 55 seconds
+# instanceId: required for consul service, consul needs to find specific services through instance-id
+# name: the group name where the service is registered to consul
+# hostName: for consul registration type, fill in the address of the registered service instance, the address of the registered service instance in this registration center will not be used for client calls, so this configuration can be omitted, port, preferAgentAddress similarly
+# port: for consul registration type, fill in the port of the registered service instance
+# tags: corresponding to the tags configuration in consul configuration
+# preferAgentAddress: use the address of the agent on the consul client side as the address of the registered service instance, which will override the manual configuration of hostName
+# enableTagOverride: corresponding to the enableTagOverride configuration in consul configuration for detailed reference, please see the user guide> attribute configuration> client access configuration document
+
+# for detailed reference, please see the `user-guide> Property Config> Register Center Instance Config` configuration document.
+```
+
+## Client Application
+
+### Maven dependency
+
+In the `pom.xml` file of the application client, introduce the following dependencies.
+
+- Shenyu-Sdk Core
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-sdk-core
+ 2.5.1-SNAPSHOT
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-sdk
+ 2.5.1-SNAPSHOT
+
+
+```
+
+- Shenyu-Sdk http implementation
+
+> HTTP client implementation, offering okhttp and httpclient as implementation options. Other implementations can be created by extending the `AbstractShenyuSdkClient` class.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-sdk-httpclient
+ 2.5.1-SNAPSHOT
+
+
+
+
+```
+
+### Edit the configuration file
+
+Add the following configuration in the application client's `yml` configuration file.
+
+```yaml
+shenyu:
+ sdk:
+ enabled: true
+ register-type: consul
+ server-lists: localhost
+ props:
+ checkTtl: 5
+ token: ""
+ waitTime: 30
+ watchDelay: 5
+ tags: ""
+ port: 8500
+ retry:
+ enable: true
+ period: 100
+ maxPeriod: 1000
+ maxAttempts: 5
+ algorithm: roundRobin
+ scheme: http
+
+# registerType: service registration type, fill in consul.
+# serverLists: consul client agent address (sidecar deployment mode (single machine or cluster), can also be the address of consul server agent (can only connect to one consul server agent node, if it is a cluster, then there will be a single point of failure problem)).
+# checkTtl: TTL, Default 5 seconds.
+# token: ""
+# waitTime: The waiting time for a single request for monitoring metadata (long polling mechanism), in seconds, with a default value of 55 seconds.
+# watchDelay: The interval duration for each polling of metadata monitoring, in seconds, with a default value of 1 second.
+# tags: tags for consul configure.
+# port: consul server port.
+# scheme: Request protocol.
+
+# retry Configuration related to failure retries
+# retry.period: Retry waiting time.
+# retry.maxPeriod: Maximum retry waiting time .
+# retry.maxAttempts: Maximum retry count.
+```
+
+## Writing the local interface for the SDK
+
+1. In the project startup class, annotate `@EnableShenyuClients(basePackages = "org.apache.shenyu.examples.sdk.http.api")`, where `basePackages` maintains the package location of Shenyu-Sdk's corresponding maintained gateway API interface.
+
+2. Create an interface and use the `@ShenyuClient(name = "xxx", contextId = "ShenyuSdkApiName")` annotation to mark it, where `name` represents the gateway service name. If you need to define multiple beans to maintain the gateway's API, you can use `contextId` as the corresponding bean alias.
+
+3. In the defined interface, add the methods of the interface to be mapped to the shenyu gateway, where the `value` of `@xxMapping` corresponds to the path of the corresponding request in the gateway.
+
+**Example**
+
+Project startup class
+
+```java
+import org.apache.shenyu.sdk.spring.EnableShenyuClients;
+
+@SpringBootApplication
+@EnableShenyuClients(basePackages = "org.apache.shenyu.examples.sdk.http.api")
+public class ShenyuSdkHttpExampleApplication {
+
+ /**
+ * main.
+ *
+ * @param args args
+ */
+ public static void main(final String[] args) {
+ SpringApplication.run(ShenyuSdkHttpExampleApplication.class, args);
+ }
+}
+```
+
+Shenyu-SDK interface
+
+```java
+import org.apache.shenyu.sdk.spring.ShenyuClient;
+
+@ShenyuClient(name = "shenyu-gateway", contextId = "ShenyuSdkApiName")
+public interface ShenyuHttpClientApi {
+
+ /**
+ * findById.
+ * test Get.
+ *
+ * @param id id
+ * @return SdkTestDto
+ */
+ @GetMapping("/http/shenyu/client/findById")
+ SdkTestDto findById(@RequestParam("id") String id);
+}
+```
+
+For more information, refer to the sample project [shenyu-examples-sdk](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-sdk)
diff --git a/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-etcd.md b/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-etcd.md
new file mode 100644
index 00000000000..0837668ef56
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-etcd.md
@@ -0,0 +1,184 @@
+---
+title: Using Etcd with Shenyu-SDK
+keywords: ["Using Shenyu-Sdk", "Etcd"]
+description: Using Shenyu-Sdk
+---
+
+## Background explanation
+
+Shenyu offers Shenyu-Sdk to make it easy for services to quickly integrate with the Shenyu gateway. By simply depending on the SDK and doing some simple configuration, client services can call the gateway's exposed APIs as if they were calling local interfaces.
+
+
+
+The registration center supported by the gateway for client access includes (nacos, eureka, etcd, zookeeper, consul), and the following is the relevant guide for using **etcd** registration center when `shenyu-bootstrap` and `application client` are used.
+
+## Environment preparation
+
+Refer to `Deployment` guide, and choose a way to start `shenyu-admin` and `shenyu-bootstrap`.
+
+## shenyu-bootstrap
+
+### Maven dependency
+
+In the gateway's `pom.xml` file, introduce the following dependencies.
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-registry
+ ${project.version}
+
+```
+
+### Edit the configuration file
+
+Add the following configuration to the gateway's `yml` configuration file.
+
+```yaml
+shenyu:
+ register:
+ enabled: true
+ registerType: etcd
+ serverLists: http://localhost:2379
+ props:
+ appName: http
+ port: xx
+
+# registerType: service registration type, fill in etcd.
+# serverList: Enter the etcd address(es), separated by commas in English.
+# appName：Your application name. If not configured, the default value will be taken from spring.application.name.
+# port: Your project's startup port, currently springmvc/tars/grpc needs to be filled in.
+
+# for detailed reference, please see the `user-guide> Property Config> Register Center Instance Config` configuration document.
+```
+
+## Client Application
+
+### Maven dependency
+
+In the `pom.xml` file of the application client, introduce the following dependencies.
+
+- Shenyu-Sdk Core
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-sdk-core
+ 2.5.1-SNAPSHOT
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-sdk
+ 2.5.1-SNAPSHOT
+
+
+```
+
+- Shenyu-Sdk http implementation
+
+> HTTP client implementation, offering okhttp and httpclient as implementation options. Other implementations can be created by extending the `AbstractShenyuSdkClient` class.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-sdk-httpclient
+ 2.5.1-SNAPSHOT
+
+
+
+
+```
+
+### Edit the configuration file
+
+Add the following configuration in the application client's `yml` configuration file.
+
+```yaml
+shenyu:
+ sdk:
+ enabled: true
+ register-type: etcd
+ server-lists: http://localhost:2379
+ props:
+ etcdTimeout: 3000
+ etcdTTL: 5
+ retry:
+ enable: true
+ period: 100
+ maxPeriod: 1000
+ maxAttempts: 5
+ algorithm: roundRobin
+ scheme: http
+
+# register-type: service registration type, fill in etcd.
+# server-lists: Enter the etcd address(es), separated by commas in English.
+# etcdTimeout: Request timeout time, in milliseconds, default 3000
+# etcdTTL: Lease TTL, default 5 seconds.
+# scheme: Request protocol.
+
+# retry: Configuration related to failure retries.
+# retry.period: Retry waiting time.
+# retry.maxPeriod: Maximum retry waiting time .
+# retry.maxAttempts: Maximum retry count.
+```
+
+## Writing the local interface for the SDK
+
+1. In the project startup class, annotate `@EnableShenyuClients(basePackages = "org.apache.shenyu.examples.sdk.http.api")`, where `basePackages` maintains the package location of Shenyu-Sdk's corresponding maintained gateway API interface.
+
+2. Create an interface and use the `@ShenyuClient(name = "xxx", contextId = "ShenyuSdkApiName")` annotation to mark it, where `name` represents the gateway service name. If you need to define multiple beans to maintain the gateway's API, you can use `contextId` as the corresponding bean alias.
+
+3. In the defined interface, add the methods of the interface to be mapped to the shenyu gateway, where the `value` of `@xxMapping` corresponds to the path of the corresponding request in the gateway.
+
+**Example**
+
+Project startup class
+
+```java
+import org.apache.shenyu.sdk.spring.EnableShenyuClients;
+
+@SpringBootApplication
+@EnableShenyuClients(basePackages = "org.apache.shenyu.examples.sdk.http.api")
+public class ShenyuSdkHttpExampleApplication {
+
+ /**
+ * main.
+ *
+ * @param args args
+ */
+ public static void main(final String[] args) {
+ SpringApplication.run(ShenyuSdkHttpExampleApplication.class, args);
+ }
+}
+```
+
+Shenyu-SDK interface
+
+```java
+import org.apache.shenyu.sdk.spring.ShenyuClient;
+
+@ShenyuClient(name = "shenyu-gateway", contextId = "ShenyuSdkApiName")
+public interface ShenyuHttpClientApi {
+
+ /**
+ * findById.
+ * test Get.
+ *
+ * @param id id
+ * @return SdkTestDto
+ */
+ @GetMapping("/http/shenyu/client/findById")
+ SdkTestDto findById(@RequestParam("id") String id);
+}
+```
+
+For more information, refer to the sample project [shenyu-examples-sdk](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-sdk)
diff --git a/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-eureka.md b/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-eureka.md
new file mode 100644
index 00000000000..dfcd9c39a61
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-eureka.md
@@ -0,0 +1,184 @@
+---
+title: Using Eureka with Shenyu-SDK
+keywords: ["Using Shenyu-Sdk", "Eureka"]
+description: Using Shenyu-Sdk
+---
+
+## Background explanation
+
+Shenyu offers Shenyu-Sdk to make it easy for services to quickly integrate with the Shenyu gateway. By simply depending on the SDK and doing some simple configuration, client services can call the gateway's exposed APIs as if they were calling local interfaces.
+
+
+
+The registration center supported by the gateway for client access includes (nacos, eureka, etcd, zookeeper, consul), and the following is the relevant guide for using **eureka** registration center when `shenyu-bootstrap` and `application client` are used.
+
+## Environment preparation
+
+Refer to `Deployment` guide, and choose a way to start `shenyu-admin` and `shenyu-bootstrap`.
+
+## shenyu-bootstrap
+
+### Maven dependency
+
+In the gateway's `pom.xml` file, introduce the following dependencies.
+
+```xml
+
+ org.springframework.cloud
+ spring-cloud-starter-netflix-eureka-client
+ ${eureka-client.version}
+
+
+ org.springframework.cloud
+ spring-cloud-starter-loadbalancer
+
+
+
+```
+
+### Edit the configuration file
+
+Add the following configuration to the gateway's `yml` configuration file.
+
+```yaml
+spring:
+ cloud:
+ discovery:
+ enabled: true # Enable service discovery
+
+eureka:
+ client:
+ enabled: true
+ serviceUrl:
+ defaultZone: http://localhost:8761/eureka/ # Enter your eureka registry center address here
+ instance:
+ prefer-ip-address: true
+```
+
+## Client Application
+
+### Maven dependency
+
+In the `pom.xml` file of the application client, introduce the following dependencies.
+
+- Shenyu-Sdk Core
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-sdk-core
+ 2.5.1-SNAPSHOT
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-sdk
+ 2.5.1-SNAPSHOT
+
+
+```
+
+- Shenyu-Sdk http implementation
+
+> HTTP client implementation, offering okhttp and httpclient as implementation options. Other implementations can be created by extending the `AbstractShenyuSdkClient` class.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-sdk-httpclient
+ 2.5.1-SNAPSHOT
+
+
+
+
+```
+
+### Edit the configuration file
+
+Add the following configuration in the application client's `yml` configuration file.
+
+```yaml
+shenyu:
+ sdk:
+ enabled: true
+ register-type: eureka
+ server-lists: http://localhost:8761/eureka/
+ props:
+ retry:
+ enable: true
+ period: 100
+ maxPeriod: 1000
+ maxAttempts: 5
+ algorithm: roundRobin
+ scheme: http
+
+# registerType: service registration type, fill in eureka
+# serverList: Enter the eureka server address(es), separated by commas in English.
+# scheme: Request protocol.
+
+# retry: Configuration related to failure retries.
+# retry.period: Retry waiting time.
+# retry.maxPeriod: Maximum retry waiting time .
+# retry.maxAttempts: Maximum retry count.
+```
+
+
+## Writing the local interface for the SDK
+
+1. In the project startup class, annotate `@EnableShenyuClients(basePackages = "org.apache.shenyu.examples.sdk.http.api")`, where `basePackages` maintains the package location of Shenyu-Sdk's corresponding maintained gateway API interface.
+
+2. Create an interface and use the `@ShenyuClient(name = "xxx", contextId = "ShenyuSdkApiName")` annotation to mark it, where `name` represents the gateway service name. If you need to define multiple beans to maintain the gateway's API, you can use `contextId` as the corresponding bean alias.
+
+3. In the defined interface, add the methods of the interface to be mapped to the shenyu gateway, where the `value` of `@xxMapping` corresponds to the path of the corresponding request in the gateway.
+
+**Example**
+
+Project startup class
+
+```java
+import org.apache.shenyu.sdk.spring.EnableShenyuClients;
+
+@SpringBootApplication
+@EnableShenyuClients(basePackages = "org.apache.shenyu.examples.sdk.http.api")
+public class ShenyuSdkHttpExampleApplication {
+
+ /**
+ * main.
+ *
+ * @param args args
+ */
+ public static void main(final String[] args) {
+ SpringApplication.run(ShenyuSdkHttpExampleApplication.class, args);
+ }
+}
+```
+
+Shenyu-SDK interface
+
+```java
+import org.apache.shenyu.sdk.spring.ShenyuClient;
+
+@ShenyuClient(name = "shenyu-bootstrap", contextId = "ShenyuSdkApiName")
+public interface ShenyuHttpClientApi {
+
+ /**
+ * findById.
+ * test Get.
+ *
+ * @param id id
+ * @return SdkTestDto
+ */
+ @GetMapping("/http/shenyu/client/findById")
+ SdkTestDto findById(@RequestParam("id") String id);
+}
+```
+
+For more information, refer to the sample project [shenyu-examples-sdk](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-sdk)
diff --git a/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-feign.md b/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-feign.md
new file mode 100644
index 00000000000..20cfe2df822
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-feign.md
@@ -0,0 +1,130 @@
+---
+title: Using Shenyu-SDK-Feign
+keywords: ["Using Shenyu-Sdk", "feign"]
+description: Using Shenyu-Sdk-Feign
+---
+
+## Shenyu sdk-feign
+
+> Integrate `open Feign` to implement declarative SDK call gateway API.
+> Like 'shenyu sdk', 'shenyu sdk feign' is another option;
+> for more information see :
+> * please refer to: [shenyu-sdk-consul](../../user-guide/sdk-usage/shenyu-sdk-consul)
+> * please refer to: [shenyu-sdk-etcd](../../user-guide/sdk-usage/shenyu-sdk-etcd)
+> * please refer to: [shenyu-sdk-eureka](../../user-guide/sdk-usage/shenyu-sdk-eureka)
+> * please refer to: [shenyu-sdk-nacos](../../user-guide/sdk-usage/shenyu-sdk-nacos)
+> * please refer to: [shenyu-sdk-zookeeper](../../user-guide/sdk-usage/shenyu-sdk-zookeeper)
+
+### Maven dependency
+
+In the `pom.xml` file of the application client, introduce the following dependencies(Compatible with `FeignClient`).
+
+```xml
+
+
+ org.springframework.cloud
+ spring-cloud-starter-openfeign
+ ${spring-cloud.version}
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-sdk-feign
+ 2.6.1-SNAPSHOT
+
+
+```
+
+
+### Edit the configuration file
+
+Add the following configuration in the application client's `yml` configuration file.
+
+```yaml
+shenyu:
+ sdk:
+ enabled: true
+ register-type: consul
+ server-lists: localhost
+ props:
+ algorithm: roundRobin
+ scheme: http
+
+# if not use openFeign and springCloud-loadBalance, feign client options must be enabled.
+feign:
+ client:
+ httpclient:
+ enabled: true
+
+# registerType: service registration type, fill in consul.
+# serverLists: consul client agent address (sidecar deployment mode (single machine or cluster), can also be the address of consul server agent (can only connect to one consul server agent node, if it is a cluster, then there will be a single point of failure problem)).
+
+# algorithm: load balance algorithm.
+# scheme: Request protocol.
+
+```
+
+## Writing the local interface for the SDK
+
+1. In the project startup class, annotate `@EnableShenyuClients(basePackages = "org.apache.shenyu.examples.sdk.http.api")`, where `basePackages` maintains the package location of Shenyu-Sdk's corresponding maintained gateway API interface.
+
+2. Create an interface and use the `@ShenyuClient(name = "xxx", contextId = "ShenyuSdkApiName")` annotation to mark it, where `name` represents the gateway service name. If you need to define multiple beans to maintain the gateway's API, you can use `contextId` as the corresponding bean alias.
+
+3. In the defined interface, add the methods of the interface to be mapped to the shenyu gateway, where the `value` of `@xxMapping` corresponds to the path of the corresponding request in the gateway.
+
+**Example**
+
+Project startup class
+
+```java
+import org.apache.shenyu.sdk.feign.EnableShenyuClients;
+
+@SpringBootApplication
+@EnableShenyuClients(basePackages = "org.apache.shenyu.examples.sdk.feign.api")
+public class ShenyuSdkHttpExampleApplication {
+
+ /**
+ * main.
+ *
+ * @param args args
+ */
+ public static void main(final String[] args) {
+ SpringApplication.run(ShenyuSdkHttpExampleApplication.class, args);
+ }
+}
+```
+
+Shenyu-SDK interface
+
+```java
+import org.apache.shenyu.sdk.feign.ShenyuClient;
+
+@ShenyuClient(name = "shenyu-gateway", contextId = "ShenyuSdkApiName", path = "/feign/shenyu/client")
+public interface ShenyuFeignClientApi {
+
+ /**
+ * findById.
+ * test Get.
+ *
+ * @param id id
+ * @return SdkTestDto
+ */
+ @GetMapping("/findById")
+ SdkTestDto findById(@RequestParam("id") String id);
+
+ /**
+ * annoTest.
+ *
+ * @param cookie cookie
+ * @param header header
+ * @param id id
+ * @param requestDto requestDto
+ * @return sdkTestDto
+ */
+ @PostMapping("/{id}/anno")
+ SdkTestDto annoTest(@CookieValue("cookie") String cookie, @RequestHeader("header") String header, @PathVariable("id") String id, @RequestBody SdkTestDto requestDto);
+
+}
+```
+
+For more information, refer to the sample project [shenyu-examples-sdk-feign](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-sdk/shenyu-examples-sdk-feign)
diff --git a/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-nacos.md b/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-nacos.md
new file mode 100644
index 00000000000..e8226285644
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-nacos.md
@@ -0,0 +1,185 @@
+---
+title: Using Nacos with Shenyu-SDK
+keywords: ["Using Shenyu-Sdk", "Nacos"]
+description: Using Shenyu-Sdk
+---
+
+## Background explanation
+
+Shenyu offers Shenyu-Sdk to make it easy for services to quickly integrate with the Shenyu gateway. By simply depending on the SDK and doing some simple configuration, client services can call the gateway's exposed APIs as if they were calling local interfaces.
+
+
+
+The registration center supported by the gateway for client access includes (nacos, eureka, etcd, zookeeper, consul), and the following is the relevant guide for using **nacos** registration center when `shenyu-bootstrap` and `application client` are used.
+
+## Environment preparation
+
+Refer to `Deployment` guide, and choose a way to start `shenyu-admin` and `shenyu-bootstrap`.
+
+## shenyu-bootstrap
+
+### Maven dependency
+
+In the gateway's `pom.xml` file, introduce the following dependencies.
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-registry
+ ${project.version}
+
+```
+
+### Edit the configuration file
+
+Add the following configuration to the gateway's `yml` configuration file.
+
+```yaml
+spring:
+ application:
+ name: shenyu-bootstrap
+ cloud:
+ discovery:
+ enabled: true
+ nacos:
+ discovery:
+ server-addr: 127.0.0.1:8848 # Enter the nacos address(es), separated by commas in English.
+ enabled: true
+ namespace: ShenyuRegisterCenter # nacos namespace ID
+ # if nacos authentication is enabled, the following parameters must be configured
+ username: nacos # Authentication username
+ password: nacos # Authentication password
+```
+
+## Client Application
+
+### Maven dependency
+
+In the `pom.xml` file of the application client, introduce the following dependencies.
+
+- Shenyu-Sdk Core
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-sdk-core
+ 2.5.1-SNAPSHOT
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-sdk
+ 2.5.1-SNAPSHOT
+
+
+```
+
+- Shenyu-Sdk http implementation
+
+> HTTP client implementation, offering okhttp and httpclient as implementation options. Other implementations can be created by extending the `AbstractShenyuSdkClient` class.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-sdk-httpclient
+ 2.5.1-SNAPSHOT
+
+
+
+
+```
+
+### Edit the configuration file
+
+Add the following configuration in the application client's `yml` configuration file.
+
+```yaml
+shenyu:
+ sdk:
+ enabled: true
+ register-type: nacos
+ server-lists: localhost:2181
+ props:
+ nacosNameSpace: ShenyuRegisterCenter
+ username: nacos
+ password: nacos
+ retry:
+ enable: true
+ period: 100
+ maxPeriod: 1000
+ maxAttempts: 5
+ algorithm: roundRobin
+ scheme: http
+
+# registerType: service registration type, fill in nacos.
+# serverList: Enter the nacos address(es), separated by commas in English.
+# nacosNameSpace: nacos namespace ID
+# username: Authentication username
+# password: Authentication password
+# scheme: Request protocol.
+
+# retry: Configuration related to failure retries.
+# retry.period: Retry waiting time.
+# retry.maxPeriod: Maximum retry waiting time .
+# retry.maxAttempts: Maximum retry count.
+```
+
+## Writing the local interface for the SDK
+
+1. In the project startup class, annotate `@EnableShenyuClients(basePackages = "org.apache.shenyu.examples.sdk.http.api")`, where `basePackages` maintains the package location of Shenyu-Sdk's corresponding maintained gateway API interface.
+
+2. Create an interface and use the `@ShenyuClient(name = "xxx", contextId = "ShenyuSdkApiName")` annotation to mark it, where `name` represents the gateway service name. If you need to define multiple beans to maintain the gateway's API, you can use `contextId` as the corresponding bean alias.
+
+3. In the defined interface, add the methods of the interface to be mapped to the shenyu gateway, where the `value` of `@xxMapping` corresponds to the path of the corresponding request in the gateway.
+
+**Example**
+
+Project startup class
+
+```java
+import org.apache.shenyu.sdk.spring.EnableShenyuClients;
+
+@SpringBootApplication
+@EnableShenyuClients(basePackages = "org.apache.shenyu.examples.sdk.http.api")
+public class ShenyuSdkHttpExampleApplication {
+
+ /**
+ * main.
+ *
+ * @param args args
+ */
+ public static void main(final String[] args) {
+ SpringApplication.run(ShenyuSdkHttpExampleApplication.class, args);
+ }
+}
+```
+
+Shenyu-SDK interface
+
+```java
+import org.apache.shenyu.sdk.spring.ShenyuClient;
+
+@ShenyuClient(name = "shenyu-bootstrap", contextId = "ShenyuSdkApiName")
+public interface ShenyuHttpClientApi {
+
+ /**
+ * findById.
+ * test Get.
+ *
+ * @param id id
+ * @return SdkTestDto
+ */
+ @GetMapping("/http/shenyu/client/findById")
+ SdkTestDto findById(@RequestParam("id") String id);
+}
+```
+
+For more information, refer to the sample project [shenyu-examples-sdk](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-sdk)
diff --git a/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-zookeeper.md b/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-zookeeper.md
new file mode 100644
index 00000000000..4c546574022
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/sdk-usage/shenyu-sdk-zookeeper.md
@@ -0,0 +1,179 @@
+---
+title: Using Zookeeper with Shenyu-SDK
+keywords: ["Using Shenyu-Sdk", "zookeeper"]
+description: Using Shenyu-Sdk
+---
+
+## Background explanation
+
+Shenyu offers Shenyu-Sdk to make it easy for services to quickly integrate with the Shenyu gateway. By simply depending on the SDK and doing some simple configuration, client services can call the gateway's exposed APIs as if they were calling local interfaces.
+
+
+
+The registration center supported by the gateway for client access includes (nacos, eureka, etcd, zookeeper, consul), and the following is the relevant guide for using **Zookeeper** registration center when `shenyu-bootstrap` and `application client` are used.
+
+## Environment preparation
+
+Refer to `Deployment` guide, and choose a way to start `shenyu-admin` and `shenyu-bootstrap`.
+
+## shenyu-bootstrap
+
+### Maven dependency
+
+In the gateway's `pom.xml` file, introduce the following dependencies.
+
+```xml
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-registry
+ ${project.version}
+
+```
+
+### Edit the configuration file
+
+Add the following configuration to the gateway's `yml` configuration file.
+
+```yaml
+shenyu:
+ register:
+ enabled: true
+ registerType: zookeeper
+ serverLists: localhost:2181
+ props:
+ appName: http
+ port: xx
+# registerType: service registration type, fill in zookeeper.
+# serverList: Enter the zookeeper address(es), separated by commas in English.
+# appName：Your application name. If not configured, the default value will be taken from spring.application.name.
+# port: Your project's startup port, currently springmvc/tars/grpc needs to be filled in.
+
+# for detailed reference, please see the `user-guide> Property Config> Register Center Instance Config` configuration document.
+```
+
+## Client Application
+
+### Maven dependency
+
+In the `pom.xml` file of the application client, introduce the following dependencies.
+
+- Shenyu-Sdk Core
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-sdk-core
+ 2.5.1-SNAPSHOT
+
+
+
+ org.apache.shenyu
+ shenyu-spring-boot-starter-sdk
+ 2.5.1-SNAPSHOT
+
+
+```
+
+- Shenyu-Sdk http implementation
+
+> HTTP client implementation, offering okhttp and httpclient as implementation options. Other implementations can be created by extending the `AbstractShenyuSdkClient` class.
+
+```xml
+
+
+ org.apache.shenyu
+ shenyu-sdk-httpclient
+ 2.5.1-SNAPSHOT
+
+
+
+
+```
+
+### Edit the configuration file
+
+Add the following configuration in the application client's `yml` configuration file.
+
+```yaml
+shenyu:
+ sdk:
+ enabled: true
+ register-type: zookeeper
+ server-lists: localhost:2181
+ props:
+ retry:
+ enable: true
+ period: 100
+ maxPeriod: 1000
+ maxAttempts: 5
+ algorithm: roundRobin
+ scheme: http
+
+# register-type: service registration type, fill in zookeeper.
+# server-lists: Enter the zookeeper address(es), separated by commas in English.
+# scheme: Request protocol.
+
+# retry: Configuration related to failure retries.
+# retry.period: Retry waiting time.
+# retry.maxPeriod: Maximum retry waiting time .
+# retry.maxAttempts: Maximum retry count.
+```
+
+## Writing the local interface for the SDK
+
+1. In the project startup class, annotate `@EnableShenyuClients(basePackages = "org.apache.shenyu.examples.sdk.http.api")`, where `basePackages` maintains the package location of Shenyu-Sdk's corresponding maintained gateway API interface.
+
+2. Create an interface and use the `@ShenyuClient(name = "xxx", contextId = "ShenyuSdkApiName")` annotation to mark it, where `name` represents the gateway service name. If you need to define multiple beans to maintain the gateway's API, you can use `contextId` as the corresponding bean alias.
+
+3. In the defined interface, add the methods of the interface to be mapped to the shenyu gateway, where the `value` of `@xxMapping` corresponds to the path of the corresponding request in the gateway.
+
+**Example**
+
+Project startup class
+
+```java
+import org.apache.shenyu.sdk.spring.EnableShenyuClients;
+
+@SpringBootApplication
+@EnableShenyuClients(basePackages = "org.apache.shenyu.examples.sdk.http.api")
+public class ShenyuSdkHttpExampleApplication {
+
+ /**
+ * main.
+ *
+ * @param args args
+ */
+ public static void main(final String[] args) {
+ SpringApplication.run(ShenyuSdkHttpExampleApplication.class, args);
+ }
+}
+```
+
+Shenyu-SDK interface
+
+```java
+import org.apache.shenyu.sdk.spring.ShenyuClient;
+
+@ShenyuClient(name = "shenyu-gateway", contextId = "ShenyuSdkApiName")
+public interface ShenyuHttpClientApi {
+
+ /**
+ * findById.
+ * test Get.
+ *
+ * @param id id
+ * @return SdkTestDto
+ */
+ @GetMapping("/http/shenyu/client/findById")
+ SdkTestDto findById(@RequestParam("id") String id);
+}
+```
+
+For more information, refer to the sample project [shenyu-examples-sdk](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-sdk)
diff --git a/versioned_sidebars/version-2.6.1-sidebars.json b/versioned_sidebars/version-2.6.1-sidebars.json
new file mode 100644
index 00000000000..7ef4ca95ab0
--- /dev/null
+++ b/versioned_sidebars/version-2.6.1-sidebars.json
@@ -0,0 +1,8 @@
+{
+ "version-2.6.0/tutorialSidebar": [
+ {
+ "type": "autogenerated",
+ "dirName": "."
+ }
+ ]
+}
diff --git a/versions.json b/versions.json
index 0973190fa61..da31d6447a6 100755
--- a/versions.json
+++ b/versions.json
@@ -1,4 +1,5 @@
[
+ "2.6.1",
"2.6.0",
"2.5.1",
"2.5.0",
+
+数据同步的相关配置请参考用户文档中的 [数据同步配置](../user-guide/property-config/use-data-sync.md) 。
+
+### 背景
+
+网关是流量请求的入口，在微服务架构中承担了非常重要的角色，网关高可用的重要性不言而喻。在使用网关的过程中，为了满足业务诉求，经常需要变更配置，比如流控规则、路由规则等等。因此，网关动态配置是保障网关高可用的重要因素。
+
+
+在实际使用 `Apache ShenYu` 网关过程中，用户也反馈了一些问题：
+
+* 依赖 `Zookeeper`，怎么使用 `Etcd`、`Consul`、`Nacos`等其他注册中心？
+* 依赖 `Redis`、`influxdb`，没有使用限流插件、监控插件，为什么需要这些？
+* 配置同步为什么不使用配置中心？
+* 为什么不能动态配置更新？
+* 每次都要查询数据库，使用`Redis`不就行了吗？
+
+根据用户的反馈信息，我们对 `Apache ShenYu` 也进行了部分的重构，当前数据同步特性如下：
+
+- 所有的配置都缓存在 `Apache ShenYu` 网关内存中，每次请求都使用本地缓存，速度非常快。
+- 用户可以在 `shenyu-admin` 后台任意修改数据，并马上同步到网关内存。
+- 支持 `Apache ShenYu` 的插件、选择器、规则数据、元数据、签名数据等数据同步。
+- 所有插件的选择器，规则都是动态配置，立即生效，不需要重启服务。
+- 数据同步方式支持 `Zookeeper`、`Http 长轮询`、`Websocket`、`Nacos`、`Etcd` 和 `Consul`。
+
+### 原理分析
+
+下图展示了 `Apache ShenYu` 数据同步的流程，`Apache ShenYu` 网关在启动时，会从配置服务同步配置数据，并且支持推拉模式获取配置变更信息，然后更新本地缓存。管理员可以在管理后台（`shenyu-admin`），变更用户权限、规则、插件、流量配置，通过推拉模式将变更信息同步给 `Apache ShenYu` 网关，具体是 `push` 模式，还是 `pull` 模式取决于使用哪种同步方式。
+
+ 
+
+在最初的版本中，配置服务依赖 `Zookeeper` 实现，管理后台将变更信息 `push` 给网关。而现在可以支持 `WebSocket`、`Http长轮询`、`Zookeeper`、`Nacos`、`Etcd` 和 `Consul`，通过在配置文件中设置 `shenyu.sync.${strategy}` 指定对应的同步策略，默认使用 `WebSocket` 同步策略，可以做到秒级数据同步。但是，有一点需要注意的是，`Apache ShenYu`网关 和 `shenyu-admin` 必须使用相同的同步策略。
+
+如下图所示，`shenyu-admin` 在用户发生配置变更之后，会通过 `EventPublisher` 发出配置变更通知，由 `EventDispatcher` 处理该变更通知，然后根据配置的同步策略(`Http、WebSocket、Zookeeper、Nacos、Etcd、Consul`)，将配置发送给对应的事件处理器。
+
+- 如果是 `WebSocket` 同步策略，则将变更后的数据主动推送给 `shenyu-web`，并且在网关层，会有对应的 `WebsocketDataHandler` 处理器来处理 `shenyu-admin` 的数据推送。
+- 如果是 `Zookeeper` 同步策略，将变更数据更新到 `Zookeeper`，而 `ZookeeperSyncCache` 会监听到 `Zookeeper` 的数据变更，并予以处理。
+- 如果是 `Http` 同步策略，由网关主动发起长轮询请求，默认有 `90s` 超时时间，如果 `shenyu-admin` 没有数据变更，则会阻塞 `Http` 请求，如果有数据发生变更则响应变更的数据信息，如果超过 `60s` 仍然没有数据变更则响应空数据，网关层接到响应后，继续发起 `Http` 请求，反复同样的请求。
+
+
+
+### Zookeeper同步原理
+
+基于 `Zookeeper` 的同步原理很简单，主要是依赖 `Zookeeper` 的 `watch` 机制。`Apache ShenYu`网关会监听配置的节点，`shenyu-admin` 在启动的时候，会将数据全量写入 `Zookeeper`，后续数据发生变更时，会增量更新 `Zookeeper` 的节点，与此同时，`Apache ShenYu`网关会监听配置信息的节点，一旦有信息变更时，会更新本地缓存。
+
+
+
+`Apache ShenYu` 将配置信息写到`zookeeper`节点，是通过精心设计的，如果您想深入了解代码实现，请参考源码 `ZookeeperSyncDataService`。
+
+### WebSocket同步原理
+
+`WebSocket` 和 `Zookeeper` 机制有点类似，将网关与 `shenyu-admin` 建立好 `WebSocket` 连接时，`shenyu-admin` 会推送一次全量数据，后续如果配置数据发生变更，则以增量形式将变更数据通过 `WebSocket` 主动推送给 `Apache ShenYu`网关。
+
+使用 `WebSocket` 同步的时候，特别要注意断线重连，也就是要保持心跳。`Apache ShenYu`使用`java-websocket` 这个第三方库来进行`websocket`连接。
+如果您想深入了解代码实现，请参考源码 `WebsocketSyncDataService`。
+
+
+### Http长轮询同步原理
+
+`Zookeeper`和`WebSocket` 数据同步的机制比较简单，而 `Http长轮询`则比较复杂。 `Apache ShenYu` 借鉴了 `Apollo`、`Nacos` 的设计思想，取其精华，自己实现了 `Http长轮询`数据同步功能。注意，这里并非传统的 `ajax` 长轮询！
+
+
+
+`Http长轮询` 机制如上所示，`Apache ShenYu`网关主动请求 `shenyu-admin` 的配置服务，读取超时时间为 `90s`，意味着网关层请求配置服务最多会等待 `90s`，这样便于 `shenyu-admin` 配置服务及时响应变更数据，从而实现准实时推送。
+
+`http` 请求到达 `shenyu-admin` 之后，并非立马响应数据，而是利用 `Servlet3.0` 的异步机制，异步响应数据。首先，将长轮询请求任务 `LongPollingClient` 扔到 `BlockingQueue` 中，并且开启调度任务，`60s` 后执行，这样做的目的是 `60s` 后将该长轮询请求移除队列。因为即便是没有配置变更，也需要让网关知道，不能一直等待。而且网关请求配置服务时，也有 `90s` 的超时时间。
+
+
+如果这段时间内，管理员在 `shenyu-admin` 变更了配置数据，此时，会挨个移除队列中的长轮询请求，并响应数据，告知是哪个 `Group` 的数据发生了变更（我们将插件、规则、流量配置、用户配置数据分成不同的组）。网关收到响应信息之后，只知道是哪个 `Group` 发生了配置变更，还需要再次请求该 `Group` 的配置数据。这里可能会存在一个疑问：为什么不是直接将变更的数据写出？我们在开发的时候，也深入讨论过该问题，因为 `http 长轮询` 机制只能保证准实时，如果在网关层处理不及时，或者管理员频繁更新配置，很有可能便错过了某个配置变更的推送，安全起见，我们只告知某个 `Group` 信息发生了变更。
+
+当 `shenyu-web` 网关层接收到 `http` 响应信息之后，拉取变更信息（如果有变更的话），然后再次请求 `shenyu-admin` 的配置服务，如此反复循环。
+如果您想深入了解代码实现，请参考源码 `HttpSyncDataService`。
+
+
+### Nacos同步原理
+
+`Nacos`的同步原理与Zookeeper基本类似，主要依赖于`Nacos`的`配置管理`,各个配置节点的路径与Zookeeper类似。
+
+`Apache ShenYu`网关会监听配置的节点，启动时，如果`Nacos`中不存在配置节点，将同步全量的数据写入`Nacos`中，后续数据发生变更时，全量更新`Nacos`中的配置节点，与此同时，`Apache ShenYu`网关会监听配置信息的节点，一旦有信息变更时，会更新本地缓存。
+
+如果您想深入了解代码实现，请参考源码 `NacosSyncDataService`和`Nacos`的[官方文档](https://nacos.io/zh-cn/docs/sdk.html)。
+
+
+### Etcd同步原理
+
+`Etcd` 数据同步原理与Zookeeper类似，主要依赖于`Etcd`的`watch`机制，各个配置节点路径与`Zookeeper`相同。
+
+`Etcd`的原生API使用稍有点复杂，所有对其进行了一定的封装。
+
+`Apache ShenYu`网关会监听配置的节点，启动时，如果`Etcd`中不存在配置节点，将同步全量的数据写入`Etcd`中，后续数据发生变更时，增量更新`Etcd`中的配置节点，与此同时，`Apache ShenYu`网关会监听配置信息的节点，一旦有信息变更时，会更新本地缓存。
+
+如果您想深入了解代码实现，请参考源码 `EtcdSyncDataService`。
+
+### Consul同步原理
+
+`Consul` 数据同步原理是网关定时轮询 `Consul` 的配置中心，获取配置版本号与本地进行比对。
+
+`Apache ShenYu`网关会定时轮询配置的节点，默认间隔时间为1s。启动时，如果 `Consul` 中不存在配置节点，将同步全量的数据写入`Consul`中，后续数据发生变更时，增量更新 `Consul` 中的配置节点，与此同时，`Apache ShenYu`网关会定时轮询配置信息的节点，拉取配置版本号与本地进行比对，若发现版本号变更时，会更新本地缓存。
+
+如果您想深入了解代码实现，请参考源码 `ConsulSyncDataService`。
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/design/database-design.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/design/database-design.md
new file mode 100644
index 00000000000..ec6ee2ac241
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/design/database-design.md
@@ -0,0 +1,95 @@
+---
+sidebar_position: 1
+title: 管理后台数据结构设计
+keywords: ["db"]
+description: ShenYu Admin数据结构
+---
+
+`Apache ShenYu Admin` 是网关的后台管理系统，能够可视化管理所有插件、选择器和规则，设置用户、角色，控制资源。
+
+## 插件、选择器和规则
+
+* 插件：`Apache ShenYu` 使用插件化设计思想，实现插件的热插拔，极易扩展。内置丰富的插件，包括 `RPC` 代理、熔断和限流、权限认证、监控等等。
+* 选择器：每个插件可设置多个选择器，对流量进行初步筛选。
+* 规则：每个选择器可设置多个规则，对流量进行更细粒度的控制。
+* 数据库 `UML` 类图:
+
+
+
+* 设计详解:
+
+ * 一个插件对应多个选择器，一个选择器对应多个规则。
+
+ * 一个选择器对应多个匹配条件，一个规则对应多个匹配条件。
+
+ * 每个规则在对应插件下，有不同的处理能力。
+
+## 资源权限
+
+* 资源代表的是 `shenyu-admin` 用户后台中的菜单或者按钮。
+
+* 资源权限数据表用来存储用户名称、角色、资源数据以及对应关系。
+
+* 数据库 `UML` 类图：
+
+
+
+* 设计详解:
+ * 一个用户对应多个角色，一个角色对应多个资源。
+
+
+## 数据权限
+
+* 数据权限表用来存储用户，选择器、规则对应关系。
+* 数据库 `UML` 类图：
+
+
+
+* 设计详解：
+ * 数据权限的表为： `data_permission`，一个用户对应多条数据权限。
+ * 数据权限表中字段 `data_type` 区分不同的类型数据， 具体对应关系如下：`0 -> 选择器, 1 -> 规则`。
+ * 数据权限表中字段 `data_id` 存放相应类型的主键`id`。
+
+## 元数据
+
+* 元数据主要是用于网关的泛化调用。
+* 每个接口方法，对应一条元数据。
+* 数据库 `UML` 类图：
+
+
+
+## 流量筛选
+
+
+
+客户端接入的相关配置请参考用户文档中的 [客户端接入配置](../user-guide/property-config/register-center-access.md) 。
+
+
+## 设计原理
+
+### 注册中心客户端
+
+
+
+在你的微服务配置中声明注册中心客户端类型，如`Http`。
+应用程序启动时使用`SPI`方式加载并初始化对应注册中心客户端，通过实现`Spring Bean`相关的后置处理器接口，在其中获取需要进行注册的服务接口信息，将获取的信息放入`Disruptor`中。
+
+注册中心客户端从`Disruptor`中读取数据，并将接口信息注册到`shenyu-admin`，`Disruptor`在其中起数据与操作解耦的作用，利于扩展。
+
+### 注册中心服务端
+
+
+
+在`shenyu-admin`配置中声明注册中心服务端类型，如`Http`。当`shenyu-admin`启动时，读取配置类型，加载并初始化对应的注册中心服务端，注册中心服务端收到`shenyu-client`注册的接口信息后，将其放入`Disruptor`中，然后会触发注册处理逻辑，将服务接口信息更新并发布同步事件。
+
+`Disruptor`在其中起到数据与操作解耦，利于扩展。如果注册请求过多，导致注册异常，也有数据缓冲作用。
+
+### Http注册原理
+
+`Http`服务注册原理较为简单，在`shenyu-client`启动后，会调用`shenyu-admin`的相关服务注册接口，上传数据进行注册。
+
+`shenyu-admin` 收到请求后进行数据更新和数据同步事件发布，将接口信息同步到`Apache ShenYu`网关。
+
+
+### SPI扩展
+
+| *SPI 名称* | *详细说明* |
+| -------------------------------- | --------------------------- |
+| ShenyuClientRegisterRepository | ShenYu网关客户端接入注册服务资源 |
+
+| *已知实现类* | *详细说明* |
+| -------------------------------- | --------------------------- |
+| HttpClientRegisterRepository | 基于Http请求的实现 |
+
+
+| *SPI 名称* | *详细说明* |
+| -------------------------------- | ----------------------------- |
+| ShenyuServerRegisterRepository | ShenYu网关客户端注册的后台服务资源 |
+
+| *已知实现类* | *详细说明* |
+| -------------------------------- | ----------------------------- |
+| ShenyuHttpRegistryController | 使用Http服务接口来处理客户端注册请求 |
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/design/spi-design.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/design/spi-design.md
new file mode 100644
index 00000000000..e07e4951046
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/design/spi-design.md
@@ -0,0 +1,42 @@
+---
+title: SPI扩展设计
+keywords: ["spi design"]
+description: 对ShenYu网关中SPI的使用进行介绍
+---
+
+`SPI` 全称为 `Service Provider Interface`, 是 `JDK` 内置的一种服务提供发现功能, 一种动态替换发现的机制。
+
+[shenyu-spi](https://github.com/apache/shenyu/tree/master/shenyu-spi) 是`Apache ShenYu`网关自定义的`SPI`扩展实现，设计和实现原理参考了`Dubbo`的 [SPI扩展实现](https://dubbo.apache.org/zh/docs/v2.7/dev/impls/) 。
+
+
+### 注册中心扩展
+
+通过哪种方式实现服务的注册，当前支持`Consul`、`Etcd`、`Http`、`Nacos`和`Zookeeper`。注册中心的扩展包括客户端和服务端，接口分别为 `ShenyuServerRegisterRepository` 和 `ShenyuClientRegisterRepository` 。
+
+### 监控中心扩展
+
+负责服务的监控，通过`SPI`加载具体实现，当前支持`Prometheus` ，服务接口是 `MetricsService` 。
+
+### 负载均衡扩展
+
+从多个服务提供方中选择一个进行调用，当前支持的算法有`Hash`、`Random` 和 `RoundRobin`，扩展接口是 `LoadBalance` 。
+
+
+### RateLimiter扩展
+
+在`RateLimiter`插件中，使用何种限流算法，当前支持`Concurrent`、`LeakyBucket`、`SlidingWindow` 和 `TokenBucket`，扩展接口是 `RateLimiterAlgorithm` 。
+
+
+### 匹配方式扩展
+
+在添加选择器和规则时，使用哪种匹配方式，当前支持`And`、`Or`，扩展接口是 `MatchStrategy` 。
+
+
+### 条件参数扩展
+
+在添加选择器和规则时，使用哪种条件参数，当前支持`URI`、`RequestMethod`、`Query`、`Post`、`IP`、`Host`、`Cookie` 和 `Header`，扩展接口是 `ParameterData` 。
+
+
+### 条件策略扩展
+
+在添加选择器和规则时，使用哪种条件策略，当前支持`Match`、`Contains`、`Equals`、`Regex`、`TimerAfter`、`TimerBefore`和`Exclude`，扩展接口是 `PredicateJudge` 。
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/design/wasm-plugin-design.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/design/wasm-plugin-design.md
new file mode 100644
index 00000000000..d7da73ed680
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/design/wasm-plugin-design.md
@@ -0,0 +1,25 @@
+---
+title: WASM插件设计
+keywords: ["WASM"]
+description: Apache ShenYu WASM插件设计
+---
+
+`Apache ShenYu`是一个Java原生，用于服务代理、协议转换和API管理的API网关。目前shenyu在Java语言中具有良好的可扩展性，然而shenyu对多种语言的支持仍然相对较弱。
+
+`WASM`(即WebAssembly)字节码被设计为以大小和加载时间高效的二进制格式进行编码。WebAssembly旨在利用各种平台上可用的通用硬件功能，以机器码的速度在浏览器中执行。
+
+`WASI`(即WebAssembly System Interface)则是让WASM可以运行在非浏览器环境中(比如linux)。
+
+`WASMPlugin`的目标是能够运行WASM字节码。其他语言，只要这种语言的代码能被编译成WASM字节码(如Rust/golang/C++)，那么这种语言就可以用来编写ShenYu插件。
+
+## 开发阶段
+
+
+
+## 准备阶段
+
+
+
+## 运行阶段
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/_category_.json b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/_category_.json
new file mode 100644
index 00000000000..35803c66300
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "开发者文档",
+ "position": 7
+}
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/custom-filter.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/custom-filter.md
new file mode 100644
index 00000000000..8bb85010302
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/custom-filter.md
@@ -0,0 +1,113 @@
+---
+title: 自定义Filter
+description: filter扩展
+---
+
+
+## 说明
+
+* 本文介绍如何对 `org.springframework.web.server.WebFliter` 进行扩展。
+
+## 跨域支持
+
+* 新增 `org.apache.shenyu.web.filter.CrossFilter` 实现 `WebFilter`。
+
+```java
+ public class CrossFilter implements WebFilter {
+
+ private static final String ALLOWED_HEADERS = "x-requested-with, authorization, Content-Type, Authorization, credential, X-XSRF-TOKEN,token,username,client";
+
+ private static final String ALLOWED_METHODS = "*";
+
+ private static final String ALLOWED_ORIGIN = "*";
+
+ private static final String ALLOWED_EXPOSE = "*";
+
+ private static final String MAX_AGE = "18000";
+
+ @Override
+ @SuppressWarnings("all")
+ public Mono
+
+> 字典类型：`loadBalance`；
+>
+> 字典编码：`LOAD_BALANCE`；
+>
+> 字典名称：`${spi name}`，填写自定义`spi`的名称；
+>
+> 字典值：使用时，下拉框的值，不要和现有的重复；
+>
+> 字典描述或备注信息：描述信息；
+>
+> 排序： 排序；
+
+* 在添加选择器或规则时，就可以使用自定义的匹配方式：
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/spi/custom-match-mode.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/spi/custom-match-mode.md
new file mode 100644
index 00000000000..a024d89162f
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/spi/custom-match-mode.md
@@ -0,0 +1,71 @@
+---
+title: 自定义匹配方式
+keywords: ["MatchStrategy"]
+description: 自定义匹配方式
+---
+
+本文介绍如何对 `org.apache.shenyu.plugin.base.condition.strategy.MatchStrategy` 进行自定义扩展。
+
+* 新建一个工程，引入如下依赖：
+
+```xml
+
+
+> 字典类型：`matchMode`；
+>
+> 字典编码：`MATCH_MODE`；
+>
+> 字典名称：`${spi name}`，填写自定义`spi`的名称；
+>
+> 字典值：使用时，下拉框的值，不要和现有的重复；
+>
+> 字典描述或备注信息：描述信息；
+>
+> 排序： 排序；
+>
+> 状态：打开或关闭。
+
+* 在添加选择器或规则时，就可以使用自定义的匹配方式：
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/spi/custom-metrics-monitor.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/spi/custom-metrics-monitor.md
new file mode 100644
index 00000000000..ef573e8258f
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/spi/custom-metrics-monitor.md
@@ -0,0 +1,60 @@
+---
+title: 自定义指标监控
+description: 自定义指标监控
+---
+
+## 说明
+
+* 在自定义开发前，请先自定义搭建好网关环境，请参考: [自定义部署](../../deployment/deployment-custom)
+
+* 本文介绍如何对 `org.apache.shenyu.plugin.metrics.spi.MetricsService` 进行自定义扩展。
+
+## 扩展实现
+
+* 新建一个工程，引入如下依赖：
+
+```xml
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/spi/custom-mock-generator.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/spi/custom-mock-generator.md
new file mode 100644
index 00000000000..6335433f2f1
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/spi/custom-mock-generator.md
@@ -0,0 +1,75 @@
+---
+title: 自定义mock数据生成器
+description: 自定义mock数据生成器
+---
+## 说明
+
+1. 本文介绍如何对 `org.apache.shenyu.plugin.mock.generator.Generator` 进行自定义扩展。
+2. mock 数据生成表达式需要满足 `${name|param1|param2|...}` 的格式。
+
+## 扩展实现
+
+* 新建一个工程，引入如下依赖：
+
+```xml
+
+
+> 字典类型：`paramType`；
+>
+> 字典编码：`PARAM_TYPE`；
+>
+> 字典名称：`${spi name}`，填写自定义`spi`的名称；
+>
+> 字典值：使用时，下拉框的值，不要和现有的重复；
+>
+> 字典描述或备注信息：描述信息；
+>
+> 排序： 排序；
+>
+> 状态：打开或关闭。
+
+* 在添加选择器或规则时，就可以使用自定义的条件参数：
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/spi/custom-predicate-judge.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/spi/custom-predicate-judge.md
new file mode 100644
index 00000000000..9415fd95ef9
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/spi/custom-predicate-judge.md
@@ -0,0 +1,120 @@
+---
+title: 自定义条件策略
+keywords: ["PredicateJudge"]
+description: 自定义条件策略
+---
+
+## 说明
+
+* 本文介绍如何对 `org.apache.shenyu.plugin.base.condition.judge.PredicateJudge` 进行自定义扩展。
+* 条件谓语是选择器中连接数据和规则的桥梁，作用是筛选出符合条件的请求。
+* 目前已经存在包括 match, =, regex, contains, TimeBefore, TimeAfter, exclude 共七个条件谓语。
+* 用户可以参考 [judge](https://github.com/apache/shenyu/tree/master/shenyu-plugin/shenyu-plugin-base/src/main/java/org/apache/shenyu/plugin/base/condition/judge) 模块，新增自己的条件谓语，如果有好的公用插件，可以向官网提交 `pr`。
+
+## 扩展
+
+* 新建一个工程，引入如下依赖：
+
+```xml
+
+
+> 字典类型：`operator`；
+>
+> 字典编码：`OPERATOR`；
+>
+> 字典名称：`${spi name}`，填写自定义`spi`的名称；
+>
+> 字典值：使用时，下拉框的值，不要和现有的重复；
+>
+> 字典描述或备注信息：描述信息；
+>
+> 排序： 排序；
+>
+> 状态：打开或关闭。
+
+* 在添加选择器或规则时，就可以使用自定义的条件策略：
+
+
+
+## 示例
+
+* 添加 `GroovyPredicateJudge` 和 `SpELPredicateJudge` 扩展。
+
+```java
+/**
+ * Groovy predicate judge.
+ */
+@Join
+public class GroovyPredicateJudge implements PredicateJudge {
+
+ @Override
+ public Boolean judge(final ConditionData conditionData, final String realData) {
+ return (Boolean) Eval.me(conditionData.getParamName(), realData, conditionData.getParamValue());
+ }
+}
+```
+
+```java
+/**
+ * SpEL predicate judge.
+ */
+@Join
+public class SpELPredicateJudge implements PredicateJudge {
+
+ private static final ExpressionParser EXPRESSION_PARSER = new SpelExpressionParser();
+
+ @Override
+ public Boolean judge(final ConditionData conditionData, final String realData) {
+ Expression expression = EXPRESSION_PARSER.parseExpression(conditionData.getParamValue().replace('#' + conditionData.getParamName(), realData));
+ return expression.getValue(Boolean.class);
+ }
+}
+```
+
+* 更新 `org.apache.shenyu.plugin.base.condition.judge.PredicateJudge`， 添加：
+
+```shell title="script"
+Groovy=xxx.xxx.xxx.GroovyPredicateJudge
+SpEL=xxx.xxx.xxx.SpELPredicateJudge
+```
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/spi/custom-rate-limiter.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/spi/custom-rate-limiter.md
new file mode 100644
index 00000000000..b3573d15fba
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/spi/custom-rate-limiter.md
@@ -0,0 +1,103 @@
+---
+title: 自定义限流策略
+description: 自定义限流策略
+---
+
+
+## 说明
+
+* 在自定义开发前，请先自定义搭建好网关环境，请参考: [自定义部署](../../deployment/deployment-custom)
+
+* 本文介绍如何对 `org.apache.shenyu.plugin.ratelimiter.algorithm.RateLimiterAlgorithm` 进行自定义扩展。
+
+## 扩展实现
+
+* 新建一个工程，引入如下依赖：
+
+```xml
+
+
+* 或者执行以下自定义`SQL`语句：
+
+```sql
+INSERT IGNORE INTO `shenyu_dict` (
+ `id`,
+ `type`,
+ `dict_code`,
+ `dict_name`,
+ `dict_value`,
+ `desc`,
+ `sort`,
+ `enabled`,
+ `date_created`,
+ `date_updated`
+ )
+VALUES (
+ 'you id',
+ 'matchMode',
+ 'MATCH_MODE',
+ 'you spi name',
+ 'you value',
+ 'you spi name',
+ 0,
+ 1,
+ '2021-08-30 19:29:10',
+ '2021-08-30 20:15:23'
+ );
+```
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/thread-model.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/thread-model.md
new file mode 100644
index 00000000000..f284df3406f
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/developer/thread-model.md
@@ -0,0 +1,29 @@
+---
+title: 线程模型
+keywords: ["线程模型"]
+description: 线程模型
+---
+
+## 说明
+
+* 本文主要介绍 `Apache ShenYu` 的线程模型，以及各种场景的使用。
+
+## IO与Work线程
+
+* `Apache ShenYu` 内置依赖 `spring-webflux`， 而其底层是使用的是 `netty`，这一块主要是使用的 `netty` 线程模型。
+
+## 业务线程
+
+* 默认使用调度线程来执行。
+* 默认使用固定的线程池来执行，其线程数为 `cpu * 2 + 1`。
+
+## 切换类型
+
+* `reactor.core.scheduler.Schedulers`。
+* 可以使用 `-Dshenyu.scheduler.type=fixed` 这个是默认。 设置其他的值 就会使用弹性线程池来执行`Schedulers.elastic()`。
+* 可以使用 `-Dshenyu.work.threads = xx` 来指定线程数量，默认为 `cpu * 2 + 1`，最小为`16`个线程。
+
+
+
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/index.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/index.md
new file mode 100644
index 00000000000..7d01a934b3a
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/index.md
@@ -0,0 +1,174 @@
+---
+sidebar_position: 1
+title: Apache ShenYu 介绍
+keywords: ["Apache shenyu"]
+description: Apache ShenYu 是一个异步的，高性能的，跨语言的，响应式的`API`网关。
+---
+
+# 架构图
+
+ 
+
+# 什么是 Apache ShenYu
+
+这是一个异步的，高性能的，跨语言的，响应式的 `API` 网关。
+
+# 为什么叫ShenYu
+
+ ShenYu(神禹)是中国古代君主夏禹(后世亦称大禹)的尊称，他留下了三渡黄河造福人民并成功治理黄河洪水的感人故事。他和尧、舜一起被认为是中国古代三大帝王之一。
+
+* 首先，ShenYu这个名字是为了弘扬我们中华文明的传统美德。
+* 其次，对于网关来说最重要的是流量管理。
+* 最后，社区将以公平、公正、公开、择优的方式做事，在向神禹致敬的同时，也符合 Apache Way。
+
+# 特点
+
+* 代理：支持Apache Dubbo，Spring Cloud，gRPC，Motan，SOFA，TARS，WebSocket，MQTT
+* 安全性：签名，OAuth 2.0，JSON Web令牌，WAF插件
+* API治理：请求、响应、参数映射、Hystrix、RateLimiter插件
+* 可观测性：跟踪、指标、日志记录插件
+* 仪表板：动态流量控制，用户菜单权限的可视化后端
+* 扩展：插件热插拔，动态加载
+* 集群：NGINX、Docker、Kubernetes
+* 语言：提供.NET，Python，Go，Java客户端用于API注册
+
+---
+
+# 脑图
+
+
+
+# 快速开始 (docker)
+
+### 运行 Apache ShenYu Admin
+
+```
+docker pull apache/shenyu-admin
+docker network create shenyu
+docker run -d -p 9095:9095 --net shenyu apache/shenyu-admin
+```
+
+默认账号: **admin**
+
+默认密码: **123456**
+
+### 运行 Apache ShenYu Bootstrap
+
+```
+docker pull apache/shenyu-bootstrap
+docker run -d -p 9195:9195 -e "shenyu.local.enabled=true" --net shenyu apache/shenyu-bootstrap
+```
+
+### 路由设置
+
+* Real requests ：
+
+---
+
+# 贡献与支持
+
+* [贡献方式](https://shenyu.apache.org/community/contributor-guide)
+* [邮件我们](mailto:dev@shenyu.apache.org)
+
+---
+
+# 已知用户
+
+按注册顺序，欢迎更多接入公司在 https://github.com/apache/shenyu/issues/68 注册（仅限开源用户）。
+
+用户 : [已知用户](https://shenyu.apache.org/community/user-registration)
+
+---
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/_category_.json b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/_category_.json
new file mode 100644
index 00000000000..4b82d108723
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "插件集合",
+ "position": 6
+}
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/cache/_category_.json b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/cache/_category_.json
new file mode 100644
index 00000000000..1452462222c
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/cache/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "缓存123",
+ "position": 7
+}
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/cache/cache-plugin.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/cache/cache-plugin.md
new file mode 100644
index 00000000000..8c7d33419aa
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/cache/cache-plugin.md
@@ -0,0 +1,149 @@
+---
+title: 缓存插件
+keywords: ["缓存"]
+description: 缓存插件
+---
+
+
+# 1. 概述
+
+## 1.1 插件名称
+
+* 缓存插件
+
+## 1.2 适用场景
+
+* 数据不会频繁更新，而且需要大量调用的场景。
+
+* 对于数据一致性要求不高的场景。
+
+## 1.3 插件功能
+
+* `Cache`插件能够缓存目标服务的结果，允许用户配置缓存结果的失效时间。
+
+## 1.4 插件代码
+
+* 核心模块 `shenyu-plugin-cache-handler`.
+* 核心模块 `shenyu-plugin-cache-redis`.
+* 核心模块 `shenyu-plugin-cache-memory`.
+
+* 核心类 `org.apache.shenyu.plugin.cache.CachePlugin`
+* 核心类 `org.apache.shenyu.plugin.cache.redis.RedisCache`
+* 核心类 `org.apache.shenyu.plugin.cache.memory.MemoryCache`
+
+## 1.5 添加自哪个shenyu版本
+
+* 2.4.3
+
+# 2. 如何使用插件
+
+## 2.1 插件使用流程图
+
+
+
+## 2.2 导入pom
+
+* 在`ShenYu Bootstrap`导入cache插件的依赖。
+
+```xml
+
+
+
+
+* 在网关的 `pom.xml` 文件中添加 `generalContext` 的支持。
+
+
+```xml
+
+ 
+
+
+## 在网关中引入 resilience4j 插件
+
+* 在网关的 `pom.xml` 文件中添加 `resilience4j`的依赖。
+
+```xml
+
+ 
+
+#### 规则配置
+
+用于对流量最终筛选，有规则处理逻辑。
+
+
+
+
+* `resilience4j`处理详解：
+
+ * `limitForPeriod`：每次刷新令牌的数量，默认值：`50`。
+
+ * `limitRefreshPeriod`：刷新令牌的时间间隔，单位`ms`，默认值：`500`。
+
+ * `timeoutDurationRate`：等待获取令牌的超时时间，单位`ms`，默认值：`5000`。
+
+ * `circuitEnable`：是否开启熔断，`0`：关闭，`1`：开启，默认值：`0`。
+
+ * `failureRateThreshold`：错误率百分比，达到这个阈值，熔断器才会开启，默认值：`50`。
+
+ * `fallbackUri`：降级处理的`uri`。
+
+ * `minimumNumberOfCalls`：开启熔断的最小请求数，超过这个请求数才开启熔断统计，默认值：`100`。
+
+ * `bufferSizeInHalfOpen`：半开状态下的环形缓冲区大小，必须达到此数量才会计算失败率，默认值：`10`。
+
+ * `slidingWindowSize`：滑动窗口大小，默认值：`100`。
+
+ * `slidingWindowType`：滑动窗口类型，`0`：基于计数，`1`：基于时间，默认值：`0`。
+
+ * `timeoutDuration`：熔断超时时间，单位`ms`，默认值：`30000`。
+
+ * `waitIntervalInOpen`：熔断器开启持续时间，单位`ms`，默认值：`60000`。
+
+ * `automaticTransitionFromOpenToHalfOpenEnabled`：是否自动从`open`状态转换为`half-open`状态，`true`：是，`false`：否，默认值：`false`。
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/fault-tolerance/sentinel-plugin.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/fault-tolerance/sentinel-plugin.md
new file mode 100644
index 00000000000..0c6d2f7072b
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/fault-tolerance/sentinel-plugin.md
@@ -0,0 +1,216 @@
+---
+title: Sentinel插件
+keywords: ["Sentinel"]
+description: sentinel插件
+---
+
+# 1. 概述
+
+## 1.1 插件名称
+
+* Sentinel插件
+
+## 1.2 适用场景
+
+* `sentinel`插件是网关用来对流量进行限流与熔断的可选选择之一。
+* `sentinel`插件为网关熔断限流提供能力。
+
+## 1.3 插件功能
+
+* 流量控制
+* 请求熔断和服务降级
+
+## 1.4 插件代码
+
+* 核心包 `shenyu-plugin-sentinel`.
+
+* 核心类 `org.apache.shenyu.plugin.sentinel.SentinelPlugin`
+
+## 1.5 添加自哪个shenyu版本
+
+* 2.4.0
+
+# 2. 如何使用插件
+
+## 2.1 插件使用流程图
+
+
+
+## 2.2 导入pom
+
+* 在网关的 `pom.xml` 文件中添加 `sentinel` 依赖。
+
+```xml
+
+
+
+### 2.4.3 规则配置
+
+用于对流量最终筛选，有规则处理逻辑。
+
+
+
+| field | default value | field type | desc |
+|-----------------------------------------------------|--------------------|------------|----------------------------------------------------------------------------------------------------------------------------|
+| degradeRuleCount | | Doule | 降级阈值 |
+| degradeRuleEnable | 1(enabled) | Integer | (是否开启流控 (1或0) ) ：是否开启`sentinel`的流控。 |
+| degradeRuleGrade | 0(slow call ratio) | Integer | (断路器策略): 支持秒级RT/秒级Error Ratio/分钟级Error Count策略。 |
+| degradeRuleMinRequestAmount | 5 | Integer | 断路器最小请求量。 |
+| degradeRuleSlowRatioThreshold | 1.0d | Double | 退化的慢比率阈值。 |
+| degradeRuleStatIntervals | 1 | Integer | 降级的状态间隔。 |
+| degradeRuleTimeWindow | | Integer | 退化时间（单位：秒）。 |
+| flowRuleControlBehavior | 0(direact reject) | Integer | 效果（直接拒绝/排队/慢启动/冷启动+匀速器），不支持调用关系流控。 |
+| flowRuleControlBehavior-direct rejection by default | | | direct rejection by default （直接拒绝） |
+| flowRuleControlBehavior-warm up | | | warm up （冷启动） |
+| flowRuleControlBehavior-constant speed queuing | | | constant speed queuing （匀速排队，漏桶算法 ） |
+| flowRuleControlBehavior-preheating uniformly queued | | | 冷启动+匀速器，除了让流量缓慢增加，还还控制的了请求的间隔时间，让请求均匀速度通过。） |
+| flowRuleMaxQueueingTimeMs | 500ms | Integer | 最大排队等待时长（在 “preheating uniformly queued“, “constant speed queuing“ 模式生效）。 |
+| flowRuleWarmUpPeriodSec | 10 | Integer | 冷启动预热时长（秒） (在 “preheating uniformly queued” “warm up” 模式下生效) |
+| flowRuleCount | | Integer | 哨兵流控制计数。 |
+| flowRuleEnable | 1(enabled) | Integer | 是否开启哨兵流控功能。 |
+| flowRuleGrade | 1(QPS) | Integer | 限流阈值的类型（QPS 或 Thread Count）。 |
+| fallbackUri | | String | 断路后降级的uri。 |
+
+## 2.5 示例
+
+### 2.5.1 使用sentinel进行流量控制
+
+#### 2.5.1.1 插件配置
+
+* 在 基础配置 `-->` 插件管理 `-->` `sentinel`，设置为开启。
+
+#### 2.5.1.2 选择器配置
+
+
+
+#### 2.5.1.3 规则配置
+
+关于选择器和规则配置的更多说明，请参考：[选择器和规则管理](../../user-guide/admin-usage/selector-and-rule)， 这里只对部分字段进行了介绍。
+
+
+
+使用qps限流策略，并且qps为10，拒绝策略为直接拒绝。
+
+代码如下：
+
+```java
+@RestController
+@RequestMapping("/order")
+@ShenyuSpringMvcClient("/order")
+public class OrderController {
+
+ /**
+ * Save order dto.
+ *
+ * @param orderDTO the order dto
+ * @return the order dto
+ */
+ @PostMapping("/save")
+ @ShenyuSpringMvcClient("/save")
+ public OrderDTO save(@RequestBody final OrderDTO orderDTO) {
+ orderDTO.setName("hello world save order");
+ return orderDTO;
+ }
+}
+```
+
+#### 2.5.1.4 通过`Apache Jmeter`请求网关
+
+* Jmeter线程组配置
+
+
+
+* Jmeter http请求配置
+
+
+
+#### 2.5.1.5 验证结果
+
+
+
+### 2.5.2 使用sentinel进行熔断降级控制
+
+#### 2.5.2.1 插件配置
+
+* 在 基础配置 `-->` 插件管理 `-->` `sentinel`，设置为开启。
+
+#### 2.5.2.2 选择器配置
+
+
+
+#### 2.5.2.3 规则配置
+
+
+
+当degrade strategy为`exception number`时，`degradeRuleSlowRatioThreshold`无效。 当单位时间内的最小请求数为 5，且请求发生的异常大于 3 时，将触发断路器。
+
+当degrade strategy为`slow call ratio`时，`degradeRuleSlowRatioThreshold`有效，`degradeRuleCount`表示RT（例如200）。
+
+
+代码如下：
+
+```java
+@RestController
+@RequestMapping("/order")
+@ShenyuSpringMvcClient("/order")
+public class OrderController {
+
+ /**
+ * Save order dto.
+ *
+ * @param orderDTO the order dto
+ * @return the order dto
+ */
+ @PostMapping("/save")
+ @ShenyuSpringMvcClient("/save")
+ public OrderDTO save(@RequestBody final OrderDTO orderDTO) {
+
+ Random random = new Random();
+ int num = random.nextInt(100);
+ if (num > 40) {
+ throw new RuntimeException("num great than 20");
+ }
+ orderDTO.setName("hello world save order");
+ return orderDTO;
+ }
+
+}
+```
+
+#### 2.5.2.4 通过`Apache Jmeter`请求网关
+
+* Jmeter线程组配置
+
+
+
+* Jmeter http请求配置
+
+
+
+#### 2.5.2.5 验证结果
+
+
+
+# 3. 如何禁用插件
+
+* 在 基础配置 `-->` 插件管理 `-->` `sentinel`，设置为关闭。
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/http-process/_category_.json b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/http-process/_category_.json
new file mode 100644
index 00000000000..ce33bac3bfa
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/http-process/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Http处理",
+ "position": 1
+}
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/http-process/contextpath-plugin.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/http-process/contextpath-plugin.md
new file mode 100644
index 00000000000..053ea88dfd7
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/http-process/contextpath-plugin.md
@@ -0,0 +1,124 @@
+---
+title: Context Path插件
+keywords: ["contextPath"]
+description: contextPath插件
+---
+
+# 1. 概述
+
+## 1.1 插件名称
+
+* 上下文路径插件
+
+## 1.2 适用场景
+
+* 不同的服务可以通过设置不同的上下文路径来做服务的流量治理
+
+## 1.3 插件功能
+
+* 设置服务的上下文路径
+* 在接口调用的时候插件统一给服务的接口地址加上前缀
+
+## 1.4 插件代码
+
+* 核心模块 ```shenyu-plugin-context-path```
+* 核心类 ```org.apache.shenyu.plugin.context.path.ContextPathPlugin```
+
+## 1.5 添加自哪个 shenyu 版本
+
+* 2.3.0
+
+# 2. 如何使用插件
+
+## 2.1 插件使用流程图
+
+
+
+## 2.2 导入 pom
+
+- 在网关的 `pom.xml` 文件中添加插件 maven 配置。
+
+```xml
+ 
+
+
+## 插件使用
+
+- 在网关的 `pom.xml` 文件中添加 `redirect` 的支持。
+
+```xml
+
+ 
+
+
+#### 网关自身接口转发
+
+* 当满足匹配规则时，服务内部会使用 `DispatcherHandler` 内部接口转发。
+* 要实现网关自身接口转发，我们需要在配置路径使用 `/` 作为前缀开始，具体配置如下图。
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/http-process/request-plugin.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/http-process/request-plugin.md
new file mode 100644
index 00000000000..22355e65b50
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/http-process/request-plugin.md
@@ -0,0 +1,90 @@
+---
+title: Request插件
+keywords: ["RequestPlugin"]
+description: RequestPlugin
+---
+
+# 1. 概述
+
+## 1.1 插件名称
+
+- Request(请求)插件
+
+## 1.2 适用场景
+
+- 请求插件能够对 `uri` 的请求参数进行自定义修改。
+
+## 1.3 插件功能
+
+- `Apache ShenYu` 网关在对目标服务进行代理调用的时候，允许用户使用 `request` 插件对请求参数、请求头以及 `Cookie` 来添加、修改、移除请求头。
+
+## 1.4 插件代码
+
+- 核心模块 ```shenyu-plugin-redirect```
+- 核心类 ```org.apache.shenyu.plugin.request.RequestPlugin```
+
+## 1.5 添加自哪个 shenyu 版本
+
+- 2.4.0
+
+# 2. 如何使用插件
+
+## 2.1 插件使用流程图
+
+
+
+## 2.2 导入 pom
+
+- 在网关的 `pom.xml` 文件中添加插件 maven 配置，默认已经添加。
+
+```xml
+
+ 
+
+## 2.4 配置插件
+
+- 选择器和规则，只有匹配的请求，才会进行转发和重定向，请参考：[选择器规则管理](../../user-guide/admin-usage/selector-and-rule)。
+- `shenyu-admin`插件列表 --> `HttpProcess` --> `Request`，先添加选择器，然后添加规则：
+- 添加选择器：
+
+ 
+
+- 添加规则：
+
+ 
+
+## 2.5 示例
+
+### 2.5.1 添加请求参数
+
+- 我们在 `规则` 配置自定义路径时，应该为一个可达的服务路径。
+- 当匹配到请求后，根据自定义的路径，`Apache ShenYu`网关会进行服务跳转。
+1. 参考[本地部署](https://shenyu.apache.org/zh/docs/deployment/deployment-local)启动 admin 和网关
+2. 参考2.2导入 pom 并重启网关
+3. 参考2.3启用插件
+4. 启动 [shenyu-examples-http](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http) 项目
+5. 参考2.4及[选择器规则管理](../../user-guide/admin-usage/selector-and-rule)配置插件规则
+6. 接口调用：[http-test-api.http](https://github.com/apache/shenyu/blob/master/shenyu-examples/shenyu-examples-http/src/main/http/http-test-api.http)
+- 调用选择器和规则声明的接口，将会看到request插件中配置的请求参数。
+
+ 
+
+# 3. 如何禁用插件
+
+- 在 `shenyu-admin` --> 基础配置 --> 插件管理 --> `Request` 设置为禁用。
+
+ 
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/http-process/rewrite-plugin.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/http-process/rewrite-plugin.md
new file mode 100644
index 00000000000..7488d92b5d8
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/http-process/rewrite-plugin.md
@@ -0,0 +1,103 @@
+---
+title: Rewrite插件
+keywords: ["rewrite"]
+description: rewrite插件
+---
+
+# 1. 概述
+
+## 1.1 插件名称
+
+* Rewrite插件
+
+## 1.2 适用场景
+
+* 通过重写请求路径, 可以使用与目标服务不同的uri。
+
+## 1.3 插件功能
+
+* 该插件用于重写请求uri。
+
+## 1.4 插件代码
+
+* 核心模块 `shenyu-plugin-rewrite`
+
+* 核心类 `org.apache.shenyu.plugin.rewrite.RewritePlugin`
+
+## 1.5 添加自哪个Shenyu版本
+
+* 2.4.0
+
+# 2. 如何使用插件
+
+## 2.1 插件使用流程图
+
+
+
+## 2.2 导入pom
+
+- 在网关的 `pom.xml` 文件中添加插件 maven 配置。
+
+```xml
+ 
+
+ * `corethreads`：业务线程池核心线程数。
+
+ * `queues`：业务线程池阻塞队列长度，0表示`无界阻塞队列`。
+
+ * `threadpool`：业务线程池类型，有`fixed`、`eager`、`cached`、`limited`和`shared`共5种类型，前面4种与dubbo官方提供的线程池一一对应，不多解释，这里单独说下`shared`，正如其名，`所有proxy插件`共用一个`shared`线程池，这样做的好处是能够减少线程池数量，进而降低内存、提高资源利用率。
+
+ * `threads`：业务线程池最大线程数。
+
+## 插件详解
+
+客户端接入`Apache ShenYu`网关后，会自动注册选择器和规则信息，关于选择器和规则配置，请参考：[选择器和规则管理](../../user-guide/admin-usage/selector-and-rule) 。
+
+#### 选择器处理
+
+
+
+选择器处理，即`handle`字段，是网关匹配到流量以后，可以进行处理的操作。更多信息请参考插件管理中的 [插件处理管理](../../user-guide/admin-usage/plugin-handle-explanation) 。
+
+* 处理配置详解：
+
+ * `host`：host地址。
+
+ * `ip:port`：ip+port地址。
+
+ * `protocol`：协议默认值为'http'。
+
+ * `group`：dubbo服务的组。
+
+ * `version`：dubbo服务版本号。
+
+ * `weight`：服务实例的权重。
+
+ * `warmupTime`：服务预热时间。
+
+ * `startupTime`：服务开启时间。
+
+ * `status`：true: 服务节点可用，false: 服务节点不可用.
+
+ * `gray`：灰度状态.
+
+灰度路由
+
+如果您想在dubbo插件中使用灰色路由，可以单击“灰色”按钮。
+
+* 灰度发布可以在发布新版本应用时，自定义控制新版本应用流量比重，渐进式完成新版本应用的全量上线，最大限度地控制新版本发布带来的业务风险，降低故障带来的影响面，同时支持快速回滚。
+
+当开启灰度是，网关的负载平衡算法将从当前节点列表中选择一个节点进行路由，并且您可以通过修改节点权重以更改负载平衡算法中节点的权重。
+
+需要注意的是，如果您的业务实例没有使用'shenyu-client-apache-dubbo'或者'shenyu-client-alibaba-dubbo'的客户端进行业务注册发现，您应该在当前选择器页面上手动添加节点信息进行灰度路由。
+
+#### 规则处理
+
+
+
+规则处理，即`handle`字段，是网关对流量完成最终匹配后，可以进行处理的操作。更多信息请参考插件管理中的 [插件处理管理](../../user-guide/admin-usage/plugin-handle-explanation) 。
+
+* 处理配置详解：
+
+ * `loadbalance`：负载均衡策略，如果选择灰度节点失败，将会使用默认的负载均衡方式。
+
+* Apache ShenYu将获得相应服务的真实IP，并从dubbo注册中心发起rpc代理调用。
+
+## 元数据
+
+每一个`dubbo`接口方法，都会对应一条元数据，当`dubbo`应用客户端接入到`Apache ShenYu`网关时，会自动注册，可以在 `shenyu-admin`后台管理系统的基础配置 `-->` 元数据管理中查看。
+
+
+
+* 应用名称：该条元数据所属的应用名称。
+
+* 方法名称：需要调用的方法名。
+
+* 路径：`http`请求路径。
+
+* 路径描述：对该路径的说明，方便查看。
+
+* 参数类型：`dubbo`接口的参数类型列表，此处有两种声明方式。例如一个接口为 `update(Integer id, String name, Integer age)`
+
+ 方式一、类型列表
+
+ ```yaml
+ java.lang.Integer,java.lang.String,java.lang.Integer
+ ```
+
+ * 按照接口的参数类型顺序，通过半角逗号分隔。
+ * 请求传参时需**严格按照参数类型顺序传参**，没有值的用 `null`占位 。请求体示例：`{"id":1,"name": null,"age":18}`
+
+ 方式二、名称映射
+
+ ```yaml
+ {"id":"java.lang.Integer","name":"java.lang.String","age":"java.lang.Integer"}
+ ```
+
+ * 使用 `"参数名":"参数类型"`表示一个参数，按接口参数类型顺序设置，半角逗号分隔。
+ * 请求时无需关注顺序，也无需使用null占位。请求体示例: `{"name":"Mike","id":1}`
+
+* Rpc扩展参数：`dubbo`接口的其他配置，支持`json`格式，字段如下：
+
+```yaml
+{"timeout":10000,"group":"",version":"","loadbalance":"","retries":1}
+```
+
+* 服务接口：`dubbo`接口的全限定类名
+
+* `Rpc`类型：此处选择 `dubbo`。
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/proxy/grpc-plugin.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/proxy/grpc-plugin.md
new file mode 100644
index 00000000000..a3c9cb2a435
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/proxy/grpc-plugin.md
@@ -0,0 +1,81 @@
+---
+title: gRPC插件
+keywords: ["gRPC"]
+description: gRPC插件
+---
+
+
+## 说明
+
+`gRPC`插件是网关用于处理 `gRPC协议`请求的核心处理插件。
+
+## 插件设置
+
+* 引入相关依赖，开启插件，请参考：[gRPC快速开始](../../quick-start/quick-start-grpc) 。
+
+* `gRPC`应用客户端接入，请参考：[gRPC服务接入](../../user-guide/proxy/grpc-proxy.md) 。
+
+* 自`2.4.3版本`起grpc插件新增字段及含义：
+
+ * `threadpool`：业务线程池类型，有`cached`和`shared`共2种类型。
+
+ `cached`相当于grpc官方提供的默认线程池；
+
+ `shared`线程池，正如其名，`所有proxy插件`共用一个`shared`线程池，这样做的好处是能够减少线程池数量，进而降低内存、提高资源利用率。
+
+
+## 插件讲解
+
+
+客户端接入`Apache ShenYu`网关后，会自动注册选择器和规则信息，可以在插件列表 `->` rpc proxy `->` grpc 中查看。 关于选择器和规则配置，请参考：[选择器和规则管理](../../user-guide/admin-usage/selector-and-rule)。
+
+
+
+#### 选择器处理
+
+
+
+
+选择器处理，即`handle`字段，是网关匹配到流量以后，可进行的处理操作。
+
+* 处理配置详解：
+
+
+ * `ip:port`：`ip` 与端口，这里填写你真实服务的 `ip` + 端口。
+
+ * `protocol`：`http` 协议，一般填写 `http://` 或者 `https://` ，不填写默认为:`http://`
+
+ * `weight`：服务权重。
+
+ * `status`：开启或关闭。
+
+
+## 元数据
+
+每一个`grpc`接口方法，都会对应一条元数据，当`gRPC`应用客户端接入到`Apache ShenYu`网关时，会自动注册，可以在 `shenyu-admin`后台管理系统的基础配置 `-->` 元数据管理中查看。
+
+
+
+
+* 应用名称：该条元数据所属的应用名称。
+
+* 方法名称：需要调用的方法名。
+
+* 路径：`http`请求路径。
+
+* 路径描述：对该路径的说明，方便查看。
+
+* 参数类型：`grpc`接口的参数类型列表，按照接口的参数类型顺序，通过半角逗号分隔。
+
+* Rpc扩展参数：`grpc`接口的其他配置，支持`json`格式，字段如下：
+
+```json
+{
+ "timeout": 5000,
+ "methodType": "BIDI_STREAMING"
+}
+```
+
+* 服务接口：`grpc`接口的全限定类名
+
+* `Rpc`类型：此处选择 `grpc`。
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/proxy/motan-plugin.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/proxy/motan-plugin.md
new file mode 100644
index 00000000000..b1b4b448005
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/proxy/motan-plugin.md
@@ -0,0 +1,59 @@
+---
+title: Motan插件
+keywords: ["Motan"]
+description: Motan插件
+---
+
+## 说明
+
+`Motan`插件是网关用于处理 `Motan协议`请求的核心处理插件。
+
+## 插件设置
+
+* 引入相关依赖，开启插件，请参考：[Motan快速开始](../../quick-start/quick-start-motan) 。
+
+* `Motan`应用客户端接入，请参考：[Motan服务接入](../../user-guide/proxy/motan-proxy.md) 。
+
+
+## 插件讲解
+
+客户端接入`Apache ShenYu`网关后，会自动注册选择器和规则信息，可以在插件列表 `->` rpc proxy `->` motan 中查看。 关于选择器和规则配置，请参考：[选择器和规则管理](../../user-guide/admin-usage/selector-and-rule)。
+
+#### 元数据
+
+每一个`motan`接口方法，都会对应一条元数据，当`motan`应用客户端接入到`Apache ShenYu`网关时，会自动注册，可以在 `shenyu-admin`后台管理系统的基础配置 `-->` 元数据管理中查看。
+
+
+
+* 应用名称：该条元数据所属的应用名称。
+
+* 方法名称：需要调用的方法名。
+
+* 路径：`motan`请求路径。
+
+* 路径描述：对该路径的说明，方便查看。
+
+* 参数类型：`motan`接口的参数类型列表，按照接口的参数类型顺序，通过半角逗号分隔。
+
+* Rpc扩展参数：描述了一个`motan`服务中每个接口信息。比如，下面是`motan`服务的接口信息：
+
+```json
+{
+ "methodInfo": [
+ {
+ "methodName": "hello",
+ "params": [
+ {
+ "left": "java.lang.String",
+ "right": "name"
+ }
+ ]
+ }
+ ],
+ "group": "motan-shenyu-rpc"
+}
+```
+
+* 服务接口：`motan`服务接口全限定名。
+
+* `Rpc`类型：下拉选择 `motan`。
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/proxy/mqtt-plugin.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/proxy/mqtt-plugin.md
new file mode 100644
index 00000000000..777a67f957a
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/proxy/mqtt-plugin.md
@@ -0,0 +1,50 @@
+---
+title: Mqtt 插件
+keywords: ["Mqtt"]
+description: Mqtt 插件
+---
+
+## 描述
+
+* 当前 MQTT 协议实现为 3.1 版本，实现的标识值为 `connect`、`publish`、`subscribe`、`unsubscribe`、`disconnect`、`PingReq`、`PingResp`，以及 QoS 0。
+
+* 缺少 retain、Qos（1，2） 实现，以及集群模式。
+
+* 具体请看 http://public.dhe.ibm.com/software/dw/webservices/ws-mqtt/mqtt-v3r1.html 内容
+
+## 引入 Mqtt 网关的插件支持
+
+* 在网关的 pom.xml 文件中引入这些依赖项。
+
+```xml
+
+
+
+## 2.5 配置插件
+
+### 2.5.1 插件配置
+
+* 你必须配置你的服务注册发现中心并将插件打开。
+
+### 2.5.2 选择器和灰度流量配置
+
+
+
+* 灰度路由
+
+如果您想在springCloud插件中使用灰色路由，可以单击“灰色”按钮。
+
+
+
+* 灰度发布可以在发布新版本应用时，自定义控制新版本应用流量比重，渐进式完成新版本应用的全量上线，最大限度地控制新版本发布带来的业务风险，降低故障带来的影响面，同时支持快速回滚。
+
+当开启灰度是，网关的负载平衡算法将从当前节点列表中选择一个节点进行路由，并且您可以通过修改节点权重以更改负载平衡算法中节点的权重。
+
+
+
+需要注意的是，如果您的业务实例没有使用`shenyu-client-springcloud`的客户端进行业务注册发现，您应该在当前选择器页面上手动添加节点信息进行灰度路由。
+
+* 处理配置详解：
+
+ * `serviceId`:serviceId。
+
+ * `gray`：启用灰度路由。
+
+ * `protocol`：协议默认值为'http://'。
+
+ * `upstreamUrl`: 服务器节点地址。
+
+ * `weight`: 服务器节点权重。
+
+ * `status`:true：服务器可用，false：服务器不可用。
+
+ * `timestamp`：节点的启动时间。
+
+ * `warmup`：节点的预热时间，参与负载均衡计算。
+
+
+### 2.5.3 规则配置
+
+规则处理，即`handle`字段，是网关对流量完成最终匹配后，可以进行处理的操作。更多信息请参考插件管理中的 [插件处理管理](../../user-guide/admin-usage/plugin-handle-explanation) 。
+
+* 使用 `shenyu-client-springcloud` 的规则配置
+
+
+
+* 规则配置详解：
+
+ * `timeout`：设置请求超时时间。
+ * `loadbalance`：负载均衡算法，有三个可选项：`roundRobin`,`random`,`hash`
+
+* 未使用 `shenyu-client-springcloud` 的规则配置
+
+
+
+* 规则配置详解：
+
+ * `path`：请求路径。
+ * `timeout`：设置请求超时时间。
+
+### 2.5.4 SpringCloud服务实例缓存配置
+
+你能在`shenyu-bootstrap.yml`文件中修改如下配置：
+
+```yaml
+shenyu:
+ springCloudCache:
+ enabled: false
+```
+
+此配置将帮助您在每次心跳时从springcloud注册中心获取serviceInstance(通过监听springcloud心跳事件)
+
+* 当您使用nacos或者eureka作为注册中心时，您可以将springcloud serviceInstance缓存设置为`false`。
+* 当您使用zookeeper或者consul作为注册中心时，您可以将springcloud serviceInstance缓存设置为`true`。
+
+## 2.6 示例
+
+### 2.6.1 使用ShenYu访问SpringCloud服务
+
+#### 2.6.1.1 准备工作
+
+- 启动 `Eureka` 或 `Nacos` 服务注册发现中心, 如果你使用eureka, 启动 `shenyu-examples-eureka`即可
+- 启动 `ShenYu Admin`
+- 启动 `shenyu-examples-springcloud`
+
+#### 2.6.1.2 插件配置
+
+- 在 `shenyu-admin` --> 基础配置 --> 插件管理-> `springCloud` ，设置为开启。
+
+- 在`ShenYu Bootstrap`配置服务注册发现中心, 请查看 [2.3 在ShenYu Bootstrap配置SpringCloud](#2.3 在ShenYu Bootstrap配置SpringCloud)
+
+#### 2.6.1.3 选择器配置
+
+
+
+如果你想使用注册到ShenYu的灰度流量，你必须配置灰度路由。
+
+
+
+#### 2.6.1.4 规则配置
+
+如果你使用`shenyu-client-springcloud`注册服务到`ShenYu`,你可以不用配置规则，如果你想改变规则，请查看[2.5.3 规则配置](#2.5.3 规则配置)
+
+#### 2.6.1.5 请求服务并且验证结果
+
+
+
+### 2.6.2 使用ShenYu访问未注册到ShenYu的SpringCloud服务
+
+#### 2.6.2.1 准备工作
+
+- 启动 `Eureka` 或 `Nacos` 服务注册发现中心, 如果你使用eureka, 启动 `shenyu-examples-eureka`即可
+- 启动 `ShenYu Admin`
+- 启动 `shenyu-examples-springcloud`
+
+#### 2.6.2.2 插件配置
+
+- 在 `shenyu-admin` --> 基础配置 --> 插件管理-> `springCloud` ，设置为开启。
+
+- 在`ShenYu Bootstrap`配置服务注册发现中心, 请查看 [2.3 在ShenYu Bootstrap配置SpringCloud](#2.3 在ShenYu Bootstrap配置SpringCloud)
+
+#### 2.6.2.3 选择器配置
+
+
+
+如果你想使用未注册到ShenYu的灰度流量，你必须配置灰度流量相关的配置
+
+
+
+#### 2.6.2.4 规则配置
+
+
+
+你必须在规则配置中配置`path`字段，`path`字段为你的服务uri，例如：`/springcloud/new/feature/gateway/not`, `timeout`为你的服务允许的超时时间。
+
+#### 2.6.2.5 通过配置访问未注册的服务
+
+##### 2.6.2.5.1 在请求头使用 `rpc_type`字段进行访问
+
+```
+### shengyu getway proxy not support
+POST http://localhost:9195/springcloud/new/feature/gateway/not
+Accept: application/json
+Content-Type: application/json
+rpc_type: springCloud
+```
+
+##### 2.6.2.5.2 在ShenYuAdmin 添加元信息
+
+
+
+#### 2.6.2.6 请求服务并且验证结果
+
+
+
+
+# 3. 如何禁用插件
+
+- 在 `shenyu-admin` --> 基础配置 --> 插件管理-> `springCloud` ，设置为关闭。
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/proxy/tars-plugin.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/proxy/tars-plugin.md
new file mode 100644
index 00000000000..af85792d937
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/plugin-center/proxy/tars-plugin.md
@@ -0,0 +1,169 @@
+---
+title: Tars插件
+keywords: ["Tars"]
+description: Tars插件
+---
+
+# 1. 概述
+
+## 1.1 插件名称
+
+- Tars插件
+
+## 1.2 适用场景
+
+- 协议转换，将 http 协议的请求转换成 Tars 框架协议的服务处理的插件
+- 服务负载均衡
+
+## 1.3 插件功能
+
+- 将 http 协议的请求转换成 Tars 框架协议
+
+## 1.4 插件代码
+
+- 核心模块`shenyu-plugin-tars`
+- 核心类`org.apache.shenyu.plugin.tars.TarsPlugin`
+
+## 1.5 添加自哪个shenyu版本
+
+- 2.3.0
+
+# 2. 如何使用插件
+
+## 2.1 插件使用流程图
+
+
+
+## 2.2 导入pom
+
+```xml
+ 
+
+2. 打开 `selector` 配置需要匹配的流量。
+
+3. 打开 `selector` 对应的 `Rules` 配置。
+
+ 
+
+* strategyName: 解密算法名称。当前基于 shenyu 的 SPI 机制，可自定义加解密算法，
+ 需要实现 `org.apache.shenyu.plugin.cryptor.strategy.CryptorStrategy` 接口。
+
+ 同时找到 `resources/META-INF/shenyu/` 底下的 `org.apache.shenyu.plugin.cryptor.strategy.CryptorStrategy` 文件，
+ 写上算法名称以及实现的 `CryptorStrategy` 接口的 class 的包名。
+
+* fieldNames: 匹配的参数名，支持解析多层次的 json 格式匹配，使用 `.` 分割，例如 data.id 。
+
+```json5
+ {
+ data: {
+ "id": ""
+ }
+ }
+```
+
+* decryptKey: 密钥，用于解密数据。
+
+* encryptKey: 密钥，用于加密数据。
+
+* way: 选择加密或解密。
+
+## 插件使用
+
+* 在网关的 `pom.xml` 文件中添加 `cryptorRequest` 的支持。
+
+```xml
+
+
+
+2. 打开 `selector` 配置需要匹配的流量。
+
+3. 打开 `selector` 对应的 `Rules` 配置。
+
+
+
+* strategyName: 解密算法名称。当前基于 shenyu 的 SPI 机制，可自定义加解密算法，
+ 需要实现 `org.apache.shenyu.plugin.cryptor.strategy.CryptorStrategy` 接口。
+
+ 同时找到 `resources/META-INF/shenyu/` 底下的 `org.apache.shenyu.plugin.cryptor.strategy.CryptorStrategy` 文件，
+ 写上算法名称以及实现的 `CryptorStrategy` 接口的 class 的包名。
+
+* fieldNames: 匹配的参数名，支持解析多层次的 json 格式匹配，使用 `.` 分割，例如 data.id 。
+
+```json5
+ {
+ data: {
+ "id": ""
+ }
+ }
+```
+
+* decryptKey: 密钥，用于解密数据。
+
+* encryptKey: 密钥，用于加密数据。
+
+* way: 选择加密或解密。
+
+## 插件使用
+
+* 在网关的 `pom.xml` 文件中添加 `cryptorResponse` 的支持。
+
+```xml
+
+
+
+## 插件使用
+
+- 在网关的pom文件中添加`oauth2`的支持
+
+```xml
+
+ 
+
+第二步，配置这条认证信息 。
+
+
+
+- 应用名称：这个账号关联的应用名称，可手动填写或下拉选择（数据来自元数据管理中配置的应用名称）。
+- 手机号：仅作为信息记录，在shenyu中无实际使用逻辑。
+- APP参数：当请求的context path与应用名称相同时，向header中添加该值，键为 `appParam`。
+- 用户ID：给该用户取一个名字，仅作为信息记录，在shenyu中无实际使用逻辑。
+- 拓展信息：仅作为信息记录，在shenyu中无实际使用逻辑。
+- 路径认证：开启后，该账号仅允许访问以下配置的资源路径。
+- 资源路径：允许访问的资源路径，支持路径匹配，如 `/order/**` 。
+
+点击确认后，生成一条认证信息，该信息包含 `AppKey` 和 `加密秘钥` ，即 `Sign` 插件中的 `AK/SK` 。
+
+#### 2.4.1.3 路径操作
+
+对已创建的认证信息，可以在认证信息列表的末尾进行 `路径操作` 。
+
+
+
+- 左侧为可配置的路径列表，右侧为允许该账号访问的路径列表 。
+- 勾选资源路径，点击中间的 `>` 或 `<` 将勾选的数据移动到对应列表中 。
+- 左侧可配置路径列表可在账号信息行末尾点击 `编辑`，在弹框中的 `资源路径` 中进行添加 。
+
+### 2.4.2 网关技术实现
+
+* 采用 `AK/SK` 鉴权技术方案。
+* 采用鉴权插件，责任链的模式来完成。
+* 当鉴权插件开启，并配置所有接口鉴权时候生效。
+
+### 2.4.3 鉴权使用指南
+
+* 第一步：AK/SK由网关来进行分配，比如分配给你的AK为: `1TEST123456781` SK为：`506EEB535CF740D7A755CB4B9F4A1536`
+
+* 第二步：确定好你要访问的网关路径 比如 `/api/service/abc`
+
+* 第三步：构造参数（以下是通用参数）
+
+| 字段 | 值 | 描述 |
+| -------- | -----: | :----: |
+| timestamp | 当前时间戳(String类型) | 当前时间的毫秒数（网关会过滤掉5分钟之前的请求） |
+| path | /api/service/abc | 就是你需要访问的接口路径(根据你访问网关接口自己变更) |
+| version | 1.0.0 | 当前鉴权算法为1.0.0 |
+
+对上述3个字段进行 `key` 的自然排序，然后进行字段与字段值拼接最后再拼接上 `SK` ，代码示例。
+
+#### 2.4.3.1 无请求体的签名参数验证
+
+第一步：首先构造一个 `Map` 。
+
+```java
+Map
+
+* 插件编辑里面新增配置模式。
+
+```yaml
+{"model":"black"}
+# model 可选值为 black, mixed
+# 默认为 black 黑名单模式，设置值为 mixed 则为混合模式，下面会专门进行讲解
+```
+
+## 在网关中引入 Waf 插件
+
+* 在网关的 `pom.xml` 文件中添加 `waf` 的依赖。
+
+```xml
+
+ 
+
+被 `Waf` 拒绝访问的请求，响应头状态码为：`403`。
+
+#### 黑名单模式
+
+- 当 `model` 设置为 `black` 黑名单模式的时候，只有匹配的流量才会执行拒绝策略，不匹配的，直接会跳过。
+- 此时规则配置中的 `处理` 配置失效，可配置为空。
+
+#### 混合模式
+
+* 当 `model` 设置为 `mixed` 混合模式的时候，所有的流量都会通过 `waf` 插件，针对不同的匹配流量，用户可以设置是拒绝，还是通过。
+
+* 此时规则配置中的 `处理` 配置必选：
+
+ * `permission`：匹配到该规则的处理逻辑。`reject`: 拒绝访问，`allow`: 允许访问。
+
+ * `statusCode`：被拒绝访问时，响应体中`code`字段的值， `不会修改响应头的状态码`。
+ 例如设置为：`statusCode=10001`，被拒绝的响应体如下：
+
+ ```json
+ {"code":10001,"message":"You are forbidden to visit"}
+ ```
+
+## 场景
+
+* `Waf`插件也是 `Apache ShenYu` 的前置插件，主要用来拦截非法请求，或者异常请求，并且给与相关的拒绝策略。
+* 当面对重放攻击时，你可以根据 `ip` 或者 `host` 来进行匹配，拦截掉非法的 `ip` 与 `host`，设置 `reject` 策略。
+* 关于如何确定 `ip` 与 `host` 值，请看 [parsing-ip-and-host](../../developer/custom-parsing-ip-and-host)
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/quick-start/_category_.json b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/quick-start/_category_.json
new file mode 100644
index 00000000000..a15cc14d2d4
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/quick-start/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "快速开始",
+ "position": 4
+}
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/quick-start/quick-start-dubbo.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/quick-start/quick-start-dubbo.md
new file mode 100644
index 00000000000..d00d87904d9
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/quick-start/quick-start-dubbo.md
@@ -0,0 +1,180 @@
+---
+title: Dubbo快速开始
+description: Dubbo快速开始
+---
+
+本文档演示如何将`Dubbo`服务接入到`Apache ShenYu`网关。您可以直接在工程下找到本文档的[示例代码](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-dubbo) 。
+
+## 环境准备
+
+请参考运维部署的内容，选择一种方式启动`shenyu-admin`。比如，通过 [本地部署](../deployment/deployment-local) 启动`Apache ShenYu`后台管理系统。
+
+启动成功后，需要在基础配置`->`插件管理中，把`dubbo` 插件设置为开启，并设置你的注册地址，请确保注册中心在你本地已经开启。
+
+
+
+
+启动网关，如果是通过源码的方式，直接运行`shenyu-bootstrap`中的`ShenyuBootstrapApplication`。
+
+> 注意，在启动前，请确保网关已经引入相关依赖。
+
+如果客户端是`apache dubbo`，注册中心使用`zookeeper`，请参考如下配置：
+
+```java
+
+ 
+
+启动网关，如果是通过源码的方式，直接运行`shenyu-bootstrap`中的`ShenyuBootstrapApplication`。
+
+> 注意，在启动前，请确保网关已经引入相关依赖。
+
+引入网关对`gRPC`的代理插件，在网关的 `pom.xml` 文件中增加如下依赖：
+
+```xml
+
+ 
+然后在 `Maven` 工具栏中选中 `protobuf:compile` 和 `protobuf:compile-custom`，然后右键 `Run Maven Build` 一键生成 `proto` 文件对应的 `java`代码。
+
+然后让`idea`识别生成的`target`文件夹
+
+
+运行 `org.apache.shenyu.examples.grpc.ShenyuTestGrpcApplication` 中的 `main` 方法启动项目。
+
+成功启动会有如下日志，表示将 `gRPC` 服务成功注册到 `shenyu-admin` 中。
+
+```shell
+2021-06-18 19:33:32.866 INFO 11004 --- [or_consumer_-19] o.a.s.r.client.http.utils.RegisterUtils : grpc client register success: {"appName":"127.0.0.1:8080","contextPath":"/grpc","path":"/grpc/clientStreamingFun","pathDesc":"clientStreamingFun","rpcType":"grpc","serviceName":"stream.StreamService","methodName":"clientStreamingFun","ruleName":"/grpc/clientStreamingFun","parameterTypes":"io.grpc.stub.StreamObserver","rpcExt":"{\"timeout\":5000,\"methodType\":\"CLIENT_STREAMING\"}","enabled":true,"host":"172.20.10.6","port":8080,"registerMetaData":false}
+2021-06-18 19:33:32.866 INFO 11004 --- [or_consumer_-17] o.a.s.r.client.http.utils.RegisterUtils : grpc client register success: {"appName":"127.0.0.1:8080","contextPath":"/grpc","path":"/grpc/echo","pathDesc":"echo","rpcType":"grpc","serviceName":"echo.EchoService","methodName":"echo","ruleName":"/grpc/echo","parameterTypes":"echo.EchoRequest,io.grpc.stub.StreamObserver","rpcExt":"{\"timeout\":5000,\"methodType\":\"UNARY\"}","enabled":true,"host":"172.20.10.6","port":8080,"registerMetaData":false}
+2021-06-18 19:33:32.866 INFO 11004 --- [or_consumer_-20] o.a.s.r.client.http.utils.RegisterUtils : grpc client register success: {"appName":"127.0.0.1:8080","contextPath":"/grpc","path":"/grpc/bidiStreamingFun","pathDesc":"bidiStreamingFun","rpcType":"grpc","serviceName":"stream.StreamService","methodName":"bidiStreamingFun","ruleName":"/grpc/bidiStreamingFun","parameterTypes":"io.grpc.stub.StreamObserver","rpcExt":"{\"timeout\":5000,\"methodType\":\"BIDI_STREAMING\"}","enabled":true,"host":"172.20.10.6","port":8080,"registerMetaData":false}
+2021-06-18 19:33:32.866 INFO 11004 --- [or_consumer_-21] o.a.s.r.client.http.utils.RegisterUtils : grpc client register success: {"appName":"127.0.0.1:8080","contextPath":"/grpc","path":"/grpc/unaryFun","pathDesc":"unaryFun","rpcType":"grpc","serviceName":"stream.StreamService","methodName":"unaryFun","ruleName":"/grpc/unaryFun","parameterTypes":"stream.RequestData,io.grpc.stub.StreamObserver","rpcExt":"{\"timeout\":5000,\"methodType\":\"UNARY\"}","enabled":true,"host":"172.20.10.6","port":8080,"registerMetaData":false}
+2021-06-18 19:33:32.866 INFO 11004 --- [or_consumer_-18] o.a.s.r.client.http.utils.RegisterUtils : grpc client register success: {"appName":"127.0.0.1:8080","contextPath":"/grpc","path":"/grpc/serverStreamingFun","pathDesc":"serverStreamingFun","rpcType":"grpc","serviceName":"stream.StreamService","methodName":"serverStreamingFun","ruleName":"/grpc/serverStreamingFun","parameterTypes":"stream.RequestData,io.grpc.stub.StreamObserver","rpcExt":"{\"timeout\":5000,\"methodType\":\"SERVER_STREAMING\"}","enabled":true,"host":"172.20.10.6","port":8080,"registerMetaData":false}
+```
+
+## 简单测试
+
+`shenyu-examples-grpc`项目成功启动之后会自动把加 `@ShenyuGrpcClient` 注解的接口方法注册到网关。
+
+打开 `插件列表 -> rpc proxy -> grpc` 可以看到插件规则配置列表。
+
+
+
+
+下面使用 `postman` 模拟 `http` 的方式来请求你的 `gRPC` 服务。
+请求参数如下：
+
+```json
+{
+ "data": [
+ {
+ "message": "hello grpc"
+ }
+ ]
+}
+```
+
+
+
+当前是以 `json` 的格式传递参数，`key`的名称默认是`data`，你可以在 `GrpcConstants.JSON_DESCRIPTOR_PROTO_FIELD_NAME` 中进行重置；`value`的传入则根据你定义的 `proto` 文件。
+
+## 流式调用
+
+`Apache ShenYu` 可以支持 `gRPC` 的流式调用，下面展示的是 `gRPC` 四种方法类型的调用。 在流式调用中，你可以通过数组的形式传递多个参数。
+
+- `UNARY`
+
+请求参数如下：
+
+```json
+{
+ "data": [
+ {
+ "text": "hello grpc"
+ }
+ ]
+}
+```
+
+通过`postman` 模拟 `http` 请求，发起`UNARY`调用。
+
+
+
+- `CLIENT_STREAMING`
+
+请求参数如下：
+
+```json
+{
+ "data": [
+ {
+ "text": "hello grpc"
+ },
+ {
+ "text": "hello grpc"
+ },
+ {
+ "text": "hello grpc"
+ }
+ ]
+}
+```
+
+通过`postman` 模拟 `http` 请求，发起`CLIENT_STREAMING`调用。
+
+
+
+- `SERVER_STREAMING`
+
+请求参数如下：
+
+```json
+{
+ "data": [
+ {
+ "text": "hello grpc"
+ }
+ ]
+}
+```
+
+通过`postman` 模拟 `http` 请求，发起`SERVER_STREAMING`调用。
+
+
+
+- `BIDI_STREAMING`
+
+请求参数如下：
+
+```json
+{
+ "data": [
+ {
+ "text": "hello grpc"
+ },
+ {
+ "text": "hello grpc"
+ },
+ {
+ "text": "hello grpc"
+ }
+ ]
+}
+```
+
+通过`postman` 模拟 `http` 请求，发起`BIDI_STREAMING`调用。
+
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/quick-start/quick-start-http.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/quick-start/quick-start-http.md
new file mode 100644
index 00000000000..a438fd8ef20
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/quick-start/quick-start-http.md
@@ -0,0 +1,81 @@
+---
+title: Http快速开始
+description: Http快速开始
+---
+
+本文档演示如何将`Http`服务接入到`Apache ShenYu`网关。您可以直接在工程下找到本文档的[示例代码](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http) 。
+
+## 环境准备
+
+请参考运维部署的内容，选择一种方式启动`shenyu-admin`。比如，通过 [本地部署](../deployment/deployment-local) 启动`Apache ShenYu`后台管理系统。
+
+启动成功后，需要在基础配置`->`插件管理中，把`divide` 插件设置为开启。在`Apache ShenYu`网关中，`Http`请求是由`divide`插件进行处理。
+
+
+
+
+
+启动网关，如果是通过源码的方式，直接运行`shenyu-bootstrap`中的`ShenyuBootstrapApplication`。
+
+> 注意，在启动前，请确保网关已经引入相关依赖。
+
+引入网关对`Http`的代理插件，在网关的 `pom.xml` 文件中增加如下依赖：
+
+```xml
+
+ 
+
+
+启动网关，如果是通过源码的方式，直接运行`shenyu-bootstrap`中的`ShenyuBootstrapApplication`。
+
+> 注意，在启动前，请确保网关已经引入相关依赖。
+> 本地已经成功启动zookeeper。
+
+引入网关对`Motan`的代理插件，在网关的 `pom.xml` 文件中增加如下依赖：
+
+```xml
+
+ 
+
+下面使用`postman`模拟`http`的方式来请求你的`motan`服务：
+
+
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/quick-start/quick-start-sofa.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/quick-start/quick-start-sofa.md
new file mode 100644
index 00000000000..1246db31304
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/quick-start/quick-start-sofa.md
@@ -0,0 +1,136 @@
+---
+title: Sofa快速开始
+description: Sofa快速开始
+---
+
+本文档演示如何将`Sofa`服务接入到`Apache ShenYu`网关。您可以直接在工程下找到本文档的[示例代码](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-sofa) 。
+
+## 环境准备
+
+请参考运维部署的内容，选择一种方式启动`shenyu-admin`。比如，通过 [本地部署](../deployment/deployment-local) 启动`Apache ShenYu`后台管理系统。
+
+启动成功后，需要在基础配置`->`插件管理中，把`sofa` 插件设置为开启，并设置你的注册地址，请确保注册中心在你本地已经开启。
+
+
+
+启动网关，如果是通过源码的方式，直接运行`shenyu-bootstrap`中的`ShenyuBootstrapApplication`。
+
+> 注意，在启动前，请确保网关已经引入相关依赖。
+
+如果客户端是`sofa`，注册中心使用`zookeeper`，请参考如下配置：
+
+```xml
+
+ 
+
+
+启动网关，如果是通过源码的方式，直接运行`shenyu-bootstrap`中的`ShenyuBootstrapApplication`。
+
+> 注意，在启动前，请确保网关已经引入相关依赖。
+
+引入网关对`Spring Cloud`的代理插件，并添加相关注册中心依赖：
+
+```xml
+
+ 
+
+启动网关，如果是通过源码的方式，直接运行`shenyu-bootstrap`中的`ShenyuBootstrapApplication`。
+
+> 注意，在启动前，请确保网关已经引入相关依赖。
+
+引入网关对`tars`的依赖：
+
+```xml
+
+
+2. 部署 `shenyu-bootstrap` 服务
+
+- 启动之后 `shenyu-bootstrap` 会根据 `shenyu.sync.websocket.url`配置的地址，通过 `websocket` 协议进行数据同步
+
+> 注意：在启动前，请确保网关已经引入相关依赖，默认已引入该依赖。
+
+引入网关对`Websocket`的代理插件，在网关的 `pom.xml` 文件中增加如下依赖：
+
+```xml
+
+ 
+
+2. 下面使用测试代码(见附件)模拟 `Websocket` 协议的请求方式来请求你的`Websocket`服务。
+
+
+
+## 附件
+
+**websocket调试代码**
+
+- 创建一个名为 websocket.html 的文件，复制下面的代码到文件中
+- 使用谷歌浏览器打开 websocket.html
+
+```html
+
+
+
+
+ 
+
+
+## 操作流程
+
+大体的流程如下：
+- 拥有管理用户权限的用户(包含 admin 用户) 新建用户。
+- 拥有管理用户数据权限的用户(包含 admin 用户)点击操作中的 `配置数据权限`。
+> 在此之前请确保插件列表中存在数据。如果没有则需要拥有管理插件权限的用户进行插件数据的增加。
+
+
+接下来我们看下具体操作：
+
+### 新建用户
+
+在点击菜单 "系统管理 -> 用户管理" 展示的页面中新增数据。如下图所示：
+
+
+### 编辑数据权限
+
+#### 增加插件数据
+
+在插件列表中增加数据，本文以 `divide` 为例
+
+
+#### 增加菜单权限
+
+给默认的角色赋予 divide 插件的权限。
+
+
+默认的角色没有任何的菜单权限，如果赋予了用户，该用户将无法登录。将数据权限所在的菜单赋予该角色。
+
+#### 配置用户的数据权限
+
+新增用户后，我们看到普通用户之后会有一个编辑数据权限的按钮，可以对用户进行数据权限的管理。
+
+
+这里的出现列表就是当时在插件中新增的数据。
+
+### 新用户登录
+
+新用户登录后只能看到已经赋予权限的数据。
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/admin-usage/dictionary-management.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/admin-usage/dictionary-management.md
new file mode 100644
index 00000000000..929bee687c5
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/admin-usage/dictionary-management.md
@@ -0,0 +1,30 @@
+---
+title: 字典管理
+keywords: ["字典"]
+description: 字典管理详解
+---
+
+本文档将介绍`Apache ShenYu`后台管理系统中字典管理的使用，字典管理主要用来维护和管理公用数据字典。
+
+请参考运维部署的内容，选择一种方式启动`shenyu-admin`。比如，通过 [本地部署](../../deployment/deployment-local) 启动`Apache ShenYu`后台管理系统。 启动成功后，可以直接访问 http://localhost:9095 ，默认用户名和密码分别为: `admin` 和 `123456`。
+
+
+目前使用场景是在 [插件处理管理](./plugin-handle-explanation) 时，选择数据类型是 `下拉框` 时使用：
+
+
+
+在字典管理中，你可以新增字典类型，供其他地方使用：
+
+
+
+* 字典类型：在插件处理管理时，使用的字段名称。
+* 字典编码：标识字典数据。
+* 字典名称：在添加插件、选择器或规则时`handle`字段的名称。
+* 字典值：字典数据实际取值。
+* 字典描述或备注：描述信息。
+* 排序：字典数据顺序。
+
+例如， `sentinel` 插件处理字段中的 `degradeRuleGrade`。当新增规则时，编辑 `degradeRuleGrade` 字段时，会自动从字典管理中查出 `type='degradeRuleGrade'` 的所有字典数据作为下拉选项：
+
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/admin-usage/plugin-handle-explanation.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/admin-usage/plugin-handle-explanation.md
new file mode 100644
index 00000000000..99c7808114f
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/admin-usage/plugin-handle-explanation.md
@@ -0,0 +1,51 @@
+---
+title: 插件配置
+keywords: ["插件"]
+description: 插件配置
+---
+
+本文档将介绍`Apache ShenYu`后台管理系统中插件的使用，包括插件管理和插件处理管理。
+
+
+请参考运维部署的内容，选择一种方式启动`shenyu-admin`。比如，通过 [本地部署](../../deployment/deployment-local) 启动`Apache ShenYu`后台管理系统。 启动成功后，可以直接访问 http://localhost:9095 ，默认用户名和密码分别为: `admin` 和 `123456`。
+
+## 插件管理
+
+在插件管理中，你可以对所有插件进行统一管理，比如关闭或开启插件：
+
+
+
+也可以对某些插件设置配置信息，比如给`Dubbo`插件设置注册中心：
+
+
+
+## 插件处理管理
+
+在插件处理管理中，你可以对插件、选择器和规则添加`handle`字段。
+
+比如给`springCloud`插件的规则列表新增一个字符串类型的字段`path`和一个数字类型的字段`timeout`。
+
+
+第一步，在 `插件处理管理` 界面新增/编辑`handle`字段：
+
+
+
+第二步，填写字段信息：
+
+
+
+* 插件名：需要给哪个插件添加`handle`字段，下拉选择。
+* 字段：添加字段的名称。
+* 描述：字段描述信息。
+* 数据类型：数字、字符串、下拉框。如果选择了`下拉框`，则规则新增页面里输入框下拉选择是通过字段名称去字典表中查出所有可选项进行下来选择，所以需要提前在 [字典管理](./dictionary-management) 中录入信息。
+* 字段所属类型：插件、选择器、规则。
+* 排序：字段顺序。
+* 是否必填：是、否。
+* 默认值：为该字段指定一个默认值。
+* 输入提示：用户填写该字段时，出现的提示信息。
+* 校验规则(正则) ：用户填写该字段时，使用校验规则。
+
+第三步，在`插件列表 -> rpc proxy -> springCloud -> 添加规则`时，就可以输入`path`、`timeout`的信息：
+
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/admin-usage/role-management.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/admin-usage/role-management.md
new file mode 100644
index 00000000000..6c1cb5094ed
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/admin-usage/role-management.md
@@ -0,0 +1,47 @@
+---
+title: 用户资源管理
+keywords: ["用户 角色"]
+description: 用户角色管理
+---
+
+本篇主要是讲述 `admin` 控制台通过用户关联的角色，角色赋予菜单和按钮等资源的权限来管理 `admin` 的操作权限。
+
+
+## 资源管理
+
+在菜单栏中 ”系统管理 >> 资源管理“ 中增加菜单和按钮。
+
+
+
+admin 用户显示了 shenyu 网关所有的菜单和按钮。如果需要自定义增加和删除，先增加菜单，在相应的菜单下，增加按钮。通过点击菜单中右侧的编辑小图标进行菜单的编辑
+
+
+## 角色管理
+
+通过菜单栏 ”系统管理 >> 角色管理“ 来关联角色和资源的权限。 默认会生成两个角色，一个超级管理员，一个普通用户。超级管理员为 admin 用户，不可更改，普通用户的角色可以更改其资源属性。 通过编辑相应的角色，赋予角色相应的菜单和按钮权限。
+
+
+
+
+## 用户管理
+
+通过菜单栏 ”系统管理 >> 用户管理“ 来管理登录到 admin 的用户。默认为 admin 用户，它拥有所有菜单权限和数据权限，不可更改， 不可删除， 只能修改用户名和密码。
+可以通过按钮 ”新增数据“ 来增加用户。通过选择用户角色来管理该用户登录后所看到的菜单和按钮权限。当用户选择了多个角色时，取所有的角色的最大并集。更改用户的角色权限后，已经登录的用户只要刷新页面便能获得更改后的权限。
+
+下面以新建用户为例，展示了新用户登录后的权限展示。
+
+- 更改默认角色的权限
+
+
+
+- 新增角色并赋予相应的资源权限
+
+
+
+- 新建用户，并赋予相应的角色
+
+
+
+- 用户登录后查看自身的菜单和按钮权限
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/admin-usage/selector-and-rule.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/admin-usage/selector-and-rule.md
new file mode 100644
index 00000000000..f3f79b26acd
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/admin-usage/selector-and-rule.md
@@ -0,0 +1,322 @@
+---
+title: 选择器和规则管理
+keywords: ["选择器", "规则"]
+description: 选择器和规则管理
+---
+
+本文档将介绍`Apache ShenYu`后台管理系统中选择器和规则的使用，关于选择器和规则的概念及设计请参考 [流量控制](../../design/flow-control)。
+
+请参考运维部署的内容，选择一种方式启动`shenyu-admin`。比如，通过 [本地部署](../../deployment/deployment-local) 启动`Apache ShenYu`后台管理系统。 启动成功后，可以直接访问 `http://localhost:9095` ，默认用户名和密码分别为: `admin` 和 `123456`。
+
+## 选择器
+
+在插件列表中展示了当前的所有插件，可以给每个插件添加选择器和规则：
+
+
+
+
+例如，给`divide`插件添加选择器：
+
+
+
+* 选择器详解：
+
+ * 名称：给选择器取一个名字。
+ * 类型：自定义流量(`custom flow`) 或 全流量(`full flow`)。自定义流量就是请求会走下面的匹配方式与条件。全流量则不走。
+ * 匹配方式：`and`或者 `or` 是指下面多个条件是按照 并(`and`) 还是 或(`or`) 的方式来组合。
+ * 条件：
+ * `uri`：根据 `uri` 的方式来筛选流量，`match` 的方式支持模糊匹配（`/**`）
+ * `header`：根据请求头里面的字段来筛选流量。
+ * `query`：根据 `uri` 的查询条件来进行筛选流量。
+ * `ip`：根据请求的真实 `ip` 来筛选流量。
+ * `host`：根据请求的真实 `host` 来筛选流量。
+ * `post`：根据请求上下文获取参数，不建议使用。
+ * `cookie`：根据请求的 `cookie` 来筛选流量。
+ * `req_method`：根据请求的方式来筛选流量。
+ * 条件匹配：
+ * `match`：模糊匹配，建议和`uri`条件搭配，支持 `restful` 风格的匹配。（`/test/**`）
+ * `=`：前后值相等，才能匹配。
+ * `regEx`：正则匹配，表示前面一个值去匹配后面的正则表达式。
+ * `contains`：请求包含指定的值，才能匹配。
+ * `TimeBefore`：指定时间之前。
+ * `TimeAfter`：指定时间之后。
+ * `exclude`： 是 `match` 方式的反选。
+ * `startsWith`：请求前缀等于指定的值，才能匹配。在特定场景下，可替换 `match` （如用`/test/`来替换`/test/**`）以获得更好的性能。
+ * `endsWith`：请求后缀等于指定的值，才能匹配。
+ * `pathPattern`：是 `match` 的优化版，性能比`match`更好，但是不支持将`**`写在path中间（如`/api/**/xxx`）。
+ * 继续后续选择器：后续选择器还是否执行。
+ * 是否开启：打开才会生效。
+ * 打印日志：打开时，当匹配上的时候，会打印匹配日志。
+ * 执行顺序：当多个选择器的时候，执行顺序小的优先执行，值越小优先级越高。
+ * 处理：即`handle`字段，在 [插件处理管理](./plugin-handle-explanation) 中进行设置。作用是：当请求流量匹配上该选择器时，做什么样的处理操作。
+* 上述图片中表示: 当请求的 `uri` 前缀是 `/http`，会转发到 `127.0.0.1:8080` 这个服务上。
+* 选择器建议：可以通过设置 `uri` 条件， `startsWith` 前缀（`/contextPath/`）匹配，进行第一道流量筛选。
+* 选择器(同规则)模糊匹配条件规则：
+ * `?` 匹配1个字符
+ * `*` 匹配0个或多个字符
+ * `**` 匹配0个或多个目录
+
+## 规则
+
+
+
+* 当流量经过选择器匹配成功之后，会进入规则来进行最终的流量匹配。
+
+* 规则是对流量最终执行逻辑的确认。
+
+* 规则详解：
+ * 名称：给规则取一个名字。
+ * 匹配方式：`and` 或者 `or` 是指下面多个条件的组合方式。
+ * 条件：
+ * `uri`：根据 `uri` 的方式来筛选流量，`match` 的方式支持模糊匹配（`/**`）
+ * `header`：根据请求头里面的字段来筛选流量。
+ * `query`：根据 `uri` 的查询条件来进行筛选流量。
+ * `ip`：根据请求的真实 `ip` 来筛选流量。
+ * `host`：根据请求的真实 `host` 来筛选流量。
+ * `post`：不建议使用。
+ * `cookie`：根据请求的 `cookie` 来筛选流量。
+ * `req_method`：根据请求的 `req_method` 来筛选流量。
+ * 条件匹配：
+ * `match`：模糊匹配，建议和`uri`条件搭配，支持 `restful` 风格的匹配。（`/test/**`）
+ * `=`：前后值相等，才能匹配。
+ * `regEx`：正则匹配，表示前面一个值去匹配后面的正则表达式。
+ * `contains`：请求包含指定的值，才能匹配。
+ * `TimeBefore`：指定时间之前。
+ * `TimeAfter`：指定时间之后。
+ * `exclude`： 是 `match` 方式的反选。
+ * `startsWith`：请求前缀等于指定的值，才能匹配。在特定场景下，可替换 `match` （如用`/test/`来替换`/test/**`）以获得更好的性能。
+ * `endsWith`：请求后缀等于指定的值，才能匹配。
+ * `pathPattern`：是 `match` 的优化版，性能比`match`更好，但是不支持将`**`写在path中间（如`/api/**/xxx`）。
+ * 是否开启：打开才会生效。
+ * 打印日志：打开时，当匹配上的时候，才会打印匹配日志。
+ * 执行顺序：当多个规则的时候，执行顺序小的优先执行。
+ * 处理：即`handle`字段，在 [插件处理管理](./plugin-handle-explanation) 中进行设置。每个插件的规则处理不一样，具体请查看每个对应插件的处理。
+
+* 上图表示：当 `uri` 等于 `/http/order/save` 的时候能够匹配上该规则，就会执行该规则中，负载策略是 `random`，重试次数是 `3` 等处理操作。
+
+* 规则建议：可以`uri` 条件， `match` 最真实的`uri路径`，进行流量的最终筛选 。
+
+联合选择器，我们来表述一下：当一个请求的 `uri` 为 `/http/order/save`，会通过 `random` 的方式，转发到 `127.0.0.1:8080` 机器上。
+
+## 匹配方式
+
+匹配方式是指在选择器或规则匹配时，多个条件之间的匹配方式，当前支持 `and` 和 `or`。
+
+* `and`
+
+ `and`表示多个条件同时满足才能匹配上选择器或规则。
+
+ 下图中的示例表示，请求必须同时满足条件 `uri = /http/order/findById` 和 条件 `id = 100` 才能匹配上该条规则。
+
+ 比如一个真实的请求 `http://localhost:9195/http/order/findById?id=100` 能够同时满足上述两个条件，所以可以匹配上该条规则。
+
+
+
+
+* `or`
+
+ `or`表示多个条件中满足一个就能匹配上选择器或规则。
+
+ 下图中的示例表示，请求满足条件 `uri = /http/order/findById` 或者 条件 `id = 100` 就能匹配上该条规则。
+
+ 比如一个真实的请求 `http://localhost:9195/http/order/findById?id=99` 能够满足上述第一个条件 `uri = /http/order/findById`，所以也可以匹配上该条规则。
+
+
+
+## 条件参数
+
+对选择器和规则中的条件参数设置再次进行解释。假如下面是一个 `HTTP` 请求的请求头：
+
+```shell
+GET http://localhost:9195/http/order/findById?id=100
+Accept: application/json
+Cookie: shenyu=shenyu_cookie
+MyHeader: custom-header
+```
+
+在`ShenYu`中可以通过设置不同的条件参数从请求信息中获取真实数据。
+
+- 如果条件参数是`uri`，那么获取到的真实数据是 `/http/order/findById`；
+- 如果条件参数是`header`，字段名称是`MyHeader`，那么获取到的真实数据是 `custom-header`；
+- 如果条件参数是`query`，字段名称是`id`，那么获取到的真实数据是 `100`；
+- 如果条件参数是`ip`，那么获取到的真实数据 `0:0:0:0:0:0:0:1`；
+- 如果条件参数是`host`，那么获取到的真实数据是 `0:0:0:0:0:0:0:1`；
+- 如果条件参数是`post`，字段名称是`contextPath`，那么获取到的真实数据是 `/http`；
+- 如果条件参数是`cookie`，字段名称是`shenyu`，那么获取到的真实数据是 `shenyu_cookie`；
+- 如果条件参数是`req_method`，那么获取到的真实数据是 `GET`。
+
+
+* `uri` （推荐）
+
+ * `uri` 匹配是根据你请求路径中的 `uri` 来进行匹配，在接入网关的时候，前端几乎不用做任何更改。
+
+ * 当使用 `match` 方式匹配时候，同 `springmvc` 模糊匹配原理相同。
+
+ * 在选择器中，推荐使用 `uri` 中的前缀来进行匹配，而在规则中，则使用具体路径来进行匹配。
+
+ * 使用该匹配方式的时候，填写匹配字段的值，图中的示例是`/http/**`。
+
+ 
+
+* `header`
+
+ * `header` 是根据你的 `http` 请求头中的字段值来匹配。
+
+ * 使用该匹配方式的时候，需要填写字段名称和字段值，图中的示例分别是`MyHeader`和`custom-header`。
+
+ 
+
+* `query`
+
+ * 这个是根据你的 `uri` 中的查询参数来进行匹配，比如 `/test?id=1`，那么可以选择该匹配方式。
+
+ * 使用该匹配方式的时候，需要填写字段名称和字段值，图中的示例分别是`id`和`1`。
+
+ 
+
+* `ip`
+
+ * 这个是根据 `http` 调用方的 `ip` 来进行匹配。
+
+ * 尤其是在 `waf` 插件里面，如果发现一个 `ip`地址有攻击，可以新增一条匹配条件，填上该 `ip`，拒绝该 `ip` 的访问。
+
+ * 如果在 `Apache ShenYu` 前面使用了 `nginx` 代理，为了获取正确的 `ip`，可以参考 [自定义解析IP与Host](../../developer/custom-parsing-ip-and-host) 。
+
+ * 使用该匹配方式的时候，填写匹配字段的值，图中的示例是`192.168.236.75`。
+
+ 
+
+
+* `host`
+
+ * 这个是根据 `http` 调用方的 `host` 来进行匹配。
+
+ * 尤其是在 `waf` 插件里面，如果发现一个 `host` 地址有攻击，可以新增一条匹配条件，填上该 `host`，拒绝该 `host` 的访问。
+
+ * 如果在 `Apache ShenYu` 前面使用了 `nginx` 代理，为了获取正确的 `host`，可以参考 [自定义解析IP与Host](../../developer/custom-parsing-ip-and-host) 。
+
+ * 使用该匹配方式的时候，填写匹配字段的值，图中的示例是`localhost`。
+
+ 
+
+* `post`
+
+ * 从请求上下文（`org.apache.shenyu.plugin.api.context.ShenyuContext`）中获取条件参数，需要通过反射获取字段的值，不推荐使用此方式。
+
+ * 使用该匹配方式的时候，需要填写字段名称和字段值，图中的示例分别是`contextPath`和`/http`。
+
+ 
+
+
+* `cookie`
+
+ * 这个是根据 `http` 调用方的请求头中`Cookie`作为条件参数进行匹配。
+
+ * 使用该匹配方式的时候，需要填写字段名称和字段值，图中的示例分别是`shenyu`和`shenyu_cookie`。
+
+ 
+
+* `req_method`
+
+ * 这个是根据 `http` 调用方的请求形式来进行匹配，比如`GET`、`POST`等。
+
+ * 使用该匹配方式的时候，填写匹配字段的值，图中的示例是`GET`。
+
+ 
+
+如果想更深入理解条件参数的获取，请阅读相关源码，包名是`org.apache.shenyu.plugin.base.condition.data`：
+
+|条件参数 | 源码类 |
+|:------------------------ |:----- |
+|`uri` |`URIParameterData` |
+|`header` |`HeaderParameterData` |
+|`query` |`QueryParameterData` |
+|`ip` |`IpParameterData` |
+|`host` |`HostParameterData` |
+|`post` |`PostParameterData` |
+|`cookie` |`CookieParameterData` |
+|`req_method` |`RequestMethodParameterData` |
+
+
+## 条件匹配策略
+
+通过条件参数能够获取到请求的真实数据。真实数据如何匹配上选择器或规则预设的条件数据，是通过条件匹配策略来实现。
+
+* `match`
+
+ `match` 的方式支持模糊匹配（`/**`）。假如你的选择器条件设置如下，那么请求 `/http/order/findById` 就可以匹配上。
+
+ 
+
+* `=`
+
+ `=` 的方式表示请求的真实数据和预设的条件数据相等。假如你的选择器条件设置如下：请求`uri`等于`/http/order/findById`，那么请求 `/http/order/findById?id=1` 就可以匹配上。
+
+ 
+
+* `regex`
+
+ `regex` 的方式表示请求的真实数据能够满足预设条件的正则表达式才能匹配成功。假如你的规则条件设置如下：请求参数中包含`id`，并且是3位数字。那么请求 `/http/order/findById?id=900` 就可以匹配上。
+
+ 
+
+* `contains`
+
+ `contains` 的方式表示请求的真实数据包含预设的条件数据。假如你的规则条件设置如下：请求`uri`中包含`findById`。那么请求 `/http/order/findById?id=1` 就可以匹配上。
+
+ 
+
+* `TimeBefore`
+
+ `TimeBefore` 的方式表示请求时间在预设的条件时间之前才能匹配成功。假如你的规则条件设置如下：请求参数中包含`date`，并且`date`小于`2021-09-26 06:12:10`。那么请求 `/http/order/findById?id=100&date=2021-09-22 06:12:10` 就可以匹配上。
+
+ 
+
+* `TimeAfter`
+
+ `TimeAfter` 的方式表示请求时间在预设的条件时间之后才能匹配成功。假如你的规则条件设置如下：请求参数中包含`date`，并且`date`大于`2021-09-26 06:12:10`。那么请求 `/http/order/findById?id=100&date=2021-09-29 06:12:10` 就可以匹配上。
+
+ 
+
+* `exclude`
+
+ `exclude` 的方式是 `match` 方式的反选，`match` 有的功能也都有，但是是匹配过滤。假如你的选择器条件设置如下，那么请求 `/http/order/findById` 就会过滤这个。
+
+ 
+
+* `startsWith`
+
+ `startsWith` 的方式表示请求的真实数据的前缀和预设的条件数据相等。假如你的规则条件设置如下：请求`uri`中前缀等于`/http/`。那么请求 `/http/order/findById?id=1` 就可以匹配上。
+
+ 
+
+* `endsWith`
+
+ `endsWith` 的方式表示请求的真实数据的后缀和预设的条件数据相等。假如你的规则条件设置如下：请求`uri`中后缀等于`Id`。那么请求 `/http/order/findById?id=1` 就可以匹配上。
+
+ 
+
+* `pathPattern`
+
+ 跟 `match` 类似， `pathPattern` 支持模糊匹配（`/**`）。假如你的规则条件设置如下，那么请求 `/http/order/findById` 就可以匹配上；
+
+ 但是注意：不支持将`**`写在path中间（如`/api/**/xxx`）!
+
+ 
+
+如果想更深入理解条件匹配策略，请阅读相关源码，包名是`org.apache.shenyu.plugin.base.condition.judge`：
+
+|匹配策略 | 源码类 |
+|:------------------------ |:----- |
+|`match` |`MatchPredicateJudge` |
+|`=` |`EqualsPredicateJudge` |
+|`regex` |`RegexPredicateJudge` |
+|`contains` |`ContainsPredicateJudge` |
+|`TimeBefore` |`TimerBeforePredicateJudge` |
+|`TimeAfter` |`TimerAfterPredicateJudge` |
+|`exclude` |`ExcludePredicateJudge` |
+|`startsWith` |`StartsWithPredicateJudge` |
+|`endsWith` |`EndsWithPredicateJudge` |
+|`pathPattern` |`PathPatternPredicateJudge` |
+
+文中的示例是为了说明选择器和规则的使用，具体条件的设置需要根据实际情况选择。
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/api-doc/_category_.json b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/api-doc/_category_.json
new file mode 100644
index 00000000000..8934b1125d0
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/api-doc/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "API文档聚合",
+ "position": 6
+}
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/api-doc/shenyu-annotation-apidoc.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/api-doc/shenyu-annotation-apidoc.md
new file mode 100644
index 00000000000..0a41e4475f8
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/api-doc/shenyu-annotation-apidoc.md
@@ -0,0 +1,38 @@
+---
+title: Shenyu客户端注册API文档
+keywords: ["api doc 接口 文档 register 注册"]
+description: Shenyu客户端注册API文档
+---
+
+此篇文介绍如何将 `API文档` 暴露到 `Apache ShenYu` 网关。
+
+接入前，请正确启动 `shenyu-admin`。
+
+## API文档暴露到网关
+
+可以参考[shenyu-examples](https://github.com/apache/shenyu/tree/master/shenyu-examples)下面任意一个example的代码。
+
+唯一需要做的就是在你的服务中的新增`@ApiModule`和`@ApiDoc`注解，以下是`shenyu-examples-http`中的例子:
+
+```java
+@RestController
+@RequestMapping("/order")
+@ShenyuSpringMvcClient("/order")
+@ApiModule(value = "order")
+public class OrderController {
+
+ @GetMapping("/findById")
+ @ShenyuSpringMvcClient("/findById")
+ @ApiDoc(desc = "findById")
+ public OrderDTO findById(@RequestParam("id") final String id) {
+ return build(id, "hello world findById");
+ }
+
+ private OrderDTO build(final String id, final String name) {
+ OrderDTO orderDTO = new OrderDTO();
+ orderDTO.setId(id);
+ orderDTO.setName(name);
+ return orderDTO;
+ }
+}
+```
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/api-doc/swagger-apidoc.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/api-doc/swagger-apidoc.md
new file mode 100644
index 00000000000..f9ca7b5a6f1
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/api-doc/swagger-apidoc.md
@@ -0,0 +1,57 @@
+---
+title: 拉取swagger注册API文档
+keywords: ["swagger api 接口 文档聚合"]
+description: 远程拉取swagger 注册 API文档
+---
+
+此篇文介绍如何将各个后端微服务的 `Swagger API文档` 聚合到 `Apache ShenYu` 网关管理系统。
+
+## 1. 说明
+
+远程拉取swagger文档，目前仅支持swaggger2.0，并且只支持 Divide 和 SpringCloud 两种代理插件。
+
+## 2. 环境准备
+
+### 2.1 启动`shenyu-admin`
+
+参考 `运维部署` , 选择一种方式启动`shenyu-admin`。
+
+### 2.2 开启远程拉取swagger文档的全局开关
+
+默认已开启。在`Apache ShenYu`网关管理系统 --> 基础配置 --> 字典管理， 找到字典编码为 `apidoc`的数据，修改 字典值: `true`。
+> 【注意】字典值：`true`表示开关已开启，`false`表示已关闭。若关闭后，`shenyu-admin`不会自动拉取各个微服务的swaggger文档。
+
+
+
+## 3. 运行示例项目
+
+3.1. 下载 [shenyu-examples-http-swagger2](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http-swagger2)
+
+3.2. 运行`org.apache.shenyu.examples.http.ShenyuTestSwaggerApplication` main方法启动项目。
+
+examples项目会根据 `shenyu.register.serverLists` 配置的地址，通过 Shenyu client 注解(比如`@ShenyuSpringMvcClient`) 将服务启动信息同步给 `shenyu-admin`, 然后触发 `shenyu-admin` 远程拉取swagger文档并完成解析，最后聚合产出新的API文档。
+
+## 4. 演示效果
+
+### 4.1 API文档列表
+
+在`Apache ShenYu`网关管理系统 --> 文档说明 --> API文档，你可以看到已经聚合好的API文档。
+
+
+
+### 4.2 API详情效果
+
+
+
+## 5. 如何自动更新API文档
+
+### 5.1 重启项目
+
+如上面示例那样，通过启动项目触发自动更新API文档。
+
+### 5.2 修改proxy插件选择器的启动时间
+
+在 proxy插件--> 选择器，找到目标服务，然后修改启动时间。
+> 注意：新设置的启动时间一定不能早于原启动时间，否则不会触发自动拉取并刷新API文档。
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/discovery/_category_.json b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/discovery/_category_.json
new file mode 100644
index 00000000000..66f64292a8b
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/discovery/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "服务发现",
+ "position": 4
+}
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/discovery/discovery-mode.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/discovery/discovery-mode.md
new file mode 100644
index 00000000000..38724ae89a6
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/discovery/discovery-mode.md
@@ -0,0 +1,392 @@
+---
+title: 服务发现模块
+keywords: [ "Discovery" ]
+description: 服务发现模块模块
+---
+
+# 服务发现模块
+
+## 1. 概述
+
+### 1.1 模块名称
+
+Discovery
+
+### 1.2 设计
+
+- 模块设计图
+
+
+
+
+- 数据库设计
+
+
+
+
+### 1.3 模块功能
+
+Discovery 模块赋予了 ShenYu 网关一种主动感知和响应被代理服务列表变化的能力。
+通过 Discovery 网关 admin 服务的主动监听，ShenYu 网关能够及时掌握被代理服务的变动情况。
+这一功能的设计具有灵活性，可以根据需要在**选择器级别**或**插件级别**进行配置。
+目前，已经引入了 Discovery 功能的插件包括 TCP 插件、Divide 插件、Websocket 插件和 gRPC 插件。
+
+
+### 1.4 监听模式
+
+LOCAL, ZOOKEEPER, NACOS, EUREKA, ETCD
+
+- LOCAL 模式: 主要依靠手动维护 upstream 列表，并推送到网关；
+- ZOOKEEPER 模式: 监听 ZooKeeper 中指定节点下临时节点的变化来获取数据；
+- NACOS 模式：监听 Nacos 中指定服务名称下实例的变化来获取数据；
+- EUREKA 模式： 监听 Eureka 中指定服务名称下实例的变化来获取数据；
+- ETCD 模式：通过监听 etcd 中指定节点键值对的变化来获取数据。
+
+
+### 1.5 作用范围
+
+- 插件级别：影响整个插件，所有该插件下的选择器都将默认采用当前的监听模式；
+- 选择器级别：适用于当前选择器，对于当前插件下的不同选择器，可以使用不同的监听模式。
+
+## 2. 使用
+
+### 2.1 插件级别配置
+
+#### 2.1.1 服务发现配置
+
+- 在支持 Discovery 模块的插件中（当前只有 TCP 插件支持在admin控制台页面，进行插件级别 discovery 配置，其他插件可以通过 shenyu-client 进行插件级别 discovery 配置，见下文中的“配合Shenyu-client使用”）， 点击 `服务发现配置`， 在弹出的表单中，选择需要的监听模式，
+ 并填写服务发现名称、注册服务器URL、注册中心配置参数等：
+
+
+
+
+
+
+#### 2.1.2 在选择器中使用
+
+- 点击 `添加选择器`，在新增选择器页面中，我们发现 `类型` 强制选择刚才配置的插件级监听模式，表示所添加的选择器也将采用相同的配置。
+ 此时，仅需输入需要监听的 `监听节点` ：
+
+ 
+
+- 这里的 `转换处理` 是指，ShenYu 规定的 upstream 注册数据是以下 JSON 格式传输，包括：
+ - url: upstream 的 url
+ - protocol: upstream 的通信协议
+ - status: upstream 节点的状态 (0: healthy, 1: unhealthy)
+ - weight: 权重，计算负载均衡时使用
+
+
+ ```json
+ {
+ "url": "127.0.0.1::6379",
+ "protocol": "tcp",
+ "status": 0,
+ "weight": 10
+ }
+ ```
+
+- 如果您的服务别名与ShenYu定义的JSON格式不匹配，您可以在 `转换处理` 中进行别名映射。
+ 例如，如上图所示，如果您需要将"status"改为"healthy"，而保留其他键不变，
+ 进行如下操作：起一个新的别名，将"status"映射为"healthy"，
+ 同时保留原有JSON键的形式。
+- 进行选择器剩余的属性的配置，详情见具体插件对应的文档。
+
+### 2.2 选择器级别配置
+
+- 在支持 Discovery 模块的插件中，点击 `添加选择器`，在 `服务发现` 标签页中，
+ 配置类型、监听节点、服务器URL列表、注册中心参数等字段内容，配置内容仅对当前选择器有效，每次新增选择器需要重新配置。
+
+
+
+- 对于Divide、gRPC、Websocket插件，添加选择器页面有 `导入后台服务发现配置` 功能，
+ 指的是，如果服务接入 ShenYu 网关时配置了 shenyu-discovery 相关的属性（见配合shenyu-client使用），可以选择导入并沿用后台的配置，如下图我们首先点击 `导入后台服务发现配置` 查看后台配置:
+
+
+
+- 如果确认导入，点击后台配置弹出框中的 `导入` 按钮后，后台的服务发现属性将会自动填充进表单，
+ 此时仅需要再配置监听节点：
+
+
+
+> **注意**：如果确认导入后台配置，后台的服务发现属性将会自动填充进表单，并沿用之前的discovery对象，
+此时，在表单中修改服务发现属性将无效，依然保持后台配置。
+
+- 若选择了 LOCAL 模式，则无需接入注册中心，用户需要手动维护 upstream 列表。
+
+
+## 3. 不同模式下的配置
+
+### 3.1 local模式
+
+- local模式只支持**选择器级别**的配置。无需接入注册中心，用户需要手动维护 upstream 列表。这里的列表是一个可编辑表格，
+ 点击表格每行的 `编辑` 按钮，可以对 upstream 的每个参数进行修改：
+
+
+
+### 3.2 ZooKeeper/Nacos/Eureka/Etcd模式
+
+- ZooKeeper/Nacos/Eureka/Etcd模式下，支持插件级别和选择器级别的服务发现配置。
+- 针对每个模式下的注册中心属性，以zookeeper为例，用户可以在`shenyu-admin` --> 基础配置 --> 字典管理 中，搜索字典名称为“zookeeper”，对默认属性对应的字典值进行修改编辑
+ （**注意**：不可修改字典类型和字典名称）。
+- 这些模式下，网关会动态地从注册中心获取服务实例信息，服务实例的新增、下线、修改等，将会实时显示在 upstream 列表中。
+
+
+
+
+## 4. 配合 Shenyu-client 使用
+
+### 4.1 介绍
+
+- 与 shenyu-client 配合使用需要依赖对应模式的注册中心中间件：zookeeper，nacos，etcd，eureka，这些模式可以通过Shenyu Admin实现自动感知服务的上线和下线。
+- 另外，如果您使用了 local 模式，则需要手动维护upstream列表。
+- shenyu-client 使用详见 shenyu-client 模块。
+
+### 4.2 Local 模式示例
+
+#### 4.2.1 使用shenyu-client
+
+- shenyu-client 默认为 Local模式，无需进行特殊的 discovery 配置，便可以自动把当前服务注册上去；
+- 对于自动注册上来的服务，可以手动在页面的upstream列表进行添加、修改和删除：
+
+
+
+#### 4.2.2 不使用shenyu-client
+
+
+- 如果不使用shenyu-client，也可以手动在 `添加选择器` 的 `服务发现` 标签页上添加、修改、删除服务信息：
+
+
+
+- 配置选择器其他信息：
+
+
+
+- 配置规则：
+
+
+
+- 测试连接
+
+```text
+curl http://localhost:9195/http/hello
+
+hello! I'm Shenyu-Gateway System. Welcome!%
+```
+
+### 4.2 Zookeeper模式示例
+
+（以 Divide 插件为例）
+- 添加依赖
+
+```xml
+
+
+
+### 属性配置
+
+```yaml
+shenyu:
+ register:
+ registerType: http #http #zookeeper #etcd #nacos #consul
+ serverLists: #localhost:2181 #http://localhost:2379 #localhost:8848
+ props:
+ sessionTimeout: 5000
+ connectionTimeout: 2000
+ checked: true
+ zombieCheckTimes: 5
+ scheduledTime: 10
+ nacosNameSpace: ShenyuRegisterCenter
+ sync:
+ websocket:
+ enabled: true
+ messageMaxSize: 10240
+ allowOrigins: ws://localhost:9095;ws://localhost:9195;
+# zookeeper:
+# url: localhost:2181
+# sessionTimeout: 5000
+# connectionTimeout: 2000
+# http:
+# enabled: true
+# nacos:
+# url: localhost:8848
+# namespace: 1c10d748-af86-43b9-8265-75f487d20c6c
+# username:
+# password:
+# acm:
+# enabled: false
+# endpoint: acm.aliyun.com
+# namespace:
+# accessKey:
+# secretKey:
+# etcd:
+# url: http://localhost:2379
+# consul:
+# url: http://localhost:8500
+ aes:
+ secret:
+ key: 2095132720951327
+ iv: 6075877187097700
+ ldap:
+ enabled: false
+ url: ldap://xxxx:xxx
+ bind-dn: cn=xxx,dc=xxx,dc=xxx
+ password: xxxx
+ base-dn: ou=xxx,dc=xxx,dc=xxx
+ object-class: person
+ login-field: cn
+ jwt:
+ expired-seconds: 86400000
+ shiro:
+ white-list:
+ - /
+ - /favicon.*
+ - /static/**
+ - /index**
+ - /plugin
+ - /platform/**
+ - /websocket
+ - /configs/**
+ - /shenyu-client/**
+ - /error
+ - /actuator/health
+ - /swagger-ui.html
+ - /webjars/**
+ - /swagger-resources/**
+ - /v2/api-docs
+ - /csrf
+ swagger:
+ enable: true
+```
+
+
+### 属性详解
+
+##### shenyu.register 配置
+
+这是客户端接入的相关配置，客户端接入原理请参考：[客户端接入原理](../../design/register-center-design) ，客户端接入配置请参考： [客户端接入配置](register-center-access.md) 。
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|registerType |String | http | 必填 |使用哪种方式进行服务注册，当前支持 `http`、`zookeeper`、`etcd`、`consul`和`nacos` 。|
+|serverLists |String | 无 | 非必填 |配置中心的地址。使用`http`方式时，不需要填写，其他类型需要填写。集群时，多个地址用 `,` 分开 。|
+|props | | | | 使用不同注册类型时，属性取值不同。|
+
+
+
+
+- `props`配置
+
+使用不同的注册类型时，属性取值不同。
+
+当注册类型为`http`时，支持的属性配置如下：
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|checked |boolean | false | 否 |是否开启检测|
+|zombieCheckTimes |int | 5 | 否 |失败几次后剔除服务|
+|scheduledTime |int | 10 | 否 | 定时检测间隔时间 （秒）|
+
+当注册类型为`zookeeper`时，支持的属性配置如下：
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|sessionTimeout | int | 30000 | 否 |session超时时间（毫秒）|
+|connectionTimeout | int | 3000 | 否 |连接超时时间（毫秒）|
+
+当注册类型为`etcd`时，暂时没有属性配置。
+
+当注册类型为`nacos`时，支持的属性配置如下：
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|nacosNameSpace | String | 无 | 是 |命名空间|
+|username | String | 空字符串 | 否 |用户名|
+|password | String | 空字符串 | 否 |密码|
+|accessKey | String | 空字符串 | 否 |accessKey|
+|secretKey | String | 空字符串 | 否 |secretKey|
+
+当注册类型为`consul`时，支持的属性配置如下：
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|delay | int | 1 | 否 |对`Metadata`的监控每次轮询的间隔时长，单位为秒，默认`1`秒。|
+|wait-time | int | 55 | 否 |对`Metadata`的监控单次请求的等待时间（长轮询机制），单位为秒，默认`55`秒。|
+|metadata-path | String | `shenyu/register` | 否 |`Metadata`路径名称，默认是`shenyu/register`。|
+
+
+
+##### shenyu.sync 配置
+
+`Admin`端和网关使用数据同步的相关配置。
+
+使用`websocket`进行数据同步的属性配置如下：
+
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|enabled | boolean | true | 否 |是否启用`websocket`进行数据同步|
+|messageMaxSize | int | 0 | 否 |设置`websocket`缓冲区大小，单位为bytes|
+|allowOrigins | String | 空字符串 | 否 |设置允许的 `origins`, 多个参数以`;`分隔|
+
+使用`zookeeper`进行数据同步的属性配置如下：/
+
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|url | String | 无 | 是 |`zookeeper`的连接地址|
+|sessionTimeout | int | 无 | 是 |`session`的超时时间（毫秒）|
+|connectionTimeout | int | 无 | 是 |连接超时时间（毫秒）|
+
+
+使用`http长轮询`进行数据同步的属性配置如下：
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|enabled | boolean | true | 否 |是否启用|
+|refreshInterval | int | 5 （分钟） | 否 |定时从数据库获取数据并加载到内存|
+|notifyBatchSize | int | 100 | 否 |批量通知客户端|
+
+
+使用`nacos`进行数据同步的属性配置如下：
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|url | String | 无 | 是 |`nacos`连接地址|
+|namespace | String | 无 | 是 |命名空间|
+|username | String | 无 | 否 |用户名|
+|password | String | 无 | 否 |密码|
+|acm | | | 否 |阿里云ACM服务配置|
+
+- `acm`配置
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|enabled | boolean | false | 否 |是否启用|
+|endpoint | String | 无 | 是 |ACM服务地址|
+|namespace | String | 无 | 否 |namespace|
+|accessKey | String | 无 | 否 |accessKey|
+|secretKey | String | 无 | 否 |secretKey|
+
+
+使用`etcd`进行数据同步的属性配置如下：
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|url | String | 无 | 是 |`etcd`连接地址|
+
+
+
+使用`consul`进行数据同步的属性配置如下：
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|url | String | 无 | 是 |`consul`连接地址|
+
+
+##### shenyu.aes.secret 配置
+
+`aes`加密算法的相关配置。
+
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|key | String | `2095132720951327` | 否 |key|
+|iv | String | 无 | 否 |初始向量|
+
+
+##### shenyu.ldap 配置
+
+`Spring`中`ldap`的相关配置。
+
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|enabled | boolean | true | 否 |是否启用|
+|url | String | 无 | 是 |`ldap`连接地址|
+|bind-dn | String | 无 | 否 | UserDn |
+|password | String | 无 | 否 |密码|
+|base-dn | String | 无 | 否 | searchBase |
+|object-class | String | `person` | 否 | filter |
+|login-field | String | `cn` | 否 | searchBase|
+|connectTimeout | int | 3000 | 否 |连接超时时间（毫秒）|
+|readTimeout | int | 3000 | 否 |读取操作超时时间（毫秒）|
+
+
+##### shenyu.jwt 配置
+
+`jwt`的相关配置如下：
+
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+| expired-seconds | long | 24 *60* 60 * 1000L | 否 |过期时间（毫秒）|
+
+
+##### shenyu.shiro 配置
+
+`shiro`的相关配置如下：
+
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+| white-list | List | 无 | 否 |白名单列表|
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/property-config/client-property-config.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/property-config/client-property-config.md
new file mode 100644
index 00000000000..0e5a1e6ea60
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/property-config/client-property-config.md
@@ -0,0 +1,90 @@
+---
+title: 客户端属性配置
+keywords: ["配置"]
+description: Client属性配置
+---
+
+本篇主要讲解如何在客户端接入时配置 `ShenYu` 的相关属性。
+
+在你的微服务中设置`shenyu`属性，比如，在[shenyu-examples-http](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http) 中相关配置如下：
+
+
+
+### 属性配置
+
+```yaml
+shenyu:
+ client:
+ registerType: http #zookeeper #etcd #nacos #consul
+ serverLists: http://localhost:9095 #localhost:2181 #http://localhost:2379 #localhost:8848
+ props:
+ contextPath: /http
+ appName: http
+ port: 8189
+ nacosNameSpace: ShenyuRegisterCenter
+
+```
+
+
+### 属性详解
+
+##### shenyu.client 配置
+
+这是客户端接入的相关配置，客户端接入原理请参考：[客户端接入原理](../../design/register-center-design) ，客户端接入配置请参考： [客户端接入配置](register-center-access.md) 。
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|registerType |String | http | 必填 |使用哪种方式进行服务注册，当前支持 `http`、`zookeeper`、`etcd`、`consul`和`nacos` 。|
+|serverLists |String | 无 | 必填 |配置中心的地址。集群时，多个地址用 `,` 分开 。|
+|props | | | | 使用不同注册类型时，属性取值不同。|
+
+
+- `props`配置
+
+微服务由不同协议构建时，属性配置略有不同，通用属性如下：
+
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|contextPath |String | 无 | 是 |服务在网关中的路由前缀|
+|appName |String | 无 | 是 |服务名称。`springcloud`服务无需配置，请通过`spring.application.name`配置。|
+|host |String | 无 | 是 | 服务地址|
+|port |int | 无 | 是 | 服务端口|
+|isFull |boolean | false | 否 | 是否代理整个服务，目前适用于`springmvc`/`springcloud`|
+|ipAndPort |String | 无 | 否 | 服务的IP和端口地址，目前适用于`gRPC`。|
+|shutdownWaitTime |int | 3000 | 否 | 服务停止等待时间（毫秒）|
+|delayOtherHooksExecTime |int | 2000 | 否 | `hook`执行时间（毫秒）|
+|applicationShutdownHooksClassName |String | `java.lang.ApplicationShutdownHooks` | 否 | `hook`执行类|
+|applicationShutdownHooksFieldName |String | `hooks` | 否 | `hook`执行字段|
+
+
+使用不同的注册类型时，属性取值不同。
+当注册类型为`http`时，暂未提供其他属性配置。
+
+
+
+当注册类型为`zookeeper`时，支持的属性配置如下：
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|sessionTimeout | int | 30000 | 否 |session超时时间（毫秒）|
+|connectionTimeout | int | 3000 | 否 |连接超时时间（毫秒）|
+
+当注册类型为`etcd`时，支持的属性配置如下：
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|etcdTimeout | int | 30000 | 否 |etcd超时时间（毫秒）|
+|etcdTTL | int | 5 | 否 |租约生存时间（秒）|
+
+当注册类型为`nacos`时，支持的属性配置如下：
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|nacosNameSpace | String | 无 | 是 |命名空间|
+|username | String | 空字符串 | 否 |用户名|
+|password | String | 空字符串 | 否 |密码|
+|accessKey | String | 空字符串 | 否 |accessKey|
+|secretKey | String | 空字符串 | 否 |secretKey|
+
+当注册类型为`consul`时，暂未提供其他属性配置。请通过`spring.cloud.consul`进行配置。
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/property-config/gateway-property-config.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/property-config/gateway-property-config.md
new file mode 100644
index 00000000000..13b103bbe42
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/property-config/gateway-property-config.md
@@ -0,0 +1,642 @@
+---
+title: 网关属性配置
+keywords: ["配置"]
+description: 网关属性配置
+---
+
+本篇主要讲解如何在 `Apache Shenyu` 网关配置 `ShenYu` 的相关属性。
+
+
+
+### 属性配置
+
+```yaml
+shenyu:
+ selectorMatchCache:
+ ## selector L1 cache
+ cache:
+ enabled: false
+ initialCapacity: 10000 # initial capacity in cache
+ maximumSize: 10000 # max size in cache
+ ## selector L2 cache, use trie as L2 cache
+ trie:
+ enabled: false
+ cacheSize: 128 # the number of plug-ins
+ matchMode: antPathMatch
+ ruleMatchCache:
+ ## rule L1 cache
+ cache:
+ enabled: true
+ initialCapacity: 10000 # initial capacity in cache
+ maximumSize: 65536 # max size in cache
+ ## rule L2 cache, use trie as L2 cache
+ trie:
+ enabled: false
+ cacheSize: 1024 # the number of selectors
+ matchMode: antPathMatch
+ netty:
+ http:
+ webServerFactoryEnabled: true
+ selectCount: 1
+ workerCount: 4
+ accessLog: false
+ serverSocketChannel:
+ soRcvBuf: 87380
+ soBackLog: 128
+ soReuseAddr: true
+ connectTimeoutMillis: 30000
+ writeBufferHighWaterMark: 65536
+ writeBufferLowWaterMark: 32768
+ writeSpinCount: 16
+ autoRead: false
+ allocType: "pooled"
+ messageSizeEstimator: 8
+ singleEventExecutorPerGroup: true
+ socketChannel:
+ soKeepAlive: false
+ soReuseAddr: false
+ soLinger: -1
+ tcpNoDelay: true
+ soRcvBuf: 87380
+ soSndBuf: 16384
+ ipTos: 0
+ allowHalfClosure: false
+ connectTimeoutMillis: 30000
+ writeBufferHighWaterMark: 65536
+ writeBufferLowWaterMark: 32768
+ writeSpinCount: 16
+ autoRead: false
+ allocType: "pooled"
+ messageSizeEstimator: 8
+ singleEventExecutorPerGroup: true
+ instance:
+ enabled: false
+ registerType: zookeeper #etcd #consul
+ serverLists: localhost:2181 #http://localhost:2379 #localhost:8848
+ props:
+# httpclient:
+# strategy: webClient
+# connectTimeout: 45000
+# responseTimeout: 3000
+# readerIdleTime: 3000
+# writerIdleTime: 3000
+# allIdleTime: 3000
+# readTimeout: 3000
+# writeTimeout: 3000
+# wiretap: false
+# keepAlive: false
+# pool:
+# type: ELASTIC
+# name: proxy
+# maxConnections: 16
+# acquireTimeout: 45000
+# maxIdleTime: 3000
+# proxy:
+# host:
+# port:
+# username:
+# password:
+# nonProxyHostsPattern:
+# ssl:
+# useInsecureTrustManager: false
+# keyStoreType: PKCS12
+# keyStorePath: classpath:keystore.p12
+# keyStorePassword: 123456
+# keyStoreProvider:
+# keyPassword: 123456
+# trustedX509Certificates:
+# handshakeTimeout:
+# closeNotifyFlushTimeout:
+# closeNotifyReadTimeout:
+# defaultConfigurationType:
+ sync:
+ websocket:
+ urls: ws://localhost:9095/websocket
+ allowOrigin: ws://localhost:9195
+# zookeeper:
+# url: localhost:2181
+# sessionTimeout: 5000
+# connectionTimeout: 2000
+# http:
+# url: http://localhost:9095
+# nacos:
+# url: localhost:8848
+# namespace: 1c10d748-af86-43b9-8265-75f487d20c6c
+# username:
+# password:
+# acm:
+# enabled: false
+# endpoint: acm.aliyun.com
+# namespace:
+# accessKey:
+# secretKey:
+# etcd:
+# url: http://localhost:2379
+# consul:
+# url: http://localhost:8500
+# waitTime: 1000
+# watchDelay: 1000
+ cross:
+ enabled: true
+ allowedHeaders:
+ allowedMethods: "*"
+ allowedAnyOrigin: false
+ allowedOrigin:
+ # format : schema://prefix spacer domain
+ # Access-Control-Allow-Origin: "http://a.apache.org,http://b.apache.org"
+ spacer: "."
+ domain: apache.org
+ prefixes:
+ - a # a.apache.org
+ - b # b.apache.org
+ origins:
+ - c.apache.org
+ - d.apache.org
+ - http://e.apache.org
+ originRegex: ^http(|s)://(.*\.|)abc.com$
+ allowedExpose: ""
+ maxAge: "18000"
+ allowCredentials: true
+ switchConfig:
+ local: true
+ file:
+ enabled: true
+ maxSize : 10
+ exclude:
+ enabled: false
+ paths:
+ - /favicon.ico
+ fallback:
+ enabled: false
+ paths:
+ - /fallback/hystrix
+ - /fallback/resilience4j
+ health:
+ enabled: false
+ paths:
+ - /actuator/health
+ - /health_check
+ alert:
+ enabled: true
+ admins: localhost:9095
+ extPlugin:
+ path:
+ enabled: true
+ threads: 1
+ scheduleTime: 300
+ scheduleDelay: 30
+ scheduler:
+ enabled: false
+ type: fixed
+ threads: 16
+ upstreamCheck:
+ enabled: false
+ timeout: 3000
+ healthyThreshold: 1
+ unhealthyThreshold: 1
+ interval: 5000
+ printEnabled: true
+ printInterval: 60000
+ ribbon:
+ serverListRefreshInterval: 10000
+ metrics:
+ enabled: false
+ name : prometheus
+ host: 127.0.0.1
+ port: 8090
+ jmxConfig:
+ props:
+ jvm_enabled: true
+ sharedPool:
+ enable: true
+ prefix: "shenyu-shared"
+ corePoolSize: 200
+ maximumPoolSize: 2000
+ keepAliveTime: 60000
+ maxWorkQueueMemory: 1073741824 # 1GB
+ maxFreeMemory: 268435456 # 256MB
+```
+
+### 属性详解
+
+
+
+##### shenyu.matchCache 配置
+
+* 选择器匹配缓存配置
+
+| 字段 | 类型 | 默认值 | 是否必填 | 说明 |
+|-----------------|---------|---------|----------|-----------------------------------|
+| enabled | Boolean | false | No | 是否开启选择器缓存 |
+| initialCapacity | Integer | 10000 | No | 选择器缓存初始化容量 |
+| maximumSize | Integer | 10000 | No | 选择器缓存最大数量 |
+
+* 选择器前缀树缓存配置
+
+| 字段 | 类型 | 默认值 | 是否必填 | 说明 |
+|--------------|---------|--------------|----------|-----------------------------------------------------------------------------------|
+| enabled | Boolean | false | No | 是否开启选择器前缀树缓存 |
+| cacheSize | Integer | 512 | No | 前缀树缓存大小 |
+| matchMode | String | antPathMatch | Yes | shenyu路径匹配模式，shenyu支持两种匹配模式: `antPathMatch` and `pathPattern` |
+
+
+* 规则匹配缓存配置
+
+| 字段 | 类型 | 默认值 | 是否必填 | 说明 |
+|-----------------|---------|---------|----------|-----------|
+| enabled | Boolean | false | No | 是否开启选择器缓存 |
+| initialCapacity | Integer | 10000 | No | 规则缓存初始化容量 |
+| maximumSize | Integer | 10000 | No | 规则缓存最大数量 |
+
+* 规则前缀树缓存配置
+
+| 字段 | 类型 | 默认值 | 是否必填 | 说明 |
+|--------------|---------|--------------|----------|---------------------------------------------------------------|
+| enabled | Boolean | false | No | 是否开启规则前缀树缓存 |
+| cacheSize | Integer | 512 | No | 前缀树缓存大小 |
+| matchMode | String | antPathMatch | Yes | shenyu路径匹配模式，shenyu支持两种匹配模式: `antPathMatch` and `pathPattern` |
+
+
+shenyu默认开启L1和L2缓存, shenyu前缀树支持两种匹配模式，我们非常建议您使用`pathPattern`作为默认的匹配模式。
+
+> pathPattern: org.springframework.web.util.pattern.PathPatternParser
+> antPathMatch: org.springframework.util.AntPathMatcher
+
+当您将`matchRestful`标记为true时，我们建议将所有缓存标记为`false`，以避免匹配冲突。
+
+
+##### shenyu.NettyTcpProperties 配置
+
+Apache ShenYu reactor-netty 配置
+
+| 名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------------|:----- |:-------:|:--------:|:------------------------------------------------------------|
+| webServerFactoryEnabled | Boolean | true | 否 | 是否开启自定义参数，true-开启，false-可以自行配置NettyReactiveWebServerFactory |
+| selectCount | Integer | 1 | 否 | Netty 选择器数 |
+| workerCount | Integer | 4 | 否 | Netty 工作线程数 |
+| accessLog | Boolean | false | 否 | netty request parameters. |
+| **ServerSocketChannelConfig** | | | | |
+| soRcvBuf | Integer | -- | 否 | Socket参数，TCP数据接收缓冲区大小，默认由系统决定 |
+| soBackLog | Integer | 128 | 否 | Socket参数，服务端接受连接的队列长度 |
+| soReuseAddr | Boolean | true | 否 | Socket 参数，是否复用地址，reactor-netty中默认值为true |
+| connectTimeoutMillis | Integer | 30000 | 否 | Netty 参数，连接超时时间 |
+| writeBufferHighWaterMark | Integer | 65536 | 否 | Netty 参数，通道水位线上限 |
+| writeBufferLowWaterMark | Integer | 32768 | 否 | Netty 参数，通道水位线下限 |
+| writeSpinCount | Integer | 16 | 否 | Netty参数，一个Loop写操作执行的最大次数 |
+| autoRead | Boolean | false | 否 | Netty参数，自动读取，reactor-netty中默认值为false，且只能为false |
+| allocType | String | pooled | 否 | Netty参数，ByteBuf的分配器 |
+| messageSizeEstimator | Integer | 8 | 否 | Netty参数, 消息大小估算器, 用于估算ByteBuf,ByteBufHolder和FileRegion大小 |
+| singleEventExecutorPerGroup | Boolean | true | 否 | Netty参数, 单线程执行ChannelPipeline中的事件 |
+| **SocketChannelConfig** | | | | |
+| soKeepAlive | Boolean | false | 否 | Socket 参数，是否启用心跳保活机制 |
+| soReuseAddr | Boolean | true | 否 | Socket 参数，是否复用地址，reactor-netty中默认值为true |
+| soLinger | Integer | -1 | 否 | Socket 参数，关闭 Socket 的延迟时间 |
+| tcpNoDelay | Boolean | true | 否 | Socket 参数，是否启用 Nagle 算法 |
+| soRcvBuf | Integer | -- | 否 | Socket参数，TCP数据接收缓冲区大小，默认由系统决定 |
+| soSndBuf | Integer | -- | 否 | Socket参数，TCP数据发送缓冲区大小，默认由系统决定 |
+| ipTos | Integer | 0 | 否 | IP参数，设置IP头部的Type-of-Service字段，用于描述IP包的优先级和QoS选项 |
+| allowHalfClosure | Boolean | false | 否 | Netty参数，一个连接的远端关闭时本地端是否关闭 |
+| connectTimeoutMillis | Integer | 30000 | 否 | Netty 参数，连接超时时间 |
+| writeBufferHighWaterMark | Integer | 65536 | 否 | Netty 参数，通道水位线上限 |
+| writeBufferLowWaterMark | Integer | 32768 | 否 | Netty 参数，通道水位线下限 |
+| writeSpinCount | Integer | 16 | 否 | Netty参数，一个Loop写操作执行的最大次数 |
+| autoRead | Boolean | false | 否 | Netty参数，自动读取，reactor-netty中默认值为false，且只能为false |
+| allocType | String | pooled | 否 | Netty参数，ByteBuf的分配器 |
+| messageSizeEstimator | Integer | 8 | 否 | Netty参数, 消息大小估算器, 用于估算ByteBuf,ByteBufHolder和FileRegion大小 |
+| singleEventExecutorPerGroup | Boolean | true | 否 | Netty参数, 单线程执行ChannelPipeline中的事件 |
+
+
+
+##### shenyu.register 配置
+
+Apache ShenYu 网关注册到注册中心的相关配置，注册中心配置请参考 [注册中心配置](register-center-instance.md)
+
+| 名称 | 类型 | 默认值 | 是否必填 | 说明 |
+| :----------- | :-----: | :------------: | :------: | :---------------------------------------- |
+| enabled | boolean | false | 是 | 是否启动 |
+| registerType | String | zookeeper | 是 | 使用哪个注册中心，目前支持zookeeper、etcd |
+| serverLists | String | localhost:2181 | 是 | 注册中心的地址。若使用集群，用 `,` 分隔 |
+| props | | | | 使用不同注册类型时，属性取值不同。 |
+
+- `props`配置
+
+使用不同的注册中心时，属性取值不同
+
+当注册类型为 `zookeeper` 时，支持的属性配置如下：
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|sessionTimeout | int | 30000 | 否 |session超时时间（毫秒）|
+|connectionTimeout | int | 3000 | 否 |连接超时时间（毫秒）|
+
+当注册类型为 `etcd` 时，支持的属性配置如下：
+
+|名称 | 类型 | 默认值 | 是否必填 | 说明 |
+|:------------------------ |:----- |:-------: |:-------:|:----------------------------|
+|etcdTimeout | int | 30000 | 否 |etcd超时时间（毫秒）|
+|etcdTTL | int | 5 | 否 |租约生存时间（秒）|
+
+
+
+##### shenyu.httpclient 配置
+
+Apache ShenYu 网关中代理Http及SpringCloud协议后，用于发送代理请求的HttpClient配置
+
+| 名称 | 类型 | 默认值 | 是否必填 | 说明 |
+| :-------------- | :-----: | :-------: | :------: | :----------------------------------------------------------- |
+| strategy | String | webClient | No | HttpClientPlugin实现策略（默认使用webClient）：
+
+
+### Http方式注册配置
+
+#### shenyu-admin配置
+
+在 `yml`文件中配置注册类型为`http`，配置信息如下：
+
+```yaml
+shenyu:
+ register:
+ enabled: true
+ registerType: http
+ props:
+ checked: true #是否开启检测
+ zombieCheckTimes: 5 #失败几次后剔除服务
+ scheduledTime: 10 #定时检测间隔时间 （秒）
+```
+
+
+
+
+#### shenyu-client配置
+
+下面展示的是`http`服务作为客户端接入到`Apache ShenYu`网关时，通过`Http`方式注册配置信息。其他客户端接入时（`Dubbo`、 `Spring Cloud`等），配置方式同理。
+
+在微服务中的 `yml`文件配置注册方式设置为`http`，并填写`shenyu-admin`服务地址列表，配置信息如下：
+
+```yaml
+shenyu:
+ register:
+ enabled: true
+ registerType: http
+ serverLists: http://localhost:9095
+ props:
+ username: admin
+ password: 123456
+ client:
+ http:
+ props:
+ contextPath: /http
+ appName: http
+ port: 8188
+ isFull: false
+# registerType : 服务注册类型，填写 http
+# serverList: 为http注册类型时，填写Shenyu-Admin项目的地址，注意加上http://，多个地址用英文逗号分隔
+# port: 你本项目的启动端口，目前springmvc/tars/grpc需要进行填写
+# contextPath: 为你的这个mvc项目在shenyu网关的路由前缀， 比如/order ，/product 等等，网关会根据你的这个前缀来进行路由.
+# appName：你的应用名称，不配置的话，会默认取 `spring.application.name` 的值
+# isFull: 设置true 代表代理你的整个服务，false表示代理你其中某几个controller；目前适用于springmvc/springcloud
+```
+
+
+
+
+### 同时注册多种服务类型
+
+> 以同时注册http和dubbo服务举例。
+在`yml`参考如下配置即可：
+
+```yaml
+shenyu:
+ register:
+ registerType: http
+ serverLists: localhost
+ props:
+ username: admin
+ password: 123456
+ client:
+ http:
+ props:
+ contextPath: /http
+ appName: http
+ port: 8188
+ isFull: false
+ dubbo:
+ props:
+ contextPath: /dubbo
+ appName: dubbo
+ port: 28080
+ props:
+ nacosNameSpace: ShenyuRegisterCenter
+# registerType : 服务注册类型，填写 nacos
+# serverList: 为nacos注册类型时，填写nacos地址，多个地址用英文逗号分隔
+# http.port: 你本项目的启动Http端口,目前springmvc/SpringCloud需要进行填写
+# http.contextPath: 为你的这个mvc项目在shenyu网关的路由前缀，比如/order ，/product 等等，网关会根据你的这个前缀来进行路由.
+# http.appName：你的应用名称，不配置的话，会默认取 `spring.application.name` 的值
+# http.isFull: 设置true 代表代理你的整个服务，false表示代理你其中某几个controller；目前适用于springmvc/springcloud
+# dubbo.contextPath: 为你的项目中对应dubbo接口的contextPath
+# dubbo.port: dubbo服务端口
+# dubbo.appName: dubbo应用名称
+# nacosNameSpace: nacos的命名空间
+```
+
+
+总结，本文主要介绍了如何将你的微服务（当前支持`Http`、 `Dubbo`、 `Spring Cloud`、 `gRPC`、 `Motan`、 `Sofa`、 `Tars`等协议）接入到`Apache ShenYu`网关。介绍了注册中心的原理，`Apache ShenYu`网关支持的注册中心有`Http`方式。介绍了以`http`服务作为客户端接入到`Apache ShenYu`网关时，使用不同方式注册配置信息。
+
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/property-config/register-center-instance.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/property-config/register-center-instance.md
new file mode 100644
index 00000000000..9dfa3a1b1c2
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/property-config/register-center-instance.md
@@ -0,0 +1,66 @@
+---
+title: 注册中心配置
+description: 注册中心配置
+---
+
+本篇将介绍如何将网关实例注册到注册中心。`Apache ShenYu` 网关目前支持注册到 `zookeeper`、`etcd`。
+
+### 添加Maven依赖
+
+首先，在网关的 `pom.xml` 文件中引入如下依赖。
+
+```xml
+
+
+
+
+数据同步原理请参考设计文档中的 [数据同步原理](../../design/data-sync) 。
+
+### WebSocket同步配置（默认方式，推荐）
+
+* `Apache ShenYu`网关配置
+
+ 首先在 `pom.xml` 文件中引入以下依赖：
+
+```xml
+
+ 
+
+然后在 `yml` 文件中进行如下配置:
+
+```yaml
+shenyu:
+ sync:
+ websocket :
+ # urls:是指 shenyu-admin的地址，如果有多个，请使用（,）分割。
+ urls: ws://localhost:9095/websocket
+ allowOrigin: ws://localhost:9195
+```
+
+ 
+
+* `shenyu-admin 配置`
+
+ 在 `yml` 文件中进行如下配置:
+
+```yml
+shenyu:
+ sync:
+ websocket:
+ enabled: true
+```
+
+ 
+
+当建立连接以后会全量获取一次数据，以后的数据都是增量的更新与新增，性能好。而且也支持断线重连 （默认`30`秒）。推荐使用此方式进行数据同步，也是`Apache ShenYu`默认的数据同步策略。
+
+### Zookeeper同步配置
+
+> 请注意，从 ShenYu 2.5.0 起将不再支持 Zookeeper 3.4.x 或更低版本。如果您已经使用了 Zookeeper 3.4.x 或更低的版本，您需要使用更高的 Zookeeper 版本并重新初始化数据。
+
+* `Apache ShenYu`网关配置
+
+ 首先在 `pom.xml` 文件中引入以下依赖：
+
+ ```xml
+
+ 
+
+
+然后在 `yml` 文件中进行如下配置:
+
+```yaml
+shenyu:
+ sync:
+ zookeeper:
+ url: localhost:2181
+ # url: 配置成你的 zookeeper 地址，集群环境请使用（,）分隔
+ sessionTimeout: 5000
+ connectionTimeout: 2000
+```
+
+ 
+
+
+* `shenyu-admin` 配置
+
+在 `yml` 文件中进行如下配置:
+
+```yaml
+shenyu:
+ sync:
+ zookeeper:
+ url: localhost:2181
+ # url: 配置成你的 zookeeper 地址，集群环境请使用（,）分隔
+ sessionTimeout: 5000
+ connectionTimeout: 2000
+```
+
+ 
+
+
+使用`zookeeper`同步机制也是非常好的，时效性也高，但是要处理`zookeeper`环境不稳定，集群脑裂等问题。
+
+
+
+### Http长轮询同步配置
+
+* `Apache ShenYu`网关配置
+
+首先在 `pom.xml` 文件中引入以下依赖：
+
+```xml
+
+ 
+
+
+然后在 `yml` 文件中进行如下配置:
+
+```yaml
+shenyu:
+ sync:
+ http:
+ url: http://localhost:9095
+ # url: 配置成你的 shenyu-admin 的 ip 与端口地址，多个admin集群环境请使用（,）分隔。
+```
+
+ 
+
+
+* `shenyu-admin` 配置
+
+在 `yml` 文件中进行如下配置:
+
+```yaml
+shenyu:
+ sync:
+ http:
+ enabled: true
+```
+
+ 
+
+
+使用`Http长轮询`进行数据同步，会让网关很轻量，但时效性略低。它是根据分组`key`来拉取，如果数据量过大，过多，会有一定的影响。原因是一个组下面的一个小地方更改，都会拉取整个组的数据。
+
+
+### Nacos同步配置
+
+* `Apache ShenYu`网关配置
+
+首先在 `pom.xml` 文件中引入以下依赖：
+
+```xml
+
+ 
+
+
+然后在 `yml` 文件中进行如下配置:
+
+```yaml
+shenyu:
+ sync:
+ nacos:
+ url: localhost:8848
+ # url: 配置成你的 nacos地址，集群环境请使用（,）分隔。
+ namespace: 1c10d748-af86-43b9-8265-75f487d20c6c
+ username:
+ password:
+ acm:
+ enabled: false
+ endpoint: acm.aliyun.com
+ namespace:
+ accessKey:
+ secretKey:
+ # 其他参数配置，请参考 naocs官网。
+```
+
+ 
+
+
+* `shenyu-admin` 配置
+
+在 `yml` 文件中进行如下配置:
+
+```yaml
+shenyu:
+ sync:
+ nacos:
+ url: localhost:8848
+ # url: 配置成你的 nacos地址，集群环境请使用（,）分隔。
+ namespace: 1c10d748-af86-43b9-8265-75f487d20c6c
+ username:
+ password:
+ acm:
+ enabled: false
+ endpoint: acm.aliyun.com
+ namespace:
+ accessKey:
+ secretKey:
+ # 其他参数配置，请参考 naocs官网。
+```
+
+ 
+
+
+### Etcd 同步配置
+
+* `Apache ShenYu`网关配置
+
+首先在 `pom.xml` 文件中引入以下依赖：
+
+```xml
+
+ 
+
+
+然后在 `yml` 文件中进行如下配置:
+
+```yaml
+shenyu:
+ sync:
+ etcd:
+ url: http://localhost:2379
+ # url: 配置成你的 etcd，集群环境请使用（,）分隔。
+```
+
+ 
+
+
+* `shenyu-admin` 配置
+
+在 `yml` 文件中进行如下配置:
+
+```yaml
+shenyu:
+ sync:
+ etcd:
+ url: http://localhost:2379
+ # url: 配置成你的 etcd，集群环境请使用（,）分隔。
+```
+
+ 
+
+### Consul 同步配置
+
+* `Apache ShenYu`网关配置
+
+首先在 `pom.xml` 文件中引入以下依赖：
+
+```xml
+
+ 
+
+
+然后在 `yml` 文件中进行如下配置:
+
+```yaml
+shenyu:
+ sync:
+ consul:
+ url: http://localhost:8500
+ waitTime: 1000 # 查询等待时间
+ watchDelay: 1000 # 数据同步间隔时间
+```
+
+ 
+
+
+* `shenyu-admin` 配置
+
+在 `yml` 文件中进行如下配置:
+
+```yaml
+shenyu:
+ sync:
+ consul:
+ url: http://localhost:8500
+```
+
+ 
+
+
+
+> 在`Apache ShenYu`网关和`shenyu-admin` 重新配置数据同步策略后，需要重启服务。
+>
+> `Apache ShenYu`网关 和 `shenyu-admin` 必须使用相同的同步策略。
+
+### Apollo同步配置
+
+Apollo仅支持Java [8,17)版本，如果您要使用apollo作为数据同步中心，请确保您的JDK版本在[8,17)之间。
+
+* `Apache ShenYu`网关配置
+
+从`https://repo1.maven.org/maven2/org/apache/shenyu/shenyu-spring-boot-starter-sync-data-apollo/` 下载对应版本的jar包，然后将jar包放到`/lib`目录下。
+
+在yaml文件中添加如下配置：
+
+```yaml
+shenyu:
+ sync:
+ apollo:
+ appId: shenyu
+ meta: http://localhost:8080
+ env: dev
+ clusterName: test
+ namespace: application
+```
+
+* `Apache ShenYu Admin` 配置
+
+从`https://repo1.maven.org/maven2/org/apache/shenyu/shenyu-admin-listener-apollo/` 下载对应版本的jar包，然后将jar包放到`/lib`目录下。
+
+在yaml文件中添加如下配置：
+
+```yaml
+shenyu:
+ sync:
+ apollo:
+ meta: http://localhost:8080
+ appId: shenyu
+ portalUrl: http://localhost:8070
+ env: dev
+ clusterName: test
+ namespace: application
+ token: 0fff5645fc74ee5e0d63a6389433c8c8afc0beea31eed0279ecc1c8961d12da9
+```
+
+ 
+
+> 在`Apache ShenYu`网关和`shenyu-admin` 重新配置数据同步策略后，需要重启服务。
+> `Apache ShenYu`网关 和 `shenyu-admin` 必须使用相同的同步策略。
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/proxy/_category_.json b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/proxy/_category_.json
new file mode 100644
index 00000000000..3b3cf7f0ca7
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/proxy/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "快速接入",
+ "position": 4
+}
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/proxy/dubbo-proxy.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/proxy/dubbo-proxy.md
new file mode 100644
index 00000000000..34b54105c57
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/user-guide/proxy/dubbo-proxy.md
@@ -0,0 +1,439 @@
+---
+title: Dubbo服务接入
+keywords: ["Dubbo"]
+description: Dubbo服务接入
+---
+
+
+## 说明
+
+* 此篇文章是介绍 `dubbo` 服务接入到 `Apache ShenYu` 网关，`Apache ShenYu` 网关使用 `dubbo` 插件来接入`Dubbo`服务。
+* 当前支持 `alibaba dubbo（< 2.7.x）` 以及 `apache dubbo (>=2.7.x)`。
+* 接入前，请正确启动 `shenyu-admin`，并开启`dubbo`插件，在网关端和`Dubbo`服务端引入相关依赖。可以参考前面的 [Dubbo快速开始](../../quick-start/quick-start-dubbo)。
+
+
+应用客户端接入的相关配置请参考：[客户端接入配置](../property-config/register-center-access.md)。
+
+数据同步的相关配置请参考：[数据同步配置](../property-config/use-data-sync.md)。
+
+## 在网关中引入 dubbo 插件
+
+* 在网关的 `pom.xml` 文件中增加如下依赖：
+
+ * `alibaba dubbo` 用户, `dubbo` 版本换成你的，引入你需要的注册中心依赖，以下是参考。
+
+ ```xml
+
+ 
+
+客户端接入网关的注册中心支持(nacos、eureka、etcd、zookeeper、consul)，下面为`shenyu-bootstrap`及`应用客户端`使用**Zookeeper**注册中心时的相关指引。
+
+## 环境准备
+
+需要参考 `运维部署` , 选择一种方式启动`shenyu-admin`及`shenyu-bootstrap`.
+
+## shenyu-bootstrap
+
+### 添加Maven依赖
+
+在网关的`pom.xml`文件中引入如下依赖.
+
+```xml
+
+
+### Access to Back-end Services via NettyClient Test Result
+
+##### Test Result
+
+| currency | **QPS** | **50% latency (ms)** | **75% latency (ms)** | **90% latency (ms)** | **99% latency (ms)** | **Avg response time (ms)** | **Max response time (ms)** |
+|:-----------:|:--------:|:--------------------:|:--------------------:|:--------------------:|:--------------------:|:--------------:|:--------------:|
+| 600 concurrency | 20472.95 | 19.37 | 25.36 | 32.89 | 69.92 | 22.09 | 1043.33 |
+| 800 concurrency | 20703.55 | 23.57 | 31.32 | 40.11 | 77.28 | 26.11 | 576.47 |
+| 1000 concurrency | 20979.91 | 29.21 | 37.86 | 47.23 | 80.91 | 31.20 | 860.55 |
+| 1200 concurrency | 21129.88 | 32.45 | 42.40 | 52.68 | 96.10 | 35.06 | 1070 |
+
+#### Screenshot of Test Result
+
+##### 600 concurrency
+
+
+
+
+
+##### 800 concurrency
+
+
+
+
+
+##### 1000 concurrency
+
+
+
+
+
+##### 1200 concurrency
+
+
+
+
+
+### Access to Back-end Services via WebClient Test Result
+
+#### Test Result
+
+| currency | **QPS** | **50% latency (ms)** | **75% latency (ms)** | **90% latency (ms)** | **99% latency (ms)** | **Avg response time (ms)** | **Max response time (ms)** |
+|:-----------:|:--------:|:--------------------:|:--------------------:|:--------------------:|:--------------------:|:--------------:|:--------------:|
+| 600 concurrency | 18640.47 | 15.77 | 24.77 | 38.26 | 80.31 | 20.32 | 852.06 |
+| 800 concurrency | 18723.44 | 18.12 | 28.69 | 44.96 | 95.3 | 23.52 | 765.26 |
+| 1000 concurrency | 18928.99 | 19.99 | 31.42 | 49.09 | 108.84 | 25.93 | 1040 |
+| 1200 concurrency | 18965.37 | 22.10 | 34.62 | 54.48 | 122.31 | 28.66 | 1075 |
+
+#### Screenshot of Test Result
+
+##### 600 concurrency
+
+
+
+
+
+##### 800 concurrency
+
+
+
+
+##### 1000 concurrency
+
+
+
+
+##### 1200 concurrency
+
+
+
+
diff --git a/versioned_docs/version-2.6.1/deployment/_category_.json b/versioned_docs/version-2.6.1/deployment/_category_.json
new file mode 100644
index 00000000000..534be1dfb6d
--- /dev/null
+++ b/versioned_docs/version-2.6.1/deployment/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Deployment",
+ "position": 3
+}
diff --git a/versioned_docs/version-2.6.1/deployment/deployment-before.md b/versioned_docs/version-2.6.1/deployment/deployment-before.md
new file mode 100644
index 00000000000..298283ebf36
--- /dev/null
+++ b/versioned_docs/version-2.6.1/deployment/deployment-before.md
@@ -0,0 +1,56 @@
+---
+sidebar_position: 0
+title: Deployment Prerequisites
+keywords: ["Deployment Prerequisites"]
+description: Deployment Prerequisites
+---
+
+This article describes some of the prerequisites you need to prepare before deploying the Apache ShenYu gateway.
+
+## Database Initialize
+
+Before deploying the `Shenyu-admin` project, initialize the database it uses (databases currently support: Mysql, PostgreSql, Oracle), which used the script files are stored in db directory [project root directory](https://github.com/apache/shenyu/tree/master/db), The following describes the initial steps for each database.
+
+### Mysql
+
+In [the mysql initialization scripts directory](https://github.com/apache/shenyu/tree/master/db/init/mysql) found in the initialization script `schema.sql`, Use the client connection tool to connect to your Mysql service and execute, so you get a database named `shenyu`, which can later be used as the database for the `Shenyu-admin` project.
+
+* sql script: https://github.com/apache/shenyu/tree/master/db/init/mysql
+
+* driver:
+
+ * maven repository: https://repo1.maven.org/maven2/mysql/mysql-connector-java/8.0.30/
+ * homepage: https://www.mysql.com/products/connector/
+
+### PostgreSql
+
+In [the pg initialization scripts directory](https://github.com/apache/shenyu/tree/master/db/init/pg) found in the initialization script `create-database.sql`、 `create-table.sql`, and use the client connection tool to connect to your PostgreSql service. so you get a database named `shenyu`, which can later be used as a database for the `Shenyu-admin` project.
+
+* sql script: https://github.com/apache/shenyu/tree/master/db/init/pg
+
+* driver:
+
+ * maven repository: https://mvnrepository.com/artifact/org.postgresql/postgresql/42.5.0
+ * homepage: https://jdbc.postgresql.org/download/
+
+### Oracle
+
+In [the oracle initialization scripts directory](https://github.com/apache/shenyu/blob/master/db/init/oracle) found in the initialization script `schema.sql`, Use the client connection tool to connect to your Oracle service to create a database, execute the `schema.sql` script on this database, and initialize the `Shenyu-admin` database. After can be [project configuration file](https://github.com/apache/shenyu/blob/master/shenyu-admin/src/main/resources/application-oracle.yml) to adjust your Oracle environment configuration.
+
+* sql script: https://github.com/apache/shenyu/blob/master/db/init/oracle
+
+* driver:
+
+ * maven repository: https://mvnrepository.com/artifact/com.oracle.database.jdbc/ojdbc8/19.3.0.0
+ * homepage: https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html
+
+### OpenGauss
+
+In [the openGuass initialization scripts directory](https://github.com/apache/shenyu/blob/master/db/init/og) found in the initialization script `create-table.sql`, Use the client connection tool to connect to your openGauss service to create a database, execute the `create-table.sql` script on this database, and initialize the `Shenyu-admin` database. After can be [project configuration file](https://github.com/apache/shenyu/blob/master/shenyu-admin/src/main/resources/application-og.yml) to adjust your openGauss environment configuration.
+
+* sql script: https://github.com/apache/shenyu/blob/master/db/init/og
+
+* driver:
+
+ * maven repository: https://mvnrepository.com/artifact/org.opengauss/opengauss-jdbc/5.0.0-og
+ * homepage: https://gitee.com/opengauss/openGauss-connector-jdbc
diff --git a/versioned_docs/version-2.6.1/deployment/deployment-cluster.md b/versioned_docs/version-2.6.1/deployment/deployment-cluster.md
new file mode 100644
index 00000000000..a24277f8c16
--- /dev/null
+++ b/versioned_docs/version-2.6.1/deployment/deployment-cluster.md
@@ -0,0 +1,246 @@
+---
+sidebar_position: 7
+title: Cluster Deployment
+keywords: ["Gateway Cluster Environment", "Cluster Environment"]
+description: Cluster Deployment
+---
+
+> Before you read this document, you need to complete some preparations before deploying Shenyu according to the [Deployment Prerequisites document](./deployment-before.md).
+
+This article introduces how to deploy the `Shenyu` gateway in cluster environment.
+
+> In this part, you can see [ShenYu Binary Packages Deployment](./deployment-package.md) before deploying.
+
+### Environmental Preparation
+
+* Two or more Gateway Boostrap servers, these servers must install JDK1.8+.
+* A server for Gateway Admin, this server must install mysql/pgsql/h2 and JDK1.8+.
+* A server for nginx.
+
+### Start Apache ShenYu Admin
+
+* download and unzip [apache-shenyu-${current.version}-admin-bin.tar.gz](https://archive.apache.org/dist/incubator/shenyu/2.5.1/apache-shenyu-2.5.1-admin-bin.tar.gz) in your Gateway Admin server.
+
+* config your database, go to the `/conf` directory, and modify `spring.profiles.active` of the configuration in `application.yaml` to `mysql`, `pg` or `h2`.
+
+* config your way of synchronization, go to the `/conf` directory, and modify `shenyu.sync` of configuration in `application.yaml` to `websocket`, `http`, `zookeeper`, `etcd`, `consul` or `nacos`.
+
+* start Apache ShenYu Admin in `bin` directory.
+
+```
+> windows: start.bat
+
+> linux: ./start.sh
+```
+
+### Start Apache ShenYu Boostrap
+
+* download and unzip [apache-shenyu-${current.version}-bootstrap-bin.tar.gz](https://archive.apache.org/dist/incubator/shenyu/2.5.1/apache-shenyu-2.5.1-bootstrap-bin.tar.gz) in your Gateway Boostrap server.
+
+* config your synchronization, go to the `/conf` directory, and modify `shenyu.sync` of configuration in `application.yaml` to `websocket`, `http`, `zookeeper`, `etcd`, `consul` or `nacos`, this configuaration must remain the same of `ShenyYu Admin`.
+
+* repeat above-mentioned operations in each `ShenYu Bootstrap` server.
+
+* start Apache ShenYu Bootstrap in `bin` directory.
+
+```
+> windwos : start.bat
+
+> linux : ./start.sh
+```
+
+> After completing these operations, you will deploy `ShenYu Boostrap` Cluster.
+>
+> For example. you will deploy `ShenYu Bootstrap` in `10.1.1.1` and `10.1.1.2` and deploy nginx in `10.1.1.3`.
+
+### Start Nginx
+
+* download and install `nginx`.
+
+* modify `upstream` and `server` of configuration in `nginx.conf`.
+
+```nginx
+upstream shenyu_gateway_cluster {
+ ip_hash;
+ server 10.1.1.1:9195 max_fails=3 fail_timeout=10s weight=50;
+ server 10.1.1.2:9195 max_fails=3 fail_timeout=10s weight=50;
+}
+
+server {
+ listen 9195;
+ location / {
+ proxy_pass http://shenyu_gateway_cluster;
+ proxy_set_header HOST $host;
+ proxy_read_timeout 10s;
+ proxy_connect_timeout 10s;
+ }
+}
+```
+
+* start nginx.
+
+```
+> windows: ./nginx.exe
+
+> linux: /usr/local/nginx/sbin/nginx
+```
+
+* verify nginx, looking at your `ShenYu Bootstrap` log or `Nginx` log, Where will the verification request go.
+
+Apache ShenYu Nginx Module
+
+---
+
+This module provided SDK to watch available ShenYu instance list as upstream nodes by Service Register Center for OpenResty.
+1. [ETCD](#greeting-etcd) (Supported)
+2. [Nacos](#greeting-nacos) (Supported)
+3. [Zookeeper](#greeting-zookeeper) (Supported)
+4. Consul (TODO)
+
+In the cluster mode, Apache ShenYu supports the deployment of multiple ShenYu instances, which may have new instances joining or leaving at any time.
+Hence, Apache ShenYu introduces Service Discovery modules to help client to detect the available instances.
+Currently, Apache ShenYu Bootstrap already supports Apache Zookeeper, Nacos, Etcd, and consul. Client or LoadBalancer can get the available ShenYu instances by those Service register center.
+
+## Getting Started
+
+- Prerequisite:
+1. Luarocks
+2. OpenResty
+
+### Build from source
+
+The first, clone the source from GitHub.
+
+```
+git clone https://github.com/apache/shenyu-nginx
+```
+
+Then, build from source and install.
+
+```
+cd shenyu-nginx
+luarocks make rockspec/shenyu-nginx-main-0.rockspec
+```
+
+### Greeting ETCD
+
+Modify the Nginx configure, create and initialize the ShenYu Register to connect to the target register center.
+The module will fetch the all of ShenYu instances which are registered to Etcd in the same cluster.
+It works like Etcd client to watch(based on long polling) ShenYu instance lists.
+
+Here is an example for Etcd.
+
+```
+init_worker_by_lua_block {
+ local register = require("shenyu.register.etcd")
+ register.init({
+ balancer_type = "chash",
+ etcd_base_url = "http://127.0.0.1:2379",
+ })
+}
+```
+
+1. `balancer_type` specify the balancer. It has supported `chash` and `round robin`.
+2. `etcd_base_url` specify the Etcd server.(Currently, authentication is not supported.)
+
+Add an `upstream block` for ShenYu and enable to update upstream servers dynamically. This case will synchronize the ShenYu instance list with register center.
+And then pick one up for handling the request.
+
+```
+upstream shenyu {
+ server 0.0.0.1; -- bad
+
+ balancer_by_lua_block {
+ require("shenyu.register.etcd").pick_and_set_peer()
+ }
+}
+```
+
+Finally, restart OpenResty.
+
+```
+openresty -s reload
+```
+
+Here is a completed [example](https://github.com/apache/shenyu-nginx/blob/main/example/etcd/nginx.conf) working with ETCD.
+
+### Greeting Nacos
+
+Modify the Nginx configure, create and initialize the ShenYu Register to connect to target register center. Here is an example for Nacos.
+
+```
+init_worker_by_lua_block {
+ local register = require("shenyu.register.nacos")
+ register.init({
+ shenyu_storage = ngx.shared.shenyu_storage,
+ balancer_type = "chash",
+ nacos_base_url = "http://127.0.0.1:8848",
+ username = "nacos",
+ password = "naocs",
+ })
+}
+```
+
+1. `balancer_type` specify the balancer. It has supported `chash` and `round robin`.
+2. `nacos_base_url` specify the Nacos server address.
+3. `username` specify the username to log in Nacos. (it is only required when Nacos auth enable)
+4. `password` specify the password to log in Nacos.
+
+Modify the `upstream` to enable to update upstream servers dynamically. This case will synchronize the ShenYu instance list with register center.
+And then pick one up for handling the request.
+
+```
+upstream shenyu {
+ server 0.0.0.1; -- bad
+
+ balancer_by_lua_block {
+ require("shenyu.register.nacos").pick_and_set_peer()
+ }
+}
+```
+
+Finally, restart OpenResty.
+
+```
+openresty -s reload
+```
+
+Here is a completed [example](https://github.com/apache/shenyu-nginx/blob/main/example/nacos/nginx.conf) working with Nacos.
+
+## Greeting Zookeeper
+
+Modify the Nginx configure, create and initialize the ShenYu register to connect to target register center.
+Listen for changes to the node via the zookeeper watch event. Here is an example of the zookeeper configuration.
+
+```
+init_worker_by_lua_block {
+ local register = require("shenyu.register.zookeeper")
+ register.init({
+ servers = {"127.0.0.1:2181","127.0.0.1:2182"},
+ shenyu_storage = ngx.shared.shenyu_storage,
+ balancer_type = "roundrobin"
+ });
+ }
+```
+
+1. `servers` zookeeper cluster address.
+2. ``balancer_type`` specify the balancer. It has supported `chash` and `round robin`.
+
+Modify the upstream to enable to update upstream servers dynamically. This case will synchronize the ShenYu instance list with register center. And then pick one up for handling the request.
+
+```
+ upstream shenyu {
+ server 0.0.0.1;
+ balancer_by_lua_block {
+ require("shenyu.register.zookeeper").pick_and_set_peer()
+ }
+ }
+```
+
+Finally, restart OpenResty.
+
+```
+openresty -s reload
+```
+
+Here is a completed [example](https://github.com/apache/shenyu-nginx/blob/main/example/zookeeper/nginx.conf) working with Zookeeper.
diff --git a/versioned_docs/version-2.6.1/deployment/deployment-custom.md b/versioned_docs/version-2.6.1/deployment/deployment-custom.md
new file mode 100644
index 00000000000..4ea65337cd6
--- /dev/null
+++ b/versioned_docs/version-2.6.1/deployment/deployment-custom.md
@@ -0,0 +1,66 @@
+---
+sidebar_position: 6
+title: Custom Deployment
+keywords: ["Custom"]
+description: Custom Deployment
+---
+
+This article describes how to build your own gateway based on `Apache ShenYu`.
+
+> Before you read this document, you need to complete some preparations before deploying Shenyu according to the [Deployment Prerequisites document](./deployment-before.md).
+
+### Start Apache ShenYu Admin
+
+* docker reference docker deployment Apache ShenYu Admin
+
+* liunx/windows reference binary packages deployment Apache ShenYu Admin
+
+### Build your own gateway (recommended)
+
+* first create an empty `springboot` project, you can refer to `shenyu-bootstrap`, or you can create it on [spring official website](https://spring.io/quickstart).
+
+* introduce the following `jar` package:
+
+```xml
+
+
+
+## Preface {#preface}
+
+Gateway is the entrance of request and it is a very important part in micro service architecture, therefore the importance of gateway high availability is self-evident. When we use gateway, we have to change configuration such as flow rule, route rule for satisfying business requirement. Therefore, the dynamic configuration of the gateway is an important factor to ensure the high availability of the gateway.
+
+In the actual use of Apache ShenYu Gateway, users also feedback some problems:
+
+* Apache ShenYu depends on ZooKeeper, how to use Etcd, Consul, Nacos and other registry center?
+
+* Apache ShenYu depends on Redis and InfluxDB, and do not use limiting plugins or monitoring plugins. Why need these?
+
+* Why not use configuration center for configuration synchronization?
+
+* Why can't updates be configured dynamically?
+
+* Every time you want to query the database, Redis is a better way.
+
+According to the feedback of users, we have also partially reconstructed ShenYu. The current data synchronization features are as follows:
+
+
+* All configuration is cached in ShenYu gateway memory, each request uses local cache, which is very fast.
+
+* Users can modify any data in the background of shenyu-admin, and immediately synchronize to the gateway memory.
+
+* Support ShenYu plugin, selector, rule data, metadata, signature data and other data synchronization.
+
+* All plugin selectors and rules are configured dynamically and take effect immediately, no service restart required.
+
+* Data synchronization mode supports Zookeeper, HTTP long polling, Websocket, Nacos, Etcd and Consul.
+
+
+## Principle Analysis {#principle-analysis}
+
+The following figure shows the process of data synchronization of ShenYu. ShenYu Gateway will synchronize configuration data from configuration service at startup, and support push-pull mode to get configuration change information, and then update local cache. The administrator can change the user permissions, rules, plugins and traffic configuration in the admin system(shenyu-admin), and synchronize the change information to ShenYu Gateway through the push-pull mode. Whether the mode is push or pull depends on the synchronization mode used.
+
+
+
+
+In the original version, the configuration service relied on the Zookeeper implementation to manage the back-end push of changes to the gateway. Now, WebSocket, HTTP long polling, ZooKeeper, Nacos, Etcd, and Consul can now be supported by specifying the corresponding synchronization policy by setting `shenyu.sync.${strategy}` in the configuration file. The default WeboSocket synchronization policy can be used to achieve second level data synchronization. However, it is important to note that Apache ShenYu Gateway and shenyu-admin must use the same synchronization policy.
+
+
+
+As showing picture below,`shenyu-admin` will issue a configuration change notification through `EventPublisher` after users change configuration,`EventDispatcher` will handle this modification and send configuration to corresponding event handler according to configured synchronization strategy.
+
+- If it is a `websocket` synchronization strategy,it will push modified data to `shenyu-web`,and corresponding `WebsocketDataHandler` handler will handle `shenyu-admin` data push at the gateway layer
+- If it is a `zookeeper` synchronization strategy,it will push modified data to `zookeeper`,and the `ZookeeperSyncCache` will monitor the data changes of `zookeeper` and process them
+- If it is a `http` synchronization strategy,`shenyu-web` proactively initiates long polling requests,90 seconds timeout by default,if there is no modified data in `shenyu-admin`,http request will be blocked,if there is a data change, it will respond to the changed data information,if there is no data change after 60 seconds,then respond with empty data,gateway continue to make http request after getting response,this kind of request will repeat.
+
+
+
+### Zookeeper Synchronization {#zookeeper-synchronization}
+
+The zookeeper-based synchronization principle is very simple,it mainly depends on `zookeeper` watch mechanism,`shenyu-web` will monitor the configured node,when `shenyu-admin` starts,all the data will be written to `zookeeper`,it will incrementally update the nodes of `zookeeper` when data changes,at the same time, `shenyu-web` will monitor the node for configuration information, and update the local cache once the information changes
+
+
+
+`Apache ShenYu` writes the configuration information to the zookeeper node,and it is meticulously designed. If you want to learn more about the code implementation, refer to the source code `ZookeeperSyncDataService`.
+
+### WebSocket Synchronization {#websocket-synchronization}
+
+The mechanism of `websocket` and `zookeeper` is similar,when the gateway and the `shenyu-admin` establish a `websocket` connection,`shenyu-admin` will push all data at once,it will automatically push incremental data to `shenyu-web` through `websocket` when configured data changes
+
+When we use websocket synchronization,pay attention to reconnect after disconnection,which also called keep heartbeat.`Apache ShenYu` uses `java-websocket` ,a third-party library,to connect to `websocket`. If you want to learn more about the code implementation, refer to the source code `WebsocketSyncDataService`.
+
+### Http Long Polling {#http-long-polling}
+
+The mechanism of zookeeper and websocket data synchronization is relatively simple,but http synchronization will be relatively complicated.ShenYu borrows the design ideas of `Apollo` and `Nacos` and realizes `http` long polling data synchronization using their advantages.Note that this is not traditional ajax long polling.
+
+
+
+http long polling mechanism as above,shenyu-web gateway requests shenyu-admin configuration services,timeout is 90 seconds,it means gateway layer request configuration service will wait at most 90 seconds,this is convenient for shenyu-admin configuration service to respond modified data in time,and therefore we realize near real-time push.
+
+After the http request reaches shenyu-admin, it does not respond immediately,but uses the asynchronous mechanism of Servlet3.0 to asynchronously respond to the data.First of all,put long polling request task `LongPollingClient` into `BlocingQueue`,and then start scheduling task,execute after 60 seconds,this aims to remove the long polling request from the queue after 60 seconds,even there is no configured data change.Because even if there is no configuration change,gateway also need to know,otherwise it will wait,and there is a 90 seconds timeout when the gateway requests configuration services.
+
+
+If the administrator changes the configuration data during this period,the long polling requests in the queue will be removed one by one, and respond which group’s data has changed(we distribute plugins, rules, flow configuration , user configuration data into different groups).After gateway receives response,it only knows which Group has changed its configuration,it need to request again to get group configuration data.Someone may ask,why don't you write out the changed data directly?We also discussed this issue deeply during development, because the http long polling mechanism can only guarantee quasi real-time,if gateway layer does not handle it in time,or administrator updates configuration frequently,we probably missed some configuration change push.For security, we only inform that a certain Group information has changed.
+
+
+When `shenyu-web` gateway layer receives the http response information,pull modified information(if exists),and then request `shenyu-admin` configuration service again,this will repeatedly execute. If you want to learn more about the code implementation, refer to the source code `HttpSyncDataService`.
+
+### Nacos Synchronization {#nacos-synchronization}
+
+
+The synchronization principle of Nacos is basically similar to that of ZooKeeper, and it mainly depends on the configuration management of Nacos. The path of each configuration node is similar to that of ZooKeeper.
+
+ShenYu gateway will monitor the configured node. At startup, if there is no configuration node in Nacos, it will write the synchronous full amount of data into Nacos. When the sequential data send changes, it will update the configuration node in Nacos in full amount. The local cache is updated.
+
+If you want to learn more about the code implementation, please refer to the source code `NacosSyncDataService` and the official documentation for [Nacos](https://nacos.io/zh-cn/docs/sdk.html) .
+
+### Etcd Synchronization {#etcd-synchronization}
+
+Etcd data synchronization principle is similar to Zookeeper, mainly relying on Etcd's watch mechanism, and each configuration node path is the same as that of Zookeeper.
+
+The native API for Etcd is a bit more complicated to use, so it's somewhat encapsulated.
+
+ShenYu gateway will listen to the configured node. When startup, if there is no configuration node in Etcd, it will write the synchronous full amount of data into Etcd. When the sequential data send changes, it will update the configuration node in Etcd incrementally.
+
+If you want to learn more about the code implementation, refer to the source `EtcdSyncDataService`.
+
+### Consul Synchronization {#consul-synchronization}
+
+
+Consul data synchronization principle is that the gateway regularly polls Consul's configuration center to get the configuration version number for local comparison.
+
+ShenYu gateway will poll the configured nodes regularly, and the default interval is 1s. When startup, if there is no configuration node in Consul, write the synchronous full amount of data into Consul, then incrementally update the configuration node in Consul when the subsequent data is sent to change. At the same time, Apache ShenYu Gateway will regularly polls the node of configuration information and pull the configuration version number for comparison with the local one. The local cache is updated when the version number is changed.
+
+If you want to learn more about the code implementation, refer to the source `ConsulsyncDataService`.
diff --git a/versioned_docs/version-2.6.1/design/database-design.md b/versioned_docs/version-2.6.1/design/database-design.md
new file mode 100644
index 00000000000..5e03ce634fa
--- /dev/null
+++ b/versioned_docs/version-2.6.1/design/database-design.md
@@ -0,0 +1,95 @@
+---
+sidebar_position: 1
+title: Admin Database Design
+keywords: ["db"]
+description: ShenYu Admin Database Design
+---
+
+Apache Shenyu Admin is the management system of the gateway, which can manage all plugins, selectors and rules visually, set users, roles and resources.
+
+## Plugin, Selector And Rule {#plugin-selector-and-rule}
+
+* Plugin: ShenYu uses the plugin design idea to realize the hot plug of the plugin, which is easy to expand. Built-in rich plugins, including RPC proxy, circuit breaker and current limiting, authority and certification, monitoring, and more.
+* Selector: Each plugin can set multiple selectors to carry out preliminary filtering of traffic.
+* Rule: Multiple rules can be set per selector for more fine-grained control of flow.
+
+* The Database Table UML Diagram:
+
+
+
+* Detailed design:
+
+ * One plugin corresponds to multiple selectors,one selector corresponds to multiple rules.
+
+ * One selector corresponds to multiple match conditions,one rule corresponds to multiple match conditions.
+
+ * Each rule handles differently in corresponding plugin according to field handler,field handler is a kind of data of JSON string type.You can view detail during the use of shenyu-admin.
+
+## Resource Permission {#resource-permission}
+
+* The resource are the menus and buttons in the shenyu-admin console.
+
+* Resource Permission use database to store user name,role,resource data and relationship.
+
+* The Resource Permission Table UML Diagram:
+
+
+* Detailed design:
+ - one user corresponds to multiple role,one role corresponds to multiple resources.
+
+## Data Permission {#data-permission}
+
+* Data Permission use database to store the relationship between users, selectors and rules.
+
+* The Data Permission Table UML Diagram:
+
+
+
+* Detailed design:
+ * The most important table is `data_permission`, where a user corresponds to multiple data permissions.
+ * The field `data_type` distinguishes between different types of data, which corresponds to the following: 0 -> selector, 1 -> rule.
+ * The field `data_id` holds the primary key id of the corresponding type.
+
+## Meta Data {#meta-data}
+
+* Metadata is used for generic invoke by gateway.
+* For each interface method, there is one piece of metadata.
+* The Database Table UML Diagram:
+
+
+
+
+* Detailed design：
+ * `path`: When the gateway is requested, a piece of data will be matched according to `path`, and then the subsequent process will be carried out.
+
+ * `rpc_ext`: Used to hold extended information for the RPC proxy.。
+
+## Dictionary Management {#dictionary-management}
+
+* Dictionary management is used to maintain and manage public data dictionaries.
+* The Database Table UML Diagram:
+
+
+
+## API Documentation {#API-documentation}
+
+* The API document tables used to maintain and manage API documents.
+* The API document (such as json, md, html, etc.) of common specifications (such as OpenApi3.0 and yapi) can be imported into `shenyu-admin` and finally stored in the API document tables.
+* API documents of other common specifications can be generated through the API document tables.
+* The Database Table UML Diagram:
+
+
+
+* Detailed design:
+ * A tag can have multiple child tags, the level of tags is unlimited, the lowest leaf node is API.
+ * Interfaces with the same path but supporting multiple http methods, they are counted as multiple APIs.
+ * An API has multiple request parameters and response fields.
+ * A parameter/field has its own type (model), and each type have multiple fields.
+ * A field has its own type, which corresponds to multiple values.
+ * A value can be used as either a request example value, or a response example value (for example, 200 indicates OK, and 400 indicates illegal parameters).
+ * The `query`, `header` and `body`, all of them are `json` stored in `mock_request_record`，but `body` does not support special types such as file。
+ * The `ext` of the `tag` table stores the full amount of json data of its parent tag (including the parent tag of the parent tag, and so on).
+ * The `ext` of the `api` table may store the IP list and the service name of `SpringCloud`.
+ * The `type` of the `parameter` table mainly includes `requestUrlParam`, `requestHeader`, `requestBody`, `requestPathVariable`, `responseHeader`, and `responseBody`; If the returned type is a special type (such as file), do not associate `model_id`.
+ * The `ext` of the `field` table stores generic type in json format (convenient for subsequent expansion), such as `{"genericTypes": [model_id1, model_id2]}`; `model_id` indicates which type has this field, `self_model_id` indicates which type of this field.
+ * The `is_example` of `detail` table indicates whether a value is a request sample value, true is a request sample value, and false is a response value.
diff --git a/versioned_docs/version-2.6.1/design/flow-control.md b/versioned_docs/version-2.6.1/design/flow-control.md
new file mode 100644
index 00000000000..9f33519b2be
--- /dev/null
+++ b/versioned_docs/version-2.6.1/design/flow-control.md
@@ -0,0 +1,36 @@
+---
+title: Flow Control Design
+keywords: ["flow-control"]
+description: ShenYu Flow Control Design
+---
+
+ShenYu gateway realizes flow control through plugins, selectors and rules. For related data structure, please refer to the previous [Apache ShenYu Admin Database Design](./database-design) .
+
+
+### Plugin
+
+In Apache ShenYu Admin System, each plugin uses Handle (JSON format) fields to represent different processing, and the plugin processing is used to manage and edit the custom processing fields in the JSON.
+
+The main purpose of this feature is to enable plugins to handle templated configurations.
+
+### Selector And Rule
+
+Selector and rule are the most soul of Apache ShenYu Gateway. Master it and you can manage any traffic.
+
+A plugin has multiple selectors, and one selector corresponds to multiple rules. The selector is the first level filter of traffic, and the rule is the final filter. For a plugin, we want to meet the traffic criteria based on our configuration before the plugin will be executed. Selectors and rules are designed to allow traffic to perform what we want under certain conditions. The rules need to be understood first.
+
+The execution logic of plugin, selector and rule is as follows. When the traffic enters into ShenYu gateway, it will first judge whether there is a corresponding plugin and whether the plugin is turned on. Then determine whether the traffic matches the selector of the plugin. It then determines whether the traffic matches the rules of the selector. If the request traffic meets the matching criteria, the plugin will be executed. Otherwise, the plugin will not be executed. Process the next one. ShenYu gateway is so through layers of screening to complete the flow control.
+
+
+
+
+### Traffic filtering
+
+
+
+Traffic filtering is the soul of the selector and the rule, corresponding to the matching conditions in the selector and the rule. According to different traffic filtering rules, we can deal with various complex scenes. Traffic filtering can fetch data from Http requests such as `Header`, `URI`, `Query`, `Cookie`, etc.
+
+You can then use `Match`, `=`, `SpEL`, `Regex`, `Groovy`, `Exclude`, etc, to Match the desired data. Multi-group matching Adds matching policies that can use And/Or.
+
+
+please refer to [Selector And Rule Config](../user-guide/admin-usage/selector-and-rule) for details.
diff --git a/versioned_docs/version-2.6.1/design/register-center-design.md b/versioned_docs/version-2.6.1/design/register-center-design.md
new file mode 100644
index 00000000000..7640e99aa50
--- /dev/null
+++ b/versioned_docs/version-2.6.1/design/register-center-design.md
@@ -0,0 +1,61 @@
+---
+title: Client Registry Design
+keywords: ["Client Access"]
+description: Application Client Access
+---
+
+> *Notice*
+> After ShenYu version 2.6.1, the ShenYu register just support http type, and the middleware register type has been removed.
+> So, please use the http register type to register your service.
+> ShenYu Register Center isn't microservice register center, it just register metadata, selector data, rule data to shenyu-admin, and then shenyu-admin will sync data to shenyu-gateway.
+
+
+Application client access means to access your microservice to ShenYu gateway, currently supports HTTP, Dubbo, Spring Cloud, gRPC, Motan, Sofa, Tars and other protocols access.
+
+Refer to the client access configuration in the user documentation for [Application Client Access Config](../user-guide/property-config/register-center-access.md) .
+
+
+
+
+## Design principle
+
+#### Client
+
+
+
+Declare the registry client type, such as HTTP, in your microservice configuration. Use SPI to load and initialize the corresponding registry client when the application starts, implement the post-processor interface associated with the Spring Bean, get the service interface information to register in it, and place the obtained information into Disruptor.
+
+The Registry client reads data from the Disruptor and registers the interface information with shenyu-admin, where the Disruptor decouples data from operations for scaling.
+
+#### Server
+
+
+
+Declare the registry server type, such as HTTP in the Shenyu-Admin configuration. When shenyu-admin is started, it will read the configuration type, load and initialize the corresponding registry server, and when the registry server receives the interface information registered by shenyu-client, it will put it into Disruptor, which will trigger the registration processing logic to update the interface information and publish a synchronous event.
+
+Disruptor provides data and operations decoupling for expansion. If there are too many registration requests, resulting in abnormal registration, there is also a data buffer role.
+
+## Http Registry
+
+The principle of HTTP service registration is relatively simple. After Shenyu-Client is started, the relevant service registration interface of Shenyu-Admin will be called to upload data for registration.
+
+After receiving the request, shenyu-admin will update the data and publish the data synchronization event to synchronize the interface information to ShenYu Gateway.
+
+## SPI
+
+| *SPI Name* | *Description* |
+| -------------------------------- | --------------------------- |
+| ShenyuClientRegisterRepository | ShenYu client register SPI |
+
+| *Implementation Class* | *Description* |
+| -------------------------------- | --------------------------- |
+| HttpClientRegisterRepository | Http client register repository |
+
+
+| *SPI Name* | *Description* |
+| -------------------------------- | ----------------------------- |
+| ShenyuServerRegisterRepository | ShenYu server register SPI |
+
+| *Implementation Class* | *Description* |
+| -------------------------------- | ----------------------------- |
+| ShenyuHttpRegistryController | Http server repository |
diff --git a/versioned_docs/version-2.6.1/design/spi-design.md b/versioned_docs/version-2.6.1/design/spi-design.md
new file mode 100644
index 00000000000..4aee4218411
--- /dev/null
+++ b/versioned_docs/version-2.6.1/design/spi-design.md
@@ -0,0 +1,49 @@
+---
+title: SPI Design
+keywords: ["spi design"]
+description: spi-design
+---
+
+
+SPI, called Service Provider Interface, is a built-in JDK Service that provides discovery function and a dynamic replacement discovery mechanism.
+
+
+[shenyu-spi](https://github.com/apache/shenyu/tree/master/shenyu-spi) is a custom SPI extension implementation for Apache Shenyu gateway. The design and implementation principles refer to [SPI Extension Implementations](https://dubbo.apache.org/en/docs/v2.7/dev/impls/) .
+
+
+### Registry Center
+
+`Consul`, `Etcd`, `Http`, `Nacos` and `Zookeeper` are supported. The expansion of the registry including client and server, interface respectively `ShenyuServerRegisterRepository` and `ShenyuClientRegisterRepository`.
+
+### Metrics Center
+
+Responsible for service monitoring, loading concrete implementation through `SPI`, currently support `Prometheus`, service interface is `MetricsService`.
+
+
+
+### Load Balance
+
+Select one of the service providers to call. Currently, the supported algorithms are `Has`, `Random`, and `RoundRobin`, and the extended interface is `LoadBalance`.
+
+### RateLimiter
+
+
+In the `RateLimiter` plugin, which stream limiting algorithm to use, currently supporting `Concurren`, `LeakyBucke`, `SlidingWindow` and `TokenBucket`, the extension interface is `RateLimiterAlgorithm`.
+
+
+### Match Strategy
+
+Which matching method to use when adding selectors And rules, currently supports `And`, `Or`, And the extension interface is `MatchStrategy`.
+
+
+### Parameter Data
+
+
+Currently, `URI`,`RequestMethod`, `Query`, `Post`, `IP`, `Host`, `Cookie`, and `Header` are supported. The extended interface is `ParameterData`.
+
+
+### Predicate Judge
+
+Which conditional policy to use when adding selectors and rules currently supports `Match`, `Contains`,`Equals`, `Groovy`, `Regex`, `SpEL`, `TimerAfter`, `TimerBefore` and `Exclude`. The extension interface is `PredicateJudge`.
+
+
diff --git a/versioned_docs/version-2.6.1/design/wasm-plugin-design.md b/versioned_docs/version-2.6.1/design/wasm-plugin-design.md
new file mode 100644
index 00000000000..60f9eff0dc3
--- /dev/null
+++ b/versioned_docs/version-2.6.1/design/wasm-plugin-design.md
@@ -0,0 +1,25 @@
+---
+title: WASM plugin design
+keywords: ["WASM"]
+description: Apache ShenYu WASM plugin design
+---
+
+`Apache ShenYu` is a Java native API Gateway for service proxy, protocol conversion and API governance. Currently, ShenYu has good scalability in the Java language. However, ShenYu's support for multiple languages is still relatively weak.
+
+`WASM`(WebAssembly) bytecode is designed to be encoded in a size- and load-time-efficient binary format. WebAssembly aims to leverage the common hardware features available on various platforms to execute in browsers at machine code speed.
+
+`WASI`(WebAssembly System Interface) allows WASM to run in non browser environments such as Linux.
+
+The goal of `WASMPlugin` is to be able to run WASM bytecode. Other languages, as long as their code can be compiled into WASM bytecode (such as Rust/golang/C++), can be used to write ShenYu plugins.
+
+## Develop Phase
+
+
+
+> DictionaryType: `loadBalance`;
+>
+> DictionaryCode: `LOAD_BALANCE`;
+>
+> DictionaryName: `${spi name}`, input your custom spi name;
+>
+> DictionaryValue: When used, the value of the drop-down box, do not repeat with the existing;
+>
+> DictionaryDescribe: desc your custom match strategy;
+>
+> Sort: to sort;
+
+* When adding selectors or rules, you can use custom MatchType:
+
+
diff --git a/versioned_docs/version-2.6.1/developer/spi/custom-match-mode.md b/versioned_docs/version-2.6.1/developer/spi/custom-match-mode.md
new file mode 100644
index 00000000000..3539e3e54ff
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/spi/custom-match-mode.md
@@ -0,0 +1,72 @@
+---
+title: Custom Match Mode
+keywords: ["MatchStrategy"]
+description: custom match mode
+---
+
+
+* This paper describes how to customize the extension of `org.apache.shenyu.plugin.base.condition.strategy.MatchStrategy`.
+
+* Create a new project and introduce the following dependencies:
+
+```xml
+
+
+> DictionaryType: `matchMode`;
+>
+> DictionaryCode: `MATCH_MODE`;
+>
+> DictionaryName: `${spi name}`, input your custom spi name;
+>
+> DictionaryValue: When used, the value of the drop-down box, do not repeat with the existing;
+>
+> DictionaryDescribe: desc your custom match strategy;
+>
+> Sort: to sort;
+>
+> Status: open or close.
+
+* When adding selectors or rules, you can use custom MatchType:
+
+
diff --git a/versioned_docs/version-2.6.1/developer/spi/custom-metrics-monitor.md b/versioned_docs/version-2.6.1/developer/spi/custom-metrics-monitor.md
new file mode 100644
index 00000000000..c8bf88e78c4
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/spi/custom-metrics-monitor.md
@@ -0,0 +1,63 @@
+---
+title: Custom Metrics Monitor
+keywords: ["MetricsMonitor"]
+description: custom Metrics Monitor
+---
+
+
+## Explanation
+
+* Before custom development, please customize and build the gateway environment first, please refer to: [custom deployment](../deployment-custom)
+
+* This article describes how to customize the extension of `org.apache.shenyu.plugin.metrics.spi.MetricsService`.
+
+## Extension
+
+* Create a new project and introduce the following dependencies:
+
+```xml
+
diff --git a/versioned_docs/version-2.6.1/developer/spi/custom-mock-generator.md b/versioned_docs/version-2.6.1/developer/spi/custom-mock-generator.md
new file mode 100644
index 00000000000..618fb42b5ea
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/spi/custom-mock-generator.md
@@ -0,0 +1,77 @@
+---
+title: Custom Mock Data Generator
+keywords: ["Mock"]
+description: custom mock data generator
+---
+## Explanation
+
+1. This article describes how to make custom extensions to `org.apache.shenyu.plugin.mock.generator.Generator`.
+2. The mock data generation expression needs to satisfy the format of `${name|param1|param2|...}`
+
+## Extension
+
+* Create a new project and introduce the following dependencies:
+
+```xml
+
+
+> DictionaryType: `paramType`;
+>
+> DictionaryCode: `PARAM_TYPE`;
+>
+> DictionaryName: `${spi name}`, input your custom spi name;
+>
+> DictionaryValue: When used, the value of the drop-down box, do not repeat with the existing;
+>
+> DictionaryDescribe: desc your custom match strategy;
+>
+> Sort: to sort;
+>
+> Status: open or close.
+
+* When adding selectors or rules, you can use custom parameter data:
+
+
diff --git a/versioned_docs/version-2.6.1/developer/spi/custom-predicate-judge.md b/versioned_docs/version-2.6.1/developer/spi/custom-predicate-judge.md
new file mode 100644
index 00000000000..6b1640d5b89
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/spi/custom-predicate-judge.md
@@ -0,0 +1,121 @@
+---
+title: Custom Predicate Judge
+keywords: ["PredicateJudge"]
+description: Custom Predicate Judge
+---
+
+## Introduction
+
+* This paper describes how to customize the extension of `org.apache.shenyu.plugin.base.condition.judge.PredicateJudge`.
+* The conditional predicate is the bridge between data and rules in the selector and serves to filter out requests that match the conditions.
+* There are already seven conditional predicates including match, =, regex, contains, TimeBefore, TimeAfter, exclude.
+* Please refer to [judge](https://github.com/apache/shenyu/tree/master/shenyu-plugin/shenyu-plugin-base/src/main/java/org/apache/shenyu/plugin/base/condition/judge) module, add your own conditional predicates, or submit `pr` to the official website if you have a good common plugin.
+
+## Extension
+
+* Create a new project and introduce the following dependencies:
+
+```xml
+
+
+> DictionaryType: `operator`;
+>
+> DictionaryCode: `OPERATOR`;
+>
+> DictionaryName: `${spi name}`, input your custom spi name;
+>
+> DictionaryValue: When used, the value of the drop-down box, do not repeat with the existing;
+>
+> DictionaryDescribe: desc your custom match strategy;
+>
+> Sort: to sort;
+>
+> Status: open or close.
+
+* When adding selectors or rules, you can use custom predicate judge:
+
+
+
+## Example
+
+* Add `GroovyPredicateJudge` and `SpELPredicateJudge` extension.
+
+```java
+/**
+ * Groovy predicate judge.
+ */
+@Join
+public class GroovyPredicateJudge implements PredicateJudge {
+
+ @Override
+ public Boolean judge(final ConditionData conditionData, final String realData) {
+ return (Boolean) Eval.me(conditionData.getParamName(), realData, conditionData.getParamValue());
+ }
+}
+```
+
+```java
+/**
+ * SpEL predicate judge.
+ */
+@Join
+public class SpELPredicateJudge implements PredicateJudge {
+
+ private static final ExpressionParser EXPRESSION_PARSER = new SpelExpressionParser();
+
+ @Override
+ public Boolean judge(final ConditionData conditionData, final String realData) {
+ Expression expression = EXPRESSION_PARSER.parseExpression(conditionData.getParamValue().replace('#' + conditionData.getParamName(), realData));
+ return expression.getValue(Boolean.class);
+ }
+}
+```
+
+* Update `org.apache.shenyu.plugin.base.condition.judge.PredicateJudge`:
+
+```shell title="script"
+Groovy=xxx.xxx.xxx.GroovyPredicateJudge
+SpEL=xxx.xxx.xxx.SpELPredicateJudge
+```
diff --git a/versioned_docs/version-2.6.1/developer/spi/custom-rate-limiter.md b/versioned_docs/version-2.6.1/developer/spi/custom-rate-limiter.md
new file mode 100644
index 00000000000..4d2bebdbc65
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/spi/custom-rate-limiter.md
@@ -0,0 +1,104 @@
+---
+title: Custom Rate Limiter
+keywords: ["RateLimiter"]
+description: Custom Rate Limiter
+---
+
+## Explanation
+
+* Before custom development, please customize and build the gateway environment first, please refer to: [custom deployment](../deployment-custom).
+
+* This article describes how to customize the extension of `org.apache.shenyu.plugin.ratelimiter.algorithm.RateLimiterAlgorithm` .
+
+## Extension
+
+* Create a new project and introduce the following dependencies:
+
+```xml
+
+
+* Or execute the following custom `SQL` statement：
+
+```sql
+INSERT IGNORE INTO `shenyu_dict` (
+ `id`,
+ `type`,
+ `dict_code`,
+ `dict_name`,
+ `dict_value`,
+ `desc`,
+ `sort`,
+ `enabled`,
+ `date_created`,
+ `date_updated`
+ )
+VALUES (
+ 'you id',
+ 'matchMode',
+ 'MATCH_MODE',
+ 'you spi name',
+ 'you value',
+ 'you spi name',
+ 0,
+ 1,
+ '2021-08-30 19:29:10',
+ '2021-08-30 20:15:23'
+ );
+```
diff --git a/versioned_docs/version-2.6.1/developer/thread-model.md b/versioned_docs/version-2.6.1/developer/thread-model.md
new file mode 100644
index 00000000000..cee61af2ec3
--- /dev/null
+++ b/versioned_docs/version-2.6.1/developer/thread-model.md
@@ -0,0 +1,30 @@
+---
+title: Thread Model
+keywords: ["Thread"]
+description: thread model
+---
+
+## Description
+
+* This article gives an introduction to thread models in ShenYu and usage in various scenarios.
+
+## IO And Work Thread
+
+* `spring-webflux` is one of dependencies of ShenYu, and it uses Netty thread model in lower layer.
+
+## Business Thread
+
+* Use scheduling thread to execute by default.
+* A fixed thread pool manages business threads, the number of threads is count in this formula: cpu * 2 + 1.
+
+
+## Type Switching
+
+* `reactor.core.scheduler.Schedulers`.
+* `-Dshenyu.scheduler.type=fixed` is a default config. If set to other value, a flexible thread pool will take place it.`Schedulers.elastic()`.
+* `-Dshenyu.work.threads = xx` is for configuring number of threads, the default value calculates in following formula `cpu * 2 + 1` with a minimum of 16 threads.
+
+
+
+
+
diff --git a/versioned_docs/version-2.6.1/index.md b/versioned_docs/version-2.6.1/index.md
new file mode 100644
index 00000000000..6ed8b63106b
--- /dev/null
+++ b/versioned_docs/version-2.6.1/index.md
@@ -0,0 +1,179 @@
+---
+sidebar_position: 1
+title: Overview
+keywords: ["Apache shenyu"]
+description: This is an asynchronous, high-performance, cross-language, responsive API gateway.
+aliases: "/shenyu/docs/Home"
+---
+
+# Architecture
+
+ 
+
+# What is the Apache ShenYu?
+
+This is an asynchronous, high-performance, cross-language, responsive API gateway.
+
+# Why named Apache ShenYu
+
+ShenYu (神禹) is the honorific name of Chinese ancient monarch Xia Yu (also known in later times as Da Yu), who left behind the touching story of the three times he crossed the Yellow River for the benefit of the people and successfully managed the flooding of the river. He is known as one of the three greatest kings of ancient China, along with Yao and Shun.
+
+* Firstly, the name ShenYu is to promote the traditional virtues of our Chinese civilisation.
+* Secondly, the most important thing about the gateway is the governance of the traffic.
+* Finally, the community will do things in a fair, just, open and meritocratic way, paying tribute to ShenYu while also conforming to the Apache Way.
+
+---
+
+# Features
+
+* Proxy: Support for Apache® Dubbo™, Spring Cloud, gRPC, Motan, SOFA, TARS, WebSocket, MQTT
+* Security: Sign, OAuth 2.0, JSON Web Tokens, WAF plugin
+* API governance: Request, response, parameter mapping, Hystrix, RateLimiter plugin
+* Observability: Tracing, metrics, logging plugin
+* Dashboard: Dynamic traffic control, visual backend for user menu permissions
+* Extensions: Plugin hot-swapping, dynamic loading
+* Cluster: NGINX, Docker, Kubernetes
+* Language: provides .NET, Python, Go, Java client for API register
+
+---
+
+# Mind map
+
+ 
+
+ ---
+
+# Quick Start (docker)
+
+### Run Apache ShenYu Admin
+
+```
+docker pull apache/shenyu-admin
+docker network create shenyu
+docker run -d -p 9095:9095 --net shenyu apache/shenyu-admin
+```
+
+Default account: **admin**
+
+Default password: **123456**
+
+### Run Apache ShenYu Bootstrap
+
+```
+docker pull apache/shenyu-bootstrap
+docker run -d -p 9195:9195 -e "shenyu.local.enabled=true" --net shenyu apache/shenyu-bootstrap
+```
+
+### Set router
+
+* Real requests ：
+
+---
+
+# Contributor and Support
+
+* [How to Contribute](https://shenyu.apache.org/community/contributor-guide)
+* [Mailing Lists](mailto:dev@shenyu.apache.org)
+
+---
+
+# Known Users
+
+In order of registration, More access companies are welcome to register at [https://github.com/apache/shenyu/issues/68](https://github.com/apache/shenyu/issues/68) (For open source users only) .
+
+All Users : [Known Users](https://shenyu.apache.org/community/user-registration)
+
+---
diff --git a/versioned_docs/version-2.6.1/plugin-center/_category_.json b/versioned_docs/version-2.6.1/plugin-center/_category_.json
new file mode 100644
index 00000000000..5831affdd38
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Plugin Center",
+ "position": 6
+}
diff --git a/versioned_docs/version-2.6.1/plugin-center/cache/_category_.json b/versioned_docs/version-2.6.1/plugin-center/cache/_category_.json
new file mode 100644
index 00000000000..8768a0fab5a
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/cache/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Cache",
+ "position": 7
+}
diff --git a/versioned_docs/version-2.6.1/plugin-center/cache/cache-plugin.md b/versioned_docs/version-2.6.1/plugin-center/cache/cache-plugin.md
new file mode 100644
index 00000000000..10675c44589
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/cache/cache-plugin.md
@@ -0,0 +1,152 @@
+---
+title: Cache Plugin
+keywords: ["Cache"]
+description: Cache Plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Cache Plugin
+
+## 1.2 Appropriate Scenario
+
+* Situation where data is not updated frequently and a large number of calls are required.
+
+* For Situation where data consistency is not required.
+
+## 1.3 Plugin functionality
+
+* The `Cache` plugin is able to cache the results of the target service, allowing the user to configure the expiration
+ time of the cached results.
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-cache-handler`.
+* Core Module `shenyu-plugin-cache-redis`.
+* Core Module `shenyu-plugin-cache-memory`.
+
+* Core Class `org.apache.shenyu.plugin.cache.CachePlugin`
+* Core Class `org.apache.shenyu.plugin.cache.redis.RedisCache`
+* Core Class `org.apache.shenyu.plugin.cache.memory.MemoryCache`
+
+## 1.5 Added Since Which shenyu version
+
+* Since 2.4.3
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+* Import cache plugin dependency in `ShenYu Bootstrap`.
+
+```xml
+
+
+
+* Introduce `generalContext` support in the pox.xml file of the gateway.
+
+```xml
+
+ 
+
+
+
+## Add resilience4j plugin dependency
+
+* Add `resilience4j` dependency in the `pom.xml` file of the gateway.
+
+```xml
+
+ 
+
+#### Rule Config
+
+For the final filtering of traffic, there is a rule handler logic.
+
+
+
+* Resilience4j Processing Details
+
+ * `limitForPeriod` ：Configures the number of permissions available during one limit refresh period,default value:`50`.
+
+ * `limitRefreshPeriod` ：Configures the period of a limit refresh. After each period the rate limiter sets its permissions count back to the limitForPeriod value,default value:`500`.
+
+ * `timeoutDurationRate` ：Configures wait time(ms) a thread waits for a permission,default value:`5000`.
+
+ * `circuitEnable` ：Configures circuitBreaker enable, `0`:OFF ,`1`:ON ,default value:`0`.
+
+ * `failureRateThreshold` ：Configures the failure rate threshold in percentage,When the failure rate is equal or greater than the threshold the CircuitBreaker transitions to open and starts short-circuiting calls,default value:`50`.
+
+ * `fallbackUri` ：Configures the fallback uri.
+
+ * `minimumNumberOfCalls` ：Configures the minimum number of calls which are required (per sliding window period) before the CircuitBreaker can calculate the error rate or slow call rate,default value:`100`.
+
+ * `bufferSizeInHalfOpen`：Configures the number of permitted calls when the CircuitBreaker is half open,default value:`10`.
+
+ * `slidingWindowSize` ：Configures the size of the sliding window which is used to record the outcome of calls when the CircuitBreaker is closed,default value:`100`.
+
+ * `slidingWindowType` ：Configures the type of the sliding window which is used to record the outcome of calls when the CircuitBreaker is closed,
+ Sliding window can either be `0`:count-based or `1`:time-based.,default value:`0`.
+
+ * `timeoutDuration` ：Configures request CircuitBreaker timeout(ms),default value:`30000`.
+
+ * `waitIntervalInOpen` ：Configures the circuitBreaker time(ms) of duration,default value:`10`.
+
+ * `automaticTransitionFromOpenToHalfOpenEnabled` ：Configures automatically transition from open state to half open state,`true`:ON, `false`:OFF, default value:`false`.
diff --git a/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/sentinel-plugin.md b/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/sentinel-plugin.md
new file mode 100644
index 00000000000..9c7919098ba
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/fault-tolerance/sentinel-plugin.md
@@ -0,0 +1,215 @@
+---
+title: Sentinel Plugin
+keywords: ["Sentinel"]
+description: sentinel plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Sentinel Plugin
+
+## 1.2 Appropriate Scenario
+
+* `Sentinel` is one of the options that supports flow control and circuit breaking.
+* `Sentinel` supports flow control and circuit breaking functions for gateway.
+
+## 1.3 Plugin functionality
+
+* flow control
+* request circuit breaker and service degrade
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-sentinel`.
+
+* Core Class `org.apache.shenyu.plugin.sentinel.SentinelPlugin`
+
+## 1.5 Added Since Which shenyu version
+
+* Since 2.4.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+* Add `sentinel` dependency in the `pom.xml` file of the gateway(shenyu-bootstrap).
+
+```xml
+
+
+
+### 2.4.3 Rule configuration
+
+For the final filtering of traffic, there is a rule handler logic.
+
+
+
+| field | default value | field type | desc |
+|-----------------------------------------------------|--------------------|------------|----------------------------------------------------------------------------------------------------------------------------|
+| degradeRuleCount | | Doule | degrade threshold |
+| degradeRuleEnable | 1(enabled) | Integer | whether enable circuit breaking function of `sentinel` |
+| degradeRuleGrade | 0(slow call ratio) | Integer | circuit breaker strategy, support RT of seconds level/ Error Ratio of seconds level/ Error Count of minutes level strategy |
+| degradeRuleMinRequestAmount | 5 | Integer | circuit breaker min request amount |
+| degradeRuleSlowRatioThreshold | 1.0d | Double | slow ratio threshold of degrading |
+| degradeRuleStatIntervals | 1 | Integer | status intervals of degrade |
+| degradeRuleTimeWindow | | Integer | time of degrading(unit: second) |
+| flowRuleControlBehavior | 0(direact reject) | Integer | effect(reject directly/ queue/ slow start up), it do not support flow control by invocation relation. |
+ | flowRuleControlBehavior-direct rejection by default | | | |
+| flowRuleControlBehavior-warm up | | | |
+| flowRuleControlBehavior-constant speed queuing | | | |
+| flowRuleControlBehavior-preheating uniformly queued | | | |
+| flowRuleMaxQueueingTimeMs | 500ms | Integer | Maximum queuing time (valid in "preheating uniformly queued", "constant speed queuing" mode) |
+| flowRuleWarmUpPeriodSec | 10 | Integer | Cold start warm-up time (seconds) (valid in "preheating uniformly queued" "warm up" mode) |
+| flowRuleCount | | Integer | sentinel flow control count |
+| flowRuleEnable | 1(enabled) | Integer | whether enable sentinel flow control function. |
+| flowRuleGrade | 1(QPS) | Integer | type of current limit threshold(QPS or Thread Count)。 |
+| fallbackUri | | String | degraded uri after circuit breaking. |
+
+## 2.5 Examples
+
+### 2.5.1 Using sentinel for flow control
+
+#### 2.5.1.1 Plugin configuration
+
+For more information on selectors and rules configuration, see [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule) , only some of the fields are covered here.
+
+* In `shenyu-admin`--> BasicConfig --> Plugin --> `sentinel` set to enable.
+
+#### 2.5.1.2 Selector configuration
+
+
+
+#### 2.5.1.3 Rule configuration
+
+
+
+just use qps flow control strategy, and qps is 10, reject strategy is directly reject.
+
+the code is as follows:
+
+```java
+@RestController
+@RequestMapping("/order")
+@ShenyuSpringMvcClient("/order")
+public class OrderController {
+
+ /**
+ * Save order dto.
+ *
+ * @param orderDTO the order dto
+ * @return the order dto
+ */
+ @PostMapping("/save")
+ @ShenyuSpringMvcClient("/save")
+ public OrderDTO save(@RequestBody final OrderDTO orderDTO) {
+ orderDTO.setName("hello world save order");
+ return orderDTO;
+ }
+}
+```
+
+#### 2.5.1.4 request by `Apache Jmeter`
+
+* Jmeter thead group config
+
+
+
+* Jmeter http request config
+
+
+
+#### 2.5.1.5 Check result
+
+
+
+### 2.5.2 Using sentinel for request circuit breaker
+
+#### 2.5.2.1 Plugin configuration
+
+* In `shenyu-admin`--> BasicConfig --> Plugin --> `sentinel` set to enable.
+
+#### 2.5.2.2 Selector configuration
+
+
+
+#### 2.5.2.3 Rule configuration
+
+
+
+when degrade strategy is `exception number`, `degradeRuleSlowRatioThreshold` is not effective. When the minimum number of requests per unit of time is 5, and the request happens exception great than 3, it will trigger the circuit breaker.
+
+when degrade strategy is `slow call ratio`, `degradeRuleSlowRatioThreshold` is effective, `degradeRuleCount` means RT(e.g. 200).
+
+the code is as follows:
+
+```java
+@RestController
+@RequestMapping("/order")
+@ShenyuSpringMvcClient("/order")
+public class OrderController {
+
+ /**
+ * Save order dto.
+ *
+ * @param orderDTO the order dto
+ * @return the order dto
+ */
+ @PostMapping("/save")
+ @ShenyuSpringMvcClient("/save")
+ public OrderDTO save(@RequestBody final OrderDTO orderDTO) {
+
+ Random random = new Random();
+ int num = random.nextInt(100);
+ if (num > 40) {
+ throw new RuntimeException("num great than 20");
+ }
+ orderDTO.setName("hello world save order");
+ return orderDTO;
+ }
+
+}
+```
+
+#### 2.5.2.4 request by `Apache Jmeter`
+
+* Jmeter thead group config
+
+
+
+* Jmeter http request config
+
+
+
+#### 2.5.2.5 Check result
+
+
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `sentinel` set Status disable.
diff --git a/versioned_docs/version-2.6.1/plugin-center/http-process/_category_.json b/versioned_docs/version-2.6.1/plugin-center/http-process/_category_.json
new file mode 100644
index 00000000000..77ac2bace2f
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/http-process/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Http Process",
+ "position": 1
+}
diff --git a/versioned_docs/version-2.6.1/plugin-center/http-process/contextpath-plugin.md b/versioned_docs/version-2.6.1/plugin-center/http-process/contextpath-plugin.md
new file mode 100644
index 00000000000..8a05fe6c1fb
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/http-process/contextpath-plugin.md
@@ -0,0 +1,127 @@
+---
+title: ContextPath Plugin
+keywords: ["contextPath"]
+description: contextPath plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* ContextPath Plugin
+
+## 1.2 Appropriate Scenario
+
+* Different services can do traffic governance of services by setting different context paths.
+
+## 1.3 Plugin functionality
+
+* Set the context path for service.
+* When the interface is called, the plug-in uniformly prefixes the interface address of the service.
+
+## 1.4 Plugin Code
+
+* Core module ```shenyu-plugin-context-path```
+* Core class ```org.apache.shenyu.plugin.context.path.ContextPathPlugin```
+
+## 1.5 Added since which shenyu version
+
+* 2.3.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+- import maven config in shenyu-bootstrap project's `pom.xml` file.
+
+```xml
+ 
+
+## 2.2 Import pom
+
+ - import maven config in shenyu-bootstrap project's `pom.xml` file.
+
+ ```xml
+
+ 
+
+## 2.4 Config plugin
+
+ - Selector and rule config, please refer: [Selector and rule config](../../user-guide/admin-usage/selector-and-rule).
+ - In `shenyu-admin` --> `PluginList` --> `HttpProcess` --> `Redirect`, add selector config first，then add rule config：
+ - Add selector config
+
+ 
+ - Add rule config
+
+ 
+
+## 2.5 Examples
+
+### 2.5.1 Redirect
+
+ - When we configure a custom path in `Rule`, it should be a reachable service path.
+ - When the request is matched, the `ShenYu Gateway` will perform the `308` service jump according to the customized path.
+ 1. Refer [Local Deployment](https://shenyu.apache.org/docs/deployment/deployment-local/) to start admin and bootstrap.
+ 2. Refer 2.2 to import pom and restart bootstrap.
+ 3. Refer 2.3 to enable plugin.
+ 4. Refer 2.4 and [Selector and rule config](../../user-guide/admin-usage/selector-and-rule).
+ 5. Invoke interface: [demo](http://localhost:9195/http)
+ - Invoke the interface declared by selectors and rules will redirect to the specified path.
+ - In this demo, it will jump to [ShenYu official website](https://shenyu.apache.org)
+
+ 
+
+### 2.5.2 Gateway's own interface forwarding
+
+ - When the matching rules are met, the service will use the `DispatcherHandler` internal interface for forwarding.
+ - To implement the gateway's own interface forwarding, we need to use `/` as the prefix in the configuration path. The specific configuration is as shown in the figure below.
+
+ 
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `Redirect` set Status disable.
+
+ 
diff --git a/versioned_docs/version-2.6.1/plugin-center/http-process/request-plugin.md b/versioned_docs/version-2.6.1/plugin-center/http-process/request-plugin.md
new file mode 100644
index 00000000000..b3757c51204
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/http-process/request-plugin.md
@@ -0,0 +1,91 @@
+---
+title: Request Plugin
+keywords: ["request"]
+description: request plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Request Plugin
+
+## 1.2 Appropriate Scenario
+
+* The request plugin is able to make customized changes to the request parameters of `uri`.
+
+## 1.3 Plugin functionality
+
+* The `Apache ShenYu` gateway allows users to use the `request` plugin to add, modify, and remove request headers to request parameters, request headers, and `Cookie` when proxying a target service.
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-request`
+
+* Core Class `org.apache.shenyu.plugin.request.RequestPlugin`
+
+## 1.5 Added Since Which shenyu version
+
+* Since ShenYu 2.4.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+- Import maven config in shenyu-bootstrap project's `pom.xml` file, which is already added by default.
+
+```xml
+ 
+
+
+## 2.4 Config plugin
+
+- selectors and rules, only requests that match are forwarded and redirected, see the [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule)
+- `shenyu-admin` Plugin --> `HttpProcess` --> `Request`. Add the selector first, then add the rule：
+- Add the selector:
+
+ 
+
+- Add the rule
+
+ 
+
+## 2.5 Examples
+
+### 2.5.1 Adding request parameters
+
+- When we configure a custom path in `Rules`, it should be a reachable service path.
+- When a request is matched, based on the customized path, the `Apache ShenYu` gateway performs a service hop.
+
+1. Refer to [Local Deployment](https://shenyu.apache.org/docs/deployment/deployment-local)启动 admin 和网关
+2. Refer to 2.2 importing pom and restarting the gateway.
+3. Refer to 2.3 enabling Plugin
+4. Start the project [shenyu-examples-http](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http)
+5. Refer to 2.4 and [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule), configuring plugin rules.
+6. Call interface：[http-test-api.http](https://github.com/apache/shenyu/blob/master/shenyu-examples/shenyu-examples-http/src/main/http/http-test-api.http)
+- Calling the interface declared by the selector and rule will see the request parameters configured in the request plugin.
+
+ 
diff --git a/versioned_docs/version-2.6.1/plugin-center/http-process/rewrite-plugin.md b/versioned_docs/version-2.6.1/plugin-center/http-process/rewrite-plugin.md
new file mode 100644
index 00000000000..adc096f0299
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/http-process/rewrite-plugin.md
@@ -0,0 +1,103 @@
+---
+title: Rewrite Plugin
+keywords: ["rewrite"]
+description: rewrite plugin
+---
+
+# 1. Overview
+
+## 1.1 Plugin Name
+
+* Rewrite Plugin
+
+## 1.2 Appropriate Scenario
+
+* The request uri can be different from the target service by rewriting the path.
+
+## 1.3 Plugin functionality
+
+* This plugin is used to rewrite the request uri.
+
+## 1.4 Plugin code
+
+* Core Module `shenyu-plugin-rewrite`
+
+* Core Class `org.apache.shenyu.plugin.rewrite.RewritePlugin`
+
+## 1.5 Added Since Which shenyu version
+
+* Since ShenYu 2.4.0
+
+# 2. How to use plugin
+
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+- Import maven config in shenyu-bootstrap project's `pom.xml` file..
+
+```xml
+ 
+
+Selector Handler, the `handle` field, is an operation that can be processed by the gateway after matching the traffic. For more information, please refer to [Plugin handle management](../plugin-handle-explanation) in Plugin Config.
+
+* details：
+
+ * `host`：host string.
+
+ * `ip:port`：ip+port string.
+
+ * `protocol`：protocol default is 'http'.
+
+ * `group`：the group of dubbo service.
+
+ * `version`：the version of dubbo service.
+
+ * `weight`：the server instance and participate in load balancing calculation.
+
+ * `warmupTime`：the server's warm up time and and participate in load balancing calculation.
+
+ * `startupTime`：the server's start time.
+
+ * `status`：true: the server is available，false: the server is unavailable.
+
+ * `gray`：enable gray routing.
+
+Gray routing
+
+if you want to user gray route in dubbo-plugin, you can click the `gray` button.
+
+* Gray level publishing can customize and control the traffic proportion of new version applications when publishing new version applications, gradually complete the full launch of new version applications, maximize the business risk caused by new version publishing, reduce the impact surface caused by faults, and support rapid roll back.
+
+when the gray is open,Gateway load balancing will select one node from the current node list for routing and you can modify node weights to change the weight of nodes in the load balancing algorithm.
+It should be noted that,if your business instance not use the client jar of 'shenyu-client-apache-dubbo' or 'shenyu-client-alibaba-dubbo', You should add gray node information manually on this selector page.
+
+#### Rule Handler
+
+
+
+Rule Handler, the `handle` field, can be performed by the gateway after the final matching of traffic. For more information, please refer to [Plugin handle management](../plugin-handle-explanation) in Plugin Config.
+
+* details：
+
+ * `loadbalance`：the loadbalance of dubbo service, if the gray node selection fails, the default load balancing method will be used.
+
+* Apache ShenYu will obtain the real IP of the corresponding service and initiate rpc proxy calls from registration center of dubbo.
+
+
+## Metadata
+
+* Every dubbo interface method corresponds to a piece of metadata, which can be found in `shenyu-admin` --> BasicConfig -> Metadata .
+
+
+
+* AppName: The name of the application to which this piece of metadata belongs.
+
+* MethodName: The name of the method that needs to be called.
+
+* Path: your http request path.
+
+* PathDescribe: Description of the path, for easy viewing.
+
+* ParamsType: List of parameter types of dubbo interface, there are two declaration methods here:
+ e.g. we have an interface `update(Integer id, String name, Integer age)`
+
+ * Type list
+
+ ```yaml
+ java.lang.Integer,java.lang.String,java.lang.Integer
+ ```
+
+ * According to the order of the parameter types of the interface, separated by `,`
+
+ * When requesting to pass parameters, **the parameters must be passed in strictly in accordance with the order of the parameter types**, if a parameter without value use `null` as a placeholder.
+
+ Request body example: `{"id":1,"name": null,"age":18}`
+
+ * Name mapping
+
+ ```yaml
+ {"id":"java.lang.Integer","name":"java.lang.String","age":"java.lang.Integer"}
+ ```
+
+ * Use `"parameter name":"parameter type"` to represent a parameter, set in order of interface parameter type, separated by `,`
+
+ * No need to pay attention to the order when requesting, and no need to use null placeholders.
+
+ Request body example: `{"name":"Mike","id":1}`
+
+* RpcExpand: corresponding to some configurations of dubbo interface; If you want to adjust, please modify here, which support json format like the following fields:
+
+```yaml
+{"timeout":10000,"group":"",version":"","loadbalance":"","retries":1}
+```
+
+* Interface: The fully-qualified name for dubbo interface .
+
+* RpcType: Choose `dubbo` .
+
diff --git a/versioned_docs/version-2.6.1/plugin-center/proxy/grpc-plugin.md b/versioned_docs/version-2.6.1/plugin-center/proxy/grpc-plugin.md
new file mode 100644
index 00000000000..85a298e66c1
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/proxy/grpc-plugin.md
@@ -0,0 +1,81 @@
+---
+title: gRPC Plugin
+keywords: ["grpc-plugin"]
+description: grpc-plugin
+---
+
+
+## Description
+
+* The grpc plugin is a plugin that converts the Http protocol into the grpc protocol.
+
+
+## Plugin Setting
+
+* Add related dependencies and enable plugin, please refer to: [Quick start with gRPC](../../quick-start/quick-start-grpc) .
+
+* `gRPC` client access, please refer to: [gRPC Proxy](../../user-guide/proxy/grpc-proxy.md) .
+
+* New fields and meanings of grpc plugin since `2.4.3`:
+
+ * `threadpool`：There are two types of business thread pools, `cached` and `shared`.
+
+ `cached` is equivalent to the default thread pool officially provided by grpc;
+
+ `shared` thread pool, just as its name, `all proxy plugins` share a `shared` `Thread pool, the advantage of doing this is that it can reduce the number of thread pools, thereby reducing memory and improving resource utilization.
+
+
+## Plugin Detail
+
+
+After the client accesses the `Apache ShenYu` gateway, it will automatically register the selector and rule information. You can see it in PluginList -> rpc proxy -> grpc. For details about the selector and rule configuration, see [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule) .
+
+
+#### Selector Handler
+
+
+
+
+Selector Handler, the `handle` field, is the processing operation that the gateway can perform after matching the traffic.
+
+
+* config details：
+
+ * `ip:port`：enter the ip:port of your real service .
+
+ * `protocol`：indicates the Http protocol. Generally, the value is `http://` or `https://`. If the value is not specified, the default value is `http://` .
+
+ * `weight`：service weight.
+
+ * `status`：open or close.
+
+
+## Metadata
+
+Each `grpc` interface method, will correspond to a metadata, when the `grpc` application client access to the `Apache ShenYu` gateway, will be automatically registered, can be viewed in the `shenyu-admin` background management system of the BasicConfig --> Metadata management.
+
+
+
+
+* AppName: specifies the name of the application to which the metadata belongs.
+
+* MethodName: the name of the method to call.
+
+* Path: http request path.
+
+* PathDescribe: the description of the path is easy to view.
+
+* ParamsType: the parameters are separated by commas (,) in the order of interface parameter types.
+
+* RpcExpand: other configurations of the `grpc` interface, which support the `JSON` format, are as follows:
+
+```json
+{
+ "timeout": 5000,
+ "methodType": "SERVER_STREAMING"
+}
+```
+
+* Interface: The fully qualified class name of the `grpc` interface.
+
+* RpcType：choose `grpc`.
diff --git a/versioned_docs/version-2.6.1/plugin-center/proxy/motan-plugin.md b/versioned_docs/version-2.6.1/plugin-center/proxy/motan-plugin.md
new file mode 100644
index 00000000000..e94e497c266
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/proxy/motan-plugin.md
@@ -0,0 +1,68 @@
+---
+title: Motan Plugin
+keywords: ["motan-plugin"]
+description: motan-plugin
+---
+
+
+## Description
+
+* The motan plugin is a plugin that converts the Http protocol into the motan protocol.
+
+
+## Plugin Setting
+
+* Add related dependencies and enable plugin, please refer to: [Quick start with Motan](../../quick-start/quick-start-motan) .
+
+* `Motan` client access, please refer to: [Motan Proxy](../../user-guide/proxy/motan-proxy.md) .
+
+
+
+## Plugin Detail
+
+After the client accesses the `Apache ShenYu` gateway, it will automatically register the selector and rule information.
+
+You can see it in PluginList -> rpc proxy -> motan. For details about the selector and rule configuration, see [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule) .
+
+## Metadata
+
+Each `motan` interface method, will correspond to a metadata, when the `motan` application client access to the `Apache ShenYu` gateway, will be automatically registered, can be viewed in the `shenyu-admin` background management system of the BasicConfig --> Metadata management.
+
+
+
+
+* AppName: specifies the name of the application to which the metadata belongs.
+
+* MethodName: the name of the method to call.
+
+* Path: http request path.
+
+* PathDescribe: the description of the path is easy to view.
+
+* ParamsType: the parameters are separated by commas (,) in the order of interface parameter types.
+
+* RpcExpand: description of each interface in a `motan` service. For example, here is the interface information for the `motan` service:
+
+
+
+```json
+{
+ "methodInfo": [
+ {
+ "methodName": "hello",
+ "params": [
+ {
+ "left": "java.lang.String",
+ "right": "name"
+ }
+ ]
+ }
+ ],
+ "group": "motan-shenyu-rpc"
+}
+```
+
+
+* Interface: The fully qualified class name of the `motan` interface.
+
+* RpcType：choose `motan`.
diff --git a/versioned_docs/version-2.6.1/plugin-center/proxy/mqtt-plugin.md b/versioned_docs/version-2.6.1/plugin-center/proxy/mqtt-plugin.md
new file mode 100644
index 00000000000..07f49b2f40d
--- /dev/null
+++ b/versioned_docs/version-2.6.1/plugin-center/proxy/mqtt-plugin.md
@@ -0,0 +1,46 @@
+---
+title: Mqtt Plugin
+keywords: ["Mqtt"]
+description: Mqtt access shenyu gateway
+---
+
+## Description
+
+* After the plugin is used, it will give the ability of mqtt.
+
+## Introducing Plugin Support of Mqtt Gateway
+
+* Introducing those dependencies in the pom.xml file of the gateway.
+
+```xml
+
+
+
+Then configure this authentication information
+
+
+
+- AppName：The application name associated with this account, it can can fill in or choose (data comes from the application name configured in the Metadata).
+- TelPhone：Telphone information.
+- AppParams：When the requested context path is the same as the AppName，add this value to the header, the key is `appParam`.
+- UserId：Give the user a name, just as an information record.
+- ExpandInfo：Description of the account.
+- PathAuth：After opening, the account only allows access to the resource path configured below.
+- ResourcePath：Allow access to the resource path, support path matching，e.g. `/order/**` .
+
+After submit, a piece of authentication information is generated, which contains `AppKey` and `AppSecret`, which is the `AK/SK` in the `Sign` plugin.
+
+Please refer to the detailed instructions of the `Sign` plugin： [Sign Plugin](../../plugin-center/authority-and-certification/sign-plugin).
+
+#### 2.4.1.3 PathOperation
+
+For the created authentication information, you can click `PathOperation` at the end of a piece of authentication information.
+
+
+
+- On the left is a list of configurable paths, and on the right is a list of paths that allow the account to access.
+- Check the resource path, click the `>` or `<` in the middle to move the checked data to the corresponding list.
+- In the list of configurable paths on the left, click "Editor" at the end of the account information line, and add them in the "Resource Path" in the pop-up box.
+
+### 2.4.2 Implementation of Gateway Technology
+
+* Adopt `AK/SK` authentication technical scheme.
+* Adopt authentication plug-in and Chain of Responsibility Pattern to realize.
+* Take effect when the authentication plugin is enabled and all interfaces are configured for authentication.
+
+### 2.4.3 Authentication Guide
+
+* Step 1: `AK/SK` is assigned by the gateway. For example, the `AK` assigned to you is: `1TEST123456781` SK is: ` 506eeb535cf740d7a755cb49f4a1536'
+
+* Step 2: Decide the gateway path you want to access, such as `/api/service/abc`
+
+* Step 3: Construct parameters (the following are general parameters)
+
+| Field | Value | Description |
+| -------- | -------- | :--------: |
+| timestamp | current timestamp(String) | The number of milliseconds of the current time（gateway will filter requests the before 5 minutes） |
+| path | /api/service/abc | The path that you want to request(Modify by yourself according to your configuration of gateway) |
+| version | 1.0.0 | `1.0.0` is a fixed string value |
+
+Sort the above three field natually according to the key, then splice fields and fields, finally splice SK. The following is a code example.
+
+#### 2.4.3.1 Generate sign with request header
+
+Step 1: First, construct a Map.
+
+```java
+
+ Map
+
+* Add configuration mode in plugin editing.
+
+```yaml
+{"model":"black"}
+# model can be 'black' or 'mixed'
+# The default mode is blacklist mode; If setting is mixed, it will be mixed mode. We will explain it specifically below.
+```
+
+## Add Dependency
+
+* Introducing `waf` dependency in the pom.xml of the gateway.
+
+```xml
+
+ 
+
+For requests that are denied access by `Waf` , the response header status code is: `403`.
+
+#### Black Model
+
+* When `model` is set to `black` mode, only the matched traffic will execute the rejection policy, and the unmatched traffic will be skipped directly.
+* The `Handler` feild in the rule configuration is invalid and can be configured to be empty.
+
+#### Mixed Model
+
+* When `model` is set to `mixed` mode, all traffic will pass through waf plugin. For different matching traffic, users can set whether to reject or pass.
+
+* The `Handler` feild in the rule configuration must be configured:
+
+ * `permission`: The handle logic that matches the rule. `reject`: deny access, `allow`: allow access.
+
+ * `statusCode`: When access is denied, the value of the code field in the response body. `Will not modify the status code of the response header`.
+
+ e.g.：`statusCode=10001`，The rejected response body is :
+
+ ```json
+ {"code":10001,"message":"You are forbidden to visit"}
+ ```
+
+## Situation
+
+* `Waf` is also the pre-plugin of `ShenYu`, which is mainly used to intercept illegal requests or exception requests and give relevant rejection policies.
+* When faced with replay attacks, you can intercept illegal `ip` and `host`, and set reject strategy according to matched `ip` or `host`.
+* How to determine `ip` and `host`, please refer to: [parsing-ip-and-host](../../developer/custom-parsing-ip-and-host)
diff --git a/versioned_docs/version-2.6.1/quick-start/_category_.json b/versioned_docs/version-2.6.1/quick-start/_category_.json
new file mode 100644
index 00000000000..6b00aae3947
--- /dev/null
+++ b/versioned_docs/version-2.6.1/quick-start/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Quick Start",
+ "position": 4
+}
diff --git a/versioned_docs/version-2.6.1/quick-start/quick-start-dubbo.md b/versioned_docs/version-2.6.1/quick-start/quick-start-dubbo.md
new file mode 100644
index 00000000000..8fd022ffbd2
--- /dev/null
+++ b/versioned_docs/version-2.6.1/quick-start/quick-start-dubbo.md
@@ -0,0 +1,180 @@
+---
+title: Quick start with Dubbo
+description: Quick start with Dubbo
+---
+
+This document introduces how to quickly access the Apache ShenYu gateway using Dubbo. You can get the code example of this document by clicking [here](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-dubbo).
+
+## Environment to prepare
+
+Please refer to the deployment to select a way to start shenyu-admin. For example, start the Apache ShenYu gateway management system through [local deployment](../deployment/deployment-local) .
+
+After successful startup, you need to open the Dubbo plugin on in the BasicConfig `->` Plugin, and set your registry address. Please make sure the registry center is open locally.
+
+
+
+If you are a startup gateway by means of source, can be directly run the ShenyuBootstrapApplication of shenyu-bootstrap module.
+
+> Note: Before starting, make sure the gateway has added dependencies.
+
+
+If client is `apache dubbo`, registry center is `Zookeeper`, please refer to the following configuration:
+
+
+```xml
+
+ 
+
+If you are a startup gateway by means of source, can be directly run the ShenyuBootstrapApplication of shenyu-bootstrap module.
+
+> Note: Before starting, make sure the gateway has added dependencies.
+
+
+Add the following dependencies to the gateway's `pom.xml` file:
+
+```xml
+
+ 
+
+If you are a startup gateway by means of source, can be directly run the ShenyuBootstrapApplication of shenyu-bootstrap module.
+
+> Note: Before starting, make sure the gateway has added dependencies.
+
+
+Add the following dependencies to the gateway's `pom.xml` file:
+
+
+```xml
+
+ 
+
+If you are a startup gateway by means of source, can be directly run the ShenyuBootstrapApplication of shenyu-bootstrap module.
+
+> Note: Before starting, make sure the gateway has added dependencies.
+> Start up zookeeper in local.
+
+Import the gateway proxy plugin for `Motan` and add the following dependencies to the gateway's `pom.xml` file:
+
+
+```xml
+
+ 
+
+Use PostMan to simulate HTTP to request your Motan service:
+
+
+
+If you are a startup gateway by means of source, can be directly run the ShenyuBootstrapApplication of shenyu-bootstrap module.
+
+> Note: Before starting, make sure the gateway has added dependencies.
+
+
+If client is `sofa`, registry center is `Zookeeper`, please refer to the following configuration:
+
+
+
+```xml
+
+ 
+
+If you are a startup gateway by means of source, can be directly run the ShenyuBootstrapApplication of shenyu-bootstrap module.
+
+> Note: Before starting, make sure the gateway has added dependencies.
+
+
+
+`shenyu-bootstrap` need to import tars dependencies:
+
+```xml
+
+
+2. Deploy the `shenyu-bootstrap` service.
+- After starting, `shenyu-bootstrap` will synchronize the data via the `websocket` protocol according to the address configured in `shenyu.sync.websocket.url`.
+
+> Note: Before starting, make sure that the gateway has introduced the relevant dependency, which is introduced by default.
+
+Import the gateway proxy plugin for `Websocket` and add the following dependencies to the gateway's `pom.xml` file.
+
+
+```xml
+
+ 
+
+2. The following test code (see attachment) simulates the request method of the `Websocket` protocol to request your `Websocket` service.
+
+
+
+
+## How to use
+
+The Brief introduce is as follows.
+- Users with administrative user resouce permissions (including the admin user) create a new user.
+- Users with administrative user data resouce permissions (including admin user) click `ConfigureDataPermission` to manage the user's data permissions.
+> Make sure the data exists in the plugin list before doing so. If not, you will have any data to configure.
+
+Now, let's look how to operation step by step:
+
+### Create User
+
+Clicking the menu "System Manage -> User" to create user, like this:
+
+
+### Edit Date
+
+#### Add Plugin Data
+
+Adding data in the plugin list, this article uses `divide` as an example, like:
+
+
+#### Configure Resource Permission
+
+Giving the `divide` plugin permission to the `default` role.
+
+
+The `default` role has none permissions.The user can't login who we set `default` role to. So we must edit the permissions.
+
+#### Configure Data Permission
+
+When we create the common users, we can edit data permissions by the `ConfigureDataPermission` button.
+
+
+
+The datas in this list are the same as the plugin list.
+
+## New User Login
+
+When the user login, he just can see the data given to him.
+
diff --git a/versioned_docs/version-2.6.1/user-guide/admin-usage/dictionary-management.md b/versioned_docs/version-2.6.1/user-guide/admin-usage/dictionary-management.md
new file mode 100644
index 00000000000..91b6989ebcf
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/admin-usage/dictionary-management.md
@@ -0,0 +1,32 @@
+---
+title: Dictionary Management
+keywords: ["dict"]
+description: dict management explanation
+---
+
+## Explanation
+
+This document will introduce the use of dictionary management in the Apache ShenYu background management system. Dictionary management is primarily used to maintain and manage common data dictionaries.
+
+Please refer to the `deployment` document, choose a way to start `shenyu-admin`. For example, [local deployment](../../deployment/deployment-local). After startup, visit `http://localhost:9095`, the default username and password are: `admin` and `123456` .
+
+The current usage scenario is in the [pluginHandle](./plugin-handle-explanation), when the data type is selected as the `dropdown`:
+
+
+
+In dictionary management, you can add dictionary types for other places:
+
+
+
+- DictionaryType: The field name used in the `pluginHandle` .
+- DictionaryCode: Identify dictionary data.
+- DictionaryName: The name of the `handle` field when adding plugins, selectors or rules.
+- DictionaryValue: The actual value of the dictionary data.
+- DictionaryDescribe: Description.
+- Sort: Dictionary data order.
+
+e.g. `degradeRuleGrade` is one of fields of Sentinel's `handle` json. When it adds rules, it automatically looks up all the general dictionaries of `type='degradeRuleGrade'` in the `shenyu_dict` table as a select-box when you edit the General rules field.
+
+
+
+
diff --git a/versioned_docs/version-2.6.1/user-guide/admin-usage/plugin-handle-explanation.md b/versioned_docs/version-2.6.1/user-guide/admin-usage/plugin-handle-explanation.md
new file mode 100644
index 00000000000..82eb4af0c95
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/admin-usage/plugin-handle-explanation.md
@@ -0,0 +1,51 @@
+---
+title: Plugin Config
+keywords: ["plugin"]
+description: plugin handle explanation
+---
+
+## Explanation
+
+This document will introduce the use of plugins in the `shenyu-admin` , including plugin management and plugin handle management.
+
+Please refer to the `deployment` document, choose a way to start `shenyu-admin`. For example, [local deployment](../../deployment/deployment-local). After startup, visit `http://localhost:9095`, the default username and password are: `admin` and `123456` .
+
+## Plugin management
+
+In the plugin management, you can manage all plugins in a unified manner, such as turning off or turning on plugins:
+
+
+
+You can also set configuration information for some plugins, such as setting a registry for `Dubbo` plugin:
+
+
+
+## Plugin handle management
+
+In plugin handle management, you can add `handle` fields to plugin, selector, and rule.
+
+For example, add a string type field `path` and a digital type field `timeout` to the rule list of the `SpringCloud` plugin.
+
+1. add/edit the `handle` field in the `shenyu-admin`-> BasicConfig -> PluginHandle :
+
+
+
+2. Fill in the field information:
+
+
+
+- PluginName: Drop down to select which plugin needs to add the `handle` field.
+- Field: Add the name of the field.
+- Describe: Field description.
+- DataType: Field data type.
+ - If the `DropDown` is selected, the drop-down selection of the input box on the rule addition page is to go to the dictionary table to find all the available options through the field name to select, so you need to config the selection in [Dictionary Management](./dictionary-management).
+- FieldType: This field belongs to selector, rule or plugin.
+- Sort: Sequence number.
+- Required: Is this field required.
+- DefaultValue: Specify a default value for this field.
+- Placeholder: The message that appears when the user fills in the field.
+- Rule (RegExp): The verification rule when the user fills in the field。
+
+3. When adding a rule in the PluginList -> rpc proxy -> `SpringCloud` -> you can enter `path` and `timeout` :
+
+
diff --git a/versioned_docs/version-2.6.1/user-guide/admin-usage/role-management.md b/versioned_docs/version-2.6.1/user-guide/admin-usage/role-management.md
new file mode 100644
index 00000000000..e3fa8f40b0e
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/admin-usage/role-management.md
@@ -0,0 +1,45 @@
+---
+title: Role Management
+keywords: ["user role resource"]
+description: user role resource permission management
+---
+
+This article focuses on the `admin` console to manage `admin` operation permissions through user-associated roles, roles that give permissions to resources such as menus and buttons.
+
+
+## Resource
+
+Add Menus and Buttons Resource in "System Manage >> Resouce".
+
+
+
+The admin user shows all menus and buttons of the `Shenyu` gateway. If you need to customize adding and removing, add the menu first and under the corresponding menu, add the button. Edit the menu by clicking on the small edit icon on the right side of the menu.
+
+
+## Role
+
+You can associate roles and resource permissions through the menu bar "System Administration >> Role Management". By default, two roles are created, one for super administrator and one for normal user. The super administrator is the admin user, which cannot be changed, and the normal user role can change its resource properties. By editing the corresponding role, you can give the role the appropriate menu and button permissions.
+
+
+## User
+
+You can manage the users logged into admin through the menu bar "System Administration >> User Management". The default user is admin, which has all menu and data permissions, cannot be changed or deleted, and can only change password or username.
+You can add a user by pressing the "Add Data" button. The user role is selected to manage the menu and button permissions that the user sees after logging in. When a user selects more than one role, the maximum set of all roles is taken together. After changing a user's role permissions, users who are already logged in can simply refresh the page to get the changed permissions.
+
+The following is an example of how the new user's permissions.
+
+- editor default user role permission
+
+
+
+- Add new roles and give the appropriate resource permissions
+
+
+
+- Create new users and give them the appropriate roles
+
+
+
+- User login to view their menu and button permissions
+
+
diff --git a/versioned_docs/version-2.6.1/user-guide/admin-usage/selector-and-rule.md b/versioned_docs/version-2.6.1/user-guide/admin-usage/selector-and-rule.md
new file mode 100644
index 00000000000..e2ad2e058eb
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/admin-usage/selector-and-rule.md
@@ -0,0 +1,336 @@
+---
+title: Selector And Rule Config
+keywords: ["Selector", "Rule"]
+description: detailed explanation of selector and rule
+---
+
+## Features
+
+This document will introduce the use of selectors and rules in the Apache ShenYu background management system. For the concept and design of selectors and rules, please refer to `Flow Control`.
+
+
+For example, add a selector to the `divide` plugin:
+
+
+
+* selector detailed explanation：
+
+ * Name: create your selector with a distinguish name.
+ * Type: Choose request matching strategy.
+ * `custom`: Only handle requests that meet the following matching conditions.
+ * `full`: Handle all requests.
+ * MatchType: Condition combination type.
+ * `and`： Need to meet all conditions.
+ * `or`: Meet any of the conditions.
+ * Conditions：
+ * uri: filter request with uri.
+ * header: filter request with request header.
+ * query: filter request with query string.
+ * ip: filter request with your real ip.
+ * host: filter request with your real host.
+ * post: not recommend to use.
+ * cookie: filter request with cookie.
+ * req_method: filter request with request method.
+ * condition match:
+ * match : fuzzy string matching，recommend to combine with uri，support path-matching.（/test/**).
+ * = : matches only if they are equal.
+ * regEx : regex matching，match characters in regex expression.
+ * contains: when it contains the specified value, it matches.
+ * TimeBefore: before the specified time.
+ * TimeAfter: after the specified time.
+ * exclude: the inverse of the method of `match`.
+ * startsWith: when its prefix is equal to the specified value, it matches. In certain scenarios, `match` can be replaced (such as `/test/` instead of `/test/**`) for better performance.
+ * endsWith: when its suffix is equal to the specified value, it matches.
+ * pathPattern: it's an optimized version of `match`, which has better performance than `match`, but does not support writing `**` in the middle of the path (such as `/api/**/xxx`).
+ * Continued: whether the subsequent selector is still executed.
+ * PrintLogs: it will print the matching log with the open option enabled.
+ * Enable: whether to enable the plugin.
+ * Order：the smaller will have high priority to execute among multi-selectors.
+ * Handler: The operation when the request matches the selector.
+* the above picture means: when the prefix of the request uri is `/http`, it will redirect to this service `127.0.0.1:8080`.
+* selector advice : combine `uri` condition and `startsWith` prefix（/contextPath/）as the first request filter.
+* selector(the same for rule) match condition fuzzy string matching rule:
+ * `?` matches one character
+ * `*` matches zero or more characters
+ * `**` matches zero or more directories in a path
+
+## Rule
+
+
+
+* when the request was passed by the selector, then it will be processed by the rule, the final filter.
+* rule is the final confirmation about how to execute request logically.
+* rule detailed explanation：
+ * Name：create your rule with a distinguish name.
+
+ * MatchType: you can combine these conditions with 'and' , 'or' operators.
+
+ * Conditions：
+
+ * uri: filter request with uri.
+ * header: filter request with request header.
+ * query: filter request with query string.
+ * ip: filter request with your real ip.
+ * host: filter request with your real host.
+ * post: not recommend to use.
+ * cookie: filter request with cookie.
+ * req_method: filter request with request method.
+
+ * condition match:
+ * match : fuzzy string matching，recommend to combine with uri，support path-matching.（/test/**).
+ * = : matches only if they are equal.
+ * regEx : regex matching，match characters in regex expression.
+ * contains: when it contains the specified value, it matches.
+ * TimeBefore: before the specified time.
+ * TimeAfter: after the specified time.
+ * exclude: Same function as `match`, flow selection is opposite.
+ * startsWith: when its prefix is equal to the specified value, it matches. In certain scenarios, `match` can be replaced (such as `/test/` instead of `/test/**`) for better performance.
+ * endsWith: when its suffix is equal to the specified value, it matches.
+ * pathPattern: it's an optimized version of `match`, which has better performance than `match`, but does not support writing `**` in the middle of the path (such as `/api/**/xxx`).
+
+ * PrintLogs: it will print the matching log with the open option enabled.
+
+ * Enable: whether to enable the plugin.
+
+ * Order：the smaller will have high priority to execute among multi-rules.
+
+ * handle: The operation when the request matches the rule.
+* above picture means: when the request `uri` equals to `/http/order/save`, it will execute based on this rule，load strategy is `random`.
+* rule advice: combine `uri` condition with `match` the real `uri path` condition as the final filter.
+* combine selector means ：when the request `uri` is `/http/order/save`, it will be redicted to `127.0.0.1:8080` by `random` method.
+
+
+## Match Strategy
+
+Matching mode refers to the matching mode between multiple conditions when a selector or rule is matched. Currently, `and` and `or` are supported.
+
+
+* `and`
+
+ `and` indicates that a selector or rule can be matched only if more than one condition is met.
+
+ The example below shows that a request must meet both the condition `uri = /http/order/findById` and the condition `id = 100` to match this rule.
+
+ For example, a real request `http://localhost:9195/http/order/findById?id=100` satisfies both conditions, this rule can be matched.
+
+
+
+
+
+* `or`
+
+ `or` indicates that one of the conditions matches a selector or rule.
+
+ The example below shows that a request matches this rule if it meets either the condition `uri = /http/order/findById` or the condition `id = 100`.
+
+ For example, a real request `http://localhost:9195/http/order/findById?id=99` satisfies the first condition `uri = /http/order/findById`, so it can also match this rule.
+
+
+
+
+
+## Condition Parameter Data
+
+Conditional parameter Settings in selectors and rules are explained again. Suppose the following is a request header for an `Http` request:
+
+```shell
+GET http://localhost:9195/http/order/findById?id=100
+Accept: application/json
+Cookie: shenyu=shenyu_cookie
+MyHeader: custom-header
+```
+
+In `ShenYu` you can set different conditional parameters to get real data from the request information.
+
+- If the condition parameter is `uri`, then the actual data retrieved is `/http/order/findById`;
+- If the condition parameter is `header`, the field name is `MyHeader`, then the actual data retrieved is `custom-header`;
+- If the condition parameter is `query`, the field name is `id`, then the actual data retrieved is `100`;
+- If the condition parameter is `ip`, then the actual data retrieved is `0:0:0:0:0:0:0:1`;
+- If the condition parameter is `host`, then the actual data retrieved is `0:0:0:0:0:0:0:1`;
+- If the condition parameter is `post`, the field name is `contextPath`, then the actual data retrieved is `/http`;
+- If the condition parameter is `cookie`, the field name is `shenyu`, then the actual data retrieved is `shenyu_cookie`;
+- If the condition parameter is `req_method`, then the actual data retrieved is `GET`;
+
+* `uri`(recommended)
+
+ * `uri` matches are based on the `uri` in the path you requested, and there is almost no change in the front end when accessing the gateway.
+
+ * When using `match`, the principle is the same as `SpringMVC` fuzzy matching.
+
+ * In selectors, it is recommended to use prefixes in `URI` for matching, while in rules, specific paths are used for matching.
+
+ * When using this matching method, fill in the value of the matching field, as shown in the figure `/http/**`.
+
+ 
+
+* `header`
+
+ * The `header` is matched against the field values in your `http` request header.
+
+ * When using this matching method, you need to fill in the field name and field value. The examples in the figure are `MyHeader` and `custom-header` respectively
+
+ 
+
+* `query`
+
+ * This matches the query parameters in your `uri`, such as `/test?id=1`, then the matching method can be selected.
+
+ * When using this matching method, you need to fill in the field name and field value. The examples in the figure are `id` and 1 respectively.
+
+ 
+
+* `ip`
+
+ * This is matched against the `http` caller's `ip`.
+
+ * Especially in waf plugin, if an `ip` address is found to be attacked, you can add a matching condition, fill in the `ip`, deny the `ip` access.
+
+ * If you use nginx proxy before ShenYu, you can get the right ip with refering to [parsing-ip-and-host](../../developer/custom-parsing-ip-and-host)
+
+ * When using this matching method, fill in the value of the matching field, as shown in the example `192.168.236.75`.
+
+ 
+
+
+* `host`
+
+ * This is matched against the `http` caller's `host`.
+
+ * Especially in waf plugin, if an `host` address is found to be attacked, you can add a matching condition, fill in the `host`, deny the `host` access.
+
+ * If you use nginx proxy before ShenYu, you can get the right ip with refering to [parsing-ip-and-host](../../developer/custom-parsing-ip-and-host)
+
+ * When using this matching method, fill in the value of the matching field, as shown in the example `localhost`.
+
+ 
+
+* `post`
+
+ * To get condition parameters from the request context(`org.apache.shenyu.plugin.api.context.ShenyuContext`), reflection is required to get the value of the field, which is not recommended.
+
+ * When using this matching method, the field name and value need to be specified. The examples in the figure are `contextPath` and `/http` respectively.
+
+ 
+
+
+* `cookie`
+
+ * This is matched against the `Cookie` in the `http` caller's request header as a condition parameter.
+
+ * When using this matching method, you need to fill in the field name and field value. The examples in the figure are `shenyu` and `shenyu_cookie` respectively.
+
+ 
+
+* `req_method`
+
+ * This matches the request form of the `http` caller, such as `GET`, `POST`, etc.
+
+ * When using this matching method, fill in the value of the matching field, as shown in the example `GET`.
+
+ 
+
+For a more in-depth understanding of condition parameter fetching, read the source code, package name is `org.apache.shenyu.plugin.base.condition.data`:
+
+|Condition Parameter | Class |
+|:------------------------ |:----- |
+|`uri` |`URIParameterData` |
+|`header` |`HeaderParameterData` |
+|`query` |`QueryParameterData` |
+|`ip` |`IpParameterData` |
+|`host` |`HostParameterData` |
+|`post` |`PostParameterData` |
+|`cookie` |`CookieParameterData` |
+|`req_method` |`RequestMethodParameterData` |
+
+
+## Condition Match Strategy
+
+Condition parameters allow you to retrieve the actual data of the request. How the real data matches the conditional data preset by the selector or rule is realized through the condition match strategy.
+
+
+* `match`
+
+ `match` supports fuzzy matching (`/**`). Request `/http/order/findById` will match if your selector condition is set as follows.
+
+ 
+
+* `=`
+
+ `=` means that the requested real data is equal to the preset condition data. If your selector condition is set to request uri equal to `/http/order/findById`, then request`/http/order/findById?id=1` can match it.
+
+ 
+
+* `regex`
+
+ `regex` means that the requested real data can meet the preset condition of the regular expression to match successfully. Suppose your rule conditions are sets as follows: the request parameter contains an `id` and is a three-digit number. So request `/http/order/findById?id=900` will match.
+
+ 
+
+* `contains`
+
+ `contains` means that the requested real data contains the default condition data. Suppose your rule condition is set as follows: request uri contains `findById`. Request `/http/order/findById?id=1` will match.
+
+ 
+
+* `TimeBefore`
+
+ `TimeBefore` indicates that the request time will be matched before the preset condition time. Suppose your rule conditions are sets as follows: request parameters contain `date` and `date` is less than `2021-09-26 06:12:10`. Request `/http/order/findById?id=100&date=2021-09-22 06:12:10` will match.
+
+ 
+
+* `TimeAfter`
+
+ `TimeAfter` indicates that the request time will be matched before the preset condition time. Suppose your rule conditions are sets as follows: request parameters contain `date` and `date` is greater than `2021-09-26 06:12:10`. Request `/http/order/findById?id=100&date=2021-09-22 06:12:10` will match.
+
+ 
+
+* `exclude`
+
+ `exclude` is the inverse of the method of `match`, and some functions of `match` are also available, but it is a matching filter. If your selector condition is set as follows, the request `/http/order/findById` will filter this.
+
+ 
+
+* `startsWith`
+
+ `startsWith` indicates that the prefix of the requested real data is equal to the preset condition data. Suppose your rule conditions are sets as follows: the prefix in the request `uri` is equal to `/http/`, the request `/http/order/findById?id=1` can be matched.
+
+ 
+
+* `endsWith`
+
+ `endsWith` indicates that the suffix of the requested real data is equal to the preset condition data. Suppose your rule conditions are sets as follows: request `uri` suffix equals `Id`. Then the request `/http/order/findById?id=1` can be matched.
+
+ 
+
+* `pathPattern`
+
+ Like `match`, `pathPattern` supports fuzzy matching (`/**`). If your rule conditions are sets as follows, then the request `/http/order/findById` can be matched;
+
+ Notice: writing `**` in the middle of the path (such as `/api/**/xxx`) is not supported!
+
+ 
+
+If you want to further understand conditions matching strategy, please read the source code, the package name is `org.apache.shenyu.plugin.base.condition.judge`:
+
+| Match Strategy | Class |
+|:---------------|:----- |
+| `match` |`MatchPredicateJudge` |
+| `=` |`EqualsPredicateJudge` |
+| `regex` |`RegexPredicateJudge` |
+| `contains` |`ContainsPredicateJudge` |
+| `TimeBefore` |`TimerBeforePredicateJudge` |
+| `TimeAfter` |`TimerAfterPredicateJudge` |
+| `exclude` |`ExcludePredicateJudge` |
+| `startsWith` |`StartsWithPredicateJudge` |
+| `endsWith` |`EndsWithPredicateJudge` |
+| `pathPattern` |`PathPatternPredicateJudge` |
+
+The examples in this article illustrate the use of selectors and rules. The Settings of specific conditions need to be selected according to actual conditions.
diff --git a/versioned_docs/version-2.6.1/user-guide/api-doc/_category_.json b/versioned_docs/version-2.6.1/user-guide/api-doc/_category_.json
new file mode 100644
index 00000000000..ae4f3bab406
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/api-doc/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "API Document Aggregation",
+ "position": 6
+}
diff --git a/versioned_docs/version-2.6.1/user-guide/api-doc/shenyu-annotation-apidoc.md b/versioned_docs/version-2.6.1/user-guide/api-doc/shenyu-annotation-apidoc.md
new file mode 100644
index 00000000000..5343291aa1f
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/api-doc/shenyu-annotation-apidoc.md
@@ -0,0 +1,38 @@
+---
+title: The client registers the API documentation
+keywords: ["api doc register"]
+description: The client registers the API documentation
+---
+
+This article describes how to expose the `API documentation` to the `Apache ShenYu` gateway.
+
+Before accessing, please start `shenyu-admin` correctly.
+
+## Export API Documentation to shenyu-admin
+
+You can refer to any of the example codes below [shenyu-examples](https://github.com/apache/shenyu/tree/master/shenyu-examples).
+
+The only thing you need to do is to add `@ApiModule` and `@ApiDoc` annotations to your service, here is an example from `shenyu-examples-http`:
+
+```java
+@RestController
+@RequestMapping("/order")
+@ShenyuSpringMvcClient("/order")
+@ApiModule(value = "order")
+public class OrderController {
+
+ @GetMapping("/findById")
+ @ShenyuSpringMvcClient("/findById")
+ @ApiDoc(desc = "findById")
+ public OrderDTO findById(@RequestParam("id") final String id) {
+ return build(id, "hello world findById");
+ }
+
+ private OrderDTO build(final String id, final String name) {
+ OrderDTO orderDTO = new OrderDTO();
+ orderDTO.setId(id);
+ orderDTO.setName(name);
+ return orderDTO;
+ }
+}
+```
diff --git a/versioned_docs/version-2.6.1/user-guide/api-doc/swagger-apidoc.md b/versioned_docs/version-2.6.1/user-guide/api-doc/swagger-apidoc.md
new file mode 100644
index 00000000000..2c9d17a0efb
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/api-doc/swagger-apidoc.md
@@ -0,0 +1,57 @@
+---
+title: Pull the swagger registration API document
+keywords: ["swagger api Interface Document Aggregation"]
+description: Remotely pull swagger registration API documentation
+---
+
+This article introduces how to aggregate the `Swagger API documentation` of each backend microservice to the `Apache ShenYu` gateway management system.
+
+## 1. Description
+
+Remotely pull swagger documents, currently only supports swagger2.0, and only supports Divide and SpringCloud proxy plug-ins.
+
+## 2. Environment Preparation
+
+### 2.1 Run `shenyu-admin`
+
+Please refer to the `deployment` document, choose a way to run `shenyu-admin`.
+
+### 2.2 Enable the global switch for remotely pulling swagger documents.
+
+It is enabled by default. In the `Apache ShenYu` gateway management system --> BasicConfig --> Dictionary, find the data whose DictionaryType is `apidoc`, and modify the dictionary value: `true`.
+> 【Notice】DictionaryValue: `true` means the switch is on, `false` means it is off. If it is closed, `shenyu-admin` will not automatically pull the swagger documents of each microservice.
+
+
+
+## 3. Run the Sample Project
+
+3.1. Download [shenyu-examples-http-swagger2](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http-swagger2)
+
+3.2. Run `org.apache.shenyu.examples.http.ShenyuTestSwaggerApplication` main method to start the project.
+
+The examples project will synchronize the service startup information to `shenyu-admin` through the Shenyu client annotation (such as `@ShenyuSpringMvcClient`) according to the address configured by `shenyu.register.serverLists`, and then trigger `shenyu-admin` to remotely pull the swagger document And complete the analysis, and finally aggregate to produce a new API document.
+
+## 4. Demonstration Effect
+
+### 4.1 List of API Documents
+
+In `Apache ShenYu` Gateway Management System --> Document --> API Document, you can see the aggregated API documents.
+
+
+
+### 4.2 API Details Effect
+
+
+
+## 5. How to Automatically Update API Documentation
+
+### 5.1 Restart Project
+
+As in the example above, an automatic update of the API docs is triggered by starting the project.
+
+### 5.2 Modify the startup time of the proxy plugin selector.
+
+In the PlugiList --> Proxy --> selector, find the target service, and then modify the startup time.
+> Note: The startup time of the new setting must not be earlier than the original startup time, otherwise the API document will not be automatically pulled and refreshed.
+
+
diff --git a/versioned_docs/version-2.6.1/user-guide/discovery/_category_.json b/versioned_docs/version-2.6.1/user-guide/discovery/_category_.json
new file mode 100644
index 00000000000..7c0997e003e
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/discovery/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "Discovery",
+ "position": 4
+}
diff --git a/versioned_docs/version-2.6.1/user-guide/discovery/discovery-mode.md b/versioned_docs/version-2.6.1/user-guide/discovery/discovery-mode.md
new file mode 100644
index 00000000000..80837a074b5
--- /dev/null
+++ b/versioned_docs/version-2.6.1/user-guide/discovery/discovery-mode.md
@@ -0,0 +1,422 @@
+---
+title: Discovery
+keywords: [ "Discovery" ]
+description: Discovery
+---
+
+# Discovery
+
+## 1. Overview
+
+### 1.1 Module Name
+
+Discovery
+
+### 1.2 Design
+
+- Module Design Diagram
+
+
+
+
+
+- Database Design
+
+
+
+
+### 1.3 Module Functionality
+
+The Discovery module endows the ShenYu Gateway with the ability to actively perceive and respond to changes in the list of services being proxied.
+By actively listening to the admin service of the Discovery Gateway, the ShenYu Gateway can promptly track changes in the services being proxied.
+This functionality is designed to be flexible and can be configured at either **the selector level or the plugin level**, as needed.
+Currently, plugins that have incorporated the Discovery feature include TCP, Divide, Websocket and gRPC plugins.
+
+
+### 1.4 Listening Mode
+
+LOCAL, ZOOKEEPER, NACOS, EUREKA, ETCD
+
+- LOCAL Mode: Primarily relies on manual maintenance of the upstream list and pushing it to the gateway.
+- ZOOKEEPER Mode: Monitors changes in ephemeral nodes under a specified node in ZooKeeper to obtain data.
+- NACOS Mode: Listens for changes in instances under a specified service name in Nacos to obtain data.
+- EUREKA Mode: Listens for changes in instances under a specified service name in Eureka to obtain data.
+- ETCD Mode: Obtains data by monitoring changes in key-value pairs under specified nodes in etcd.
+
+### 1.5 Scope of Effect
+
+- Plugin Level: Impacts the entire plugin,
+and all selectors under that plugin will default to the current listening mode.
+- Selector Level: Applies to the current selector,
+allowing different selectors under the same plugin to use different listening modes.
+
+## 2. Usage
+
+### 2.1 Plugin-Level Configuration
+
+#### 2.1.1 Service Discovery Configuration
+
+- In plugins that support the Discovery module (currently, only the TCP plugin supports plugin-level discovery
+configuration on the admin console page; other plugins can configure plugin-level discovery through shenyu-client,
+as described in the "Using Shenyu-client" section below), click on `Discovery Configuration`. In the popup form,
+select the desired listening mode and fill in the service discovery name, registration server URL, registry configuration parameters, etc.:
+
+
+
+
+
+
+#### 2.1.2 Usage within Selectors
+
+- To add a new selector, click on `Add Selector`. In the new selector page, you will notice that the `Type` field enforces the previously configured plugin-level listening mode,
+indicating that the added selector will also adopt the same configuration.
+At this point, simply input the desired `ListeningNode`:
+
+ 
+
+- The `Handler` here refers to ShenYu's specified JSON format for transmitting upstream registration data,
+as shown below:
+ - url: URL of the upstream
+ - protocol: communication protocol of the upstream
+ - status: status of the upstream node (0 for healthy, 1 for unhealthy)
+ - weight: Used for load balancing calculations
+
+
+ ```json
+ {
+ "url": "127.0.0.1::6379",
+ "protocol": "tcp",
+ "status": 0,
+ "weight": 10
+ }
+ ```
+
+- If your service alias does not match ShenYu's defined JSON format,
+you can perform alias mapping in `Handler`.
+For example, as shown in the above image,
+if you need to change `status` to "healthy" while keeping other keys unchanged,
+follow these steps: create a new alias, map `status` to `healthy`,
+and retain the original JSON keys' format.
+- Configure the remaining properties for the selector according to the specific plugin's documentation.
+
+### 2.2 Selector-Level Configuration
+
+- In plugins that support the Discovery module, click on `Add Selector`.
+In the `Discovery Config` tab, configure the fields such as type,
+listening node, server URL list, and registry properties.
+This configuration only applies to the current selector and must be reconfigured each time a new selector is added.
+
+
+
+- For the Divide, gRPC, and Websocket plugins,
+the `Import Background Discovery Config` function on the selector creation page
+allows you to import and use the backend configuration if the service connecting to the ShenYu Gateway
+was configured with shenyu-discovery-related properties (see usage with shenyu-client).
+As shown in the following image, click `Import Background Discovery Config` to view the backend configuration:
+
+
+
+- If you confirm the import, clicking the `Import` button in the backend configuration popup will automatically populate the form with the backend service discovery properties.
+At this point, you only need to configure the listening node:
+
+
+
+> **Note**: If you confirm importing the backend configuration,
+the backend service discovery properties will be automatically filled in the form and will continue to use the previous discovery object.
+In this case, modifying service discovery properties in the form will be ineffective, and the backend configuration will be retained.
+
+- If you choose the LOCAL mode, there is no need to connect to a registry, and users must manually maintain the upstream list.
+
+
+## 3. Configuration in Different Modes
+
+### 3.1 Local Mode
+
+- Local mode only supports configuration at the **selector level**.
+There is no need to connect to a registry, and users must manually maintain the upstream list.
+This list is an editable table. Click the `Edit` button for each row in the table to modify each parameter of the upstream:
+
+
+
+### 3.2 ZooKeeper/Nacos/Eureka/Etcd Modes
+
+- In the ZooKeeper/Nacos/Eureka/Etcd modes, service discovery configuration is supported at both the plugin level and the selector level.
+- For each registry property under these modes, taking ZooKeeper as an example, users can go to `shenyu-admin` --> `BasicConfig` --> `Dictionary`,
+search for the dictionary name "zookeeper", and edit the dictionary values corresponding to the default properties
+(**Note**: You cannot modify the dictionary type and dictionary name).
+- In these modes, the gateway dynamically retrieves service instance information from the registry. Additions, removals, modifications,
+and other changes to service instances will be displayed in real-time in the upstream list.
+
+
+
+## 4. Using Shenyu-client
+
+### 4.1 Introduction
+
+- To use Shenyu-client, you need to depend on the corresponding mode's registry middleware: ZooKeeper, Nacos, Etcd, Eureka.
+These modes can automatically detect service up and down events through ShenYu Admin.
+- Additionally, if you are using the local mode, you will need to manually maintain the upstream list.
+- For detailed instructions on using Shenyu-client, refer to the Shenyu-client module documentation.
+
+### 4.2 Local Mode Example
+
+#### 4.2.1 Using Shenyu-client
+
+- Shenyu-client defaults to the Local mode, so there is no need for any special discovery configuration.
+It will automatically register the current service.
+- For services that are automatically registered, you can manually add, modify,
+or delete them in the upstream list on the page:
+
+
+
+#### 4.2.2 Without Using Shenyu-client
+
+
+- If you are not using Shenyu-client, you can manually add, modify,
+or delete service information on the `Discovery Config` tab under `Add Selector`:
+
+
+
+- Configure other selector information:
+
+
+
+- Configure rules:
+
+
+
+- Test Connection
+
+```text
+curl http://localhost:9195/http/hello
+
+hello! I'm Shenyu-Gateway System. Welcome!%
+```
+
+### 4.2 Zookeeper Mode Example
+
+(Taking the Divide plugin as an example)
+
+- Add Dependencies
+
+```xml
+
+
+
+### Http Registry Config
+
+#### shenyu-admin config
+
+Set the register type to '`Http` in the `yml` file. The configuration information is as follows:
+
+```yaml
+shenyu:
+ register:
+ registerType: http
+ props:
+ checked: true # is checked
+ zombieCheckTimes: 5 # how many times does it fail to detect the service
+ scheduledTime: 10 # timed detection interval time
+```
+
+
+
+
+For details about the data synchronization principles, see [Data Synchronization Design](../../design/data-sync) in the design document.
+
+### WebSocket Synchronization Config（default strategy, recommend）
+
+* `Apache ShenYu` gateway config
+
+ Add these dependencies in `pom.xml`：
+
+```xml
+
+