harpunius
harpunius
*Title*: Support multiples of units for rate limits *Description*: We want to be able to specify rate limit intervals more flexibly than per-minute or per-second, for example per 30 seconds...
Implements the unit multiplier idea suggested in https://github.com/envoyproxy/ratelimit/issues/190. ```yaml rate_limit: unit: requests_per_unit: unit_multiplier: ``` I chose to force unit multiplier to 1 if the value is unset to avoid if/else...
We migrated from statsD to the prometheus sink and use the following mapper snippet to monitor our infrastructure: ```yaml - match: "ratelimit_server.*.response_time" name: "ratelimit_service_response_time_seconds" timer_type: histogram labels: grpc_method: "$1" ```...
I recently migrated from statsd-exporter to the prometheus sink, and couldn't make the mapping work, until I found that the path didn't match up. This error is not logged currently,...
When trying to switch to the new prometheus sink instead of a custom statsd-exporter, the pod crashed since `USE_STATSD` defaults to true and I hit the below error: https://github.com/envoyproxy/ratelimit/blob/28b1629a21e885bdd2b527d6a1c1de8483dc47d4/src/service_cmd/runner/runner.go#L65-L68. This...