envoyproxy/envoy

logging: gRPC status should be extracted from stream_info

Open

#10,296 opened on Mar 7, 2020

View on GitHub
 (4 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/grpcenhancementhelp wanted

Repository metrics

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

Description

It seems that we can't extract grpc-status from stream_info directly now. Any other status-related info (e.g. response code) can extract from it but that not. I think that is should be extracted from that information pack. Do you think about it?

Contributor guide

Research direction
Examine how other status related information (e.g., response code) is extracted from stream info in the codebase. Then implement a similar extraction for grpc status. Look at the relevant files and follow the pattern.
Tech stack
cpp
Domain
backendnetworking
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-3 hours
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++gRPC
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60