Enterprise only. The global rate limit functionality enables a Redis database store to centralize all KrakenD node counters. Instead of having each KrakenD node count its hits, the counters are global and stored in the database. See: https://www.krakend.io/docs/enterprise/endpoints/global-rate-limit/
Get JSON SchemaBundleIdentifier | https://schemas.sourcemeta.com/krakend/v2.2/plugin/redis-ratelimit.json |
---|---|
Base Dialect | Draft7 |
Dialect | http://json-schema.org/draft-07/schema# |
Size | 0.002341 MB |
{
"$schema": "http://json-schema.org/draft-07/schema#",
"$id": "https://schemas.sourcemeta.com/krakend/v2.2/plugin/redis-ratelimit.json",
"title": "Redis ratelimit",
"description": "Enterprise only. The global rate limit functionality enables a Redis database store to centralize all KrakenD node counters. Instead of having each KrakenD node count its hits, the counters are global and stored in the database.\n\nSee: https://www.krakend.io/docs/enterprise/endpoints/global-rate-limit/",
"type": "object",
"required": [ "host", "tokenizer", "burst", "rate", "period" ],
"properties": {
"burst": {
"title": "Burst",
"description": "How many requests a client can make above the rate specified during a peak.\n\nSee: https://www.krakend.io/docs/enterprise/endpoints/global-rate-limit/",
"type": "integer"
},
"host": {
"title": "Redis host",
"description": "The URL to the Redis instance that stores the counters using the format `host:port`.\n\nSee: https://www.krakend.io/docs/enterprise/endpoints/global-rate-limit/",
"examples": [ "redis", "redis:6379" ],
"type": "string"
},
"period": {
...
See the full schema