seninel部署
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
Eric Zhao a0196b6b00 Bump version to 1.8.0-SNAPSHOT il y a 4 ans
..
src Polish code and demo of Sentinel Zuul 2.x adapter il y a 4 ans
README.md Polish code and demo of Sentinel Zuul 2.x adapter il y a 4 ans
pom.xml Bump version to 1.8.0-SNAPSHOT il y a 4 ans

README.md

Sentinel Zuul 2.x Adapter

This adapter provides route level and customized API level flow control for Zuul 2.x API Gateway.

Note: this adapter only supports Zuul 2.x.

How to use

You can refer to demo sentinel-demo-zuul2-gateway.

  1. Add Maven dependency to your pom.xml:
<dependency>
    <groupId>com.alibaba.csp</groupId>
    <artifactId>sentinel-zuul2-adapter</artifactId>
    <version>x.y.z</version>
</dependency>
  1. Register filters
filterMultibinder.addBinding().toInstance(new SentinelZuulInboundFilter(500));
filterMultibinder.addBinding().toInstance(new SentinelZuulOutboundFilter(500));
filterMultibinder.addBinding().toInstance(new SentinelZuulEndpoint());

How it works

As Zuul 2.x is based on Netty, an event-driven asynchronous model, so we use AsyncEntry.

  • SentinelZuulInboundFilter: This inbound filter will regard all routes (routeVIP in SessionContext by default) and all customized API as resources. When a BlockException caught, the filter will set endpoint to find a fallback to execute.
  • SentinelZuulOutboundFilter: When the response has no exception caught, the post filter will trace the exception and complete the entries.
  • SentinelZuulEndpoint: When an exception is caught, the filter will find a fallback to execute.

Integration with Sentinel Dashboard

  1. Start Sentinel Dashboard.
  2. You can configure the rules in Sentinel dashboard or via dynamic rule configuration.

You may need to add -Dcsp.sentinel.app.type=1 property to mark this application as API gateway.

Fallbacks

You can implement ZuulBlockFallbackProvider to define your own fallback provider when Sentinel BlockException is thrown. The default fallback provider is DefaultBlockFallbackProvider.

By default fallback route is proxy ID (or customized API name).

Here is an example:


// custom provider
public class MyBlockFallbackProvider implements ZuulBlockFallbackProvider {

    private Logger logger = LoggerFactory.getLogger(DefaultBlockFallbackProvider.class);

    // you can define root as service level
    @Override
    public String getRoute() {
        return "my-route";
    }

    @Override
        public BlockResponse fallbackResponse(String route, Throwable cause) {
            RecordLog.info(String.format("[Sentinel DefaultBlockFallbackProvider] Run fallback route: %s", route));
            if (cause instanceof BlockException) {
                return new BlockResponse(429, "Sentinel block exception", route);
            } else {
                return new BlockResponse(500, "System Error", route);
            }
        }
 }

 // register fallback
 ZuulBlockFallbackManager.registerProvider(new MyBlockFallbackProvider());

Default block response:

{
    "code":429,
    "message":"Sentinel block exception",
    "route":"/"
}