envoyproxy/envoy

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

Open

#41,339 opened on Oct 2, 2025

View on GitHub
 (7 comments) (1 reaction) (0 assignees)C++ (5,373 forks)batch import
area/ratelimitenhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

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

Research direction
Look into the RateLimitResponse and DescriptorStatus in the rate limit filter, and trace how the status is handled after the rate limit service returns. Implement logging for each descriptor status in the rate limit filter's response handling.
Tech stack
cpp
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50