envoyproxy/envoy

How to log which rate limit rule was triggered via descriptor?

Open

#41.339 geöffnet am 2. Okt. 2025

Auf GitHub ansehen
 (7 Kommentare) (1 Reaktion) (0 zugewiesene Personen)C++ (5.373 Forks)batch import
area/ratelimitenhancementhelp wanted

Repository-Metriken

Stars
 (27.997 Stars)
PR-Merge-Metriken
 (Durchschn. Merge 8T) (378 gemergte PRs in 30 T)

Beschreibung

Title: Is there an easy way to log which rate limit rule was triggered via descriptor?

Description: I can't seem to find how to log which specific rate limit rule was triggered and blocked/overlimit. The Rate Limit Response has a statuses field, which is a list of DescriptorStatus messages. This information doesn't seem to be logged anywhere, more specifically the descriptor status code.

Link to the Rate Limit Response docs: https://www.envoyproxy.io/docs/envoy/latest/api-v3/service/ratelimit/v3/rls.proto#service-ratelimit-v3-ratelimitresponse-descriptorstatus

https://www.envoyproxy.io/docs/envoy/latest/api-v3/service/ratelimit/v3/rls.proto#service-ratelimit-v3-ratelimitresponse

Contributor Guide