Skip to content

gRPC C++: Limited options for displaying headers in logs, GRPC_TRACE=api is too verbose #15063

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
eliekozah opened this issue Apr 4, 2025 · 0 comments
Assignees
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: cleanup An internal cleanup or hygiene concern.

Comments

@eliekozah
Copy link
Contributor

The GRPC_TRACE environment variable is used to enable detailed logging for various gRPC components. While GRPC_TRACE=api successfully displays request and response headers in the output, using other combinations, such as GRPC_TRACE=http, does not show these headers. GRPC_TRACE=api, while displaying headers, results in an extremely verbose output (thousands of lines) regardless of the GRPC_VERBOSITY level (INFO or DEBUG).

Proposed solution:
Implement a lightweight interceptor mechanism in the gRPC C++ SDK that customers can utilize. This interceptor would allow users to capture and view request and response headers without enabling overly verbose logging.

@eliekozah eliekozah added type: cleanup An internal cleanup or hygiene concern. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Apr 4, 2025
@eliekozah eliekozah self-assigned this Apr 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: cleanup An internal cleanup or hygiene concern.
Projects
None yet
Development

No branches or pull requests

1 participant