Rate Limit Service (RLS)

service.ratelimit.v2.RateLimitRequest

[service.ratelimit.v2.RateLimitRequest proto]

Main message for a rate limit request. The rate limit service is designed to be fully generic in the sense that it can operate on arbitrary hierarchical key/value pairs. The loaded configuration will parse the request and find the most specific limit to apply. In addition, a RateLimitRequest can contain multiple “descriptors” to limit on. When multiple descriptors are provided, the server will limit on ALL of them and return an OVER_LIMIT response if any of them are over limit. This enables more complex application level rate limiting scenarios if desired.

{
  "domain": "...",
  "descriptors": [],
  "hits_addend": "..."
}
domain

(string) All rate limit requests must specify a domain. This enables the configuration to be per application without fear of overlap. E.g., “envoy”.

descriptors

(ratelimit.RateLimitDescriptor) All rate limit requests must specify at least one RateLimitDescriptor. Each descriptor is processed by the service (see below). If any of the descriptors are over limit, the entire request is considered to be over limit.

hits_addend

(uint32) Rate limit requests can optionally specify the number of hits a request adds to the matched limit. If the value is not set in the message, a request increases the matched limit by 1.

service.ratelimit.v2.RateLimitResponse

[service.ratelimit.v2.RateLimitResponse proto]

A response from a ShouldRateLimit call.

{
  "overall_code": "...",
  "statuses": [],
  "headers": []
}
overall_code

(service.ratelimit.v2.RateLimitResponse.Code) The overall response code which takes into account all of the descriptors that were passed in the RateLimitRequest message.

statuses

(service.ratelimit.v2.RateLimitResponse.DescriptorStatus) A list of DescriptorStatus messages which matches the length of the descriptor list passed in the RateLimitRequest. This can be used by the caller to determine which individual descriptors failed and/or what the currently configured limits are for all of them.

headers

(core.HeaderValue) A list of headers to add to the response

service.ratelimit.v2.RateLimitResponse.RateLimit

[service.ratelimit.v2.RateLimitResponse.RateLimit proto]

Defines an actual rate limit in terms of requests per unit of time and the unit itself.

{
  "requests_per_unit": "...",
  "unit": "..."
}
requests_per_unit

(uint32) The number of requests per unit of time.

unit

(service.ratelimit.v2.RateLimitResponse.RateLimit.Unit) The unit of time.

Enum service.ratelimit.v2.RateLimitResponse.RateLimit.Unit

[service.ratelimit.v2.RateLimitResponse.RateLimit.Unit proto]

UNKNOWN

(DEFAULT) ⁣The time unit is not known.

SECOND

⁣The time unit representing a second.

MINUTE

⁣The time unit representing a minute.

HOUR

⁣The time unit representing an hour.

DAY

⁣The time unit representing a day.

service.ratelimit.v2.RateLimitResponse.DescriptorStatus

[service.ratelimit.v2.RateLimitResponse.DescriptorStatus proto]

{
  "code": "...",
  "current_limit": "{...}",
  "limit_remaining": "..."
}
code

(service.ratelimit.v2.RateLimitResponse.Code) The response code for an individual descriptor.

current_limit

(service.ratelimit.v2.RateLimitResponse.RateLimit) The current limit as configured by the server. Useful for debugging, etc.

limit_remaining

(uint32) The limit remaining in the current time unit.

Enum service.ratelimit.v2.RateLimitResponse.Code

[service.ratelimit.v2.RateLimitResponse.Code proto]

UNKNOWN

(DEFAULT) ⁣The response code is not known.

OK

⁣The response code to notify that the number of requests are under limit.

OVER_LIMIT

⁣The response code to notify that the number of requests are over limit.