envoyproxy/envoy

support decoding gRPC messages with tap filter

Open

#9,695 opened on Jan 16, 2020

View on GitHub
 (1 comment) (0 reactions) (1 assignee)C++ (5,373 forks)batch import
area/tapenhancementhelp wanted

Repository metrics

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

Description

By being given access to the proto descriptor the HTTP tap filter should be able to output gRPC message bodies as human readable (i.e. as JSON).

Note the overlap with https://github.com/envoyproxy/envoy/issues/6109: both issues would rely on the proto descriptors being made available to Envoy (either statically or dynamically somehow), but this issue tracks being able to support a gRPC specific output format rather than the ability to match on message fields.

Contributor guide

Research direction
Investigate the tap filter's current handling of gRPC streams and plan integration of proto descriptors to decode messages into JSON format.
Tech stack
cppgrpc
Domain
backendinfrastructure
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
C++gRPCProtobufEnvoy filter internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25