envoyproxy/envoy

Allow fine-grain logging to be configurable via CLI arguments

Open

#41,028 opened on Sep 9, 2025

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

Repository metrics

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

Description

Title: Allow fine-grain logging to be configurable via CLI arguments

Description:

As discussed in Slack, it's currently not possible to change the fine-grain logging using CLI arguments. Currently it can only be configured via an admin endpoint. This is inconvenient because when deploying on Kubernetes, I can't easily configure the fine-grain logging building a container of my own. It's difficult (or at the very best a hack like a postStart with a sleep) to do it with a plain envoy image.

Suggestion: The suggestion given in Slack that @paul-r-gall and @botengyao seemed to prefer was the following:

Rather than having --enable-fine-grain-logging it would take configuration similar to --component-log-level, so something like --fine-grain-log-level(s) <string>.

Contributor guide

Research direction
Examine existing CLI argument parsing for component log level and implement similar parsing for fine grain log level. Ensure backward compatibility with admin endpoint.
Tech stack
cpp
Domain
backendcli
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.
1-2 days
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
GitC++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60