envoyproxy/envoy

Add an OTLP (gRPC) logger to Envoy

Open

#13,801 opened on Oct 28, 2020

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

Repository metrics

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

Description

Adding the OTLP logger will allow integration with more 3rd party monitoring frameworks, especially when using OT collector to convert them to whichever format needed.

Although OpenTelemetry logging isn't going to be part of the GA and the C++ SDK isn't ready yet, we don't actually need them in order to export OTLP logs - as long as the OTLP logs proto is stable. The logs format is actually already available in the Amazon managed OT collector as an exporter, and Microsoft are also working on something similar, so it shouldn't change much - either way we'll get the OT community guarantee for backwards compatibility.

The general idea is to take the existing gRPC logger and just output a different format.

FYI @htuch @yanavlasov

Contributor guide

Research direction
Study the existing gRPC logger implementation in Envoy, then adapt it to output OTLP logs using the OTLP logs proto 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.
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++gRPCOpenTelemetry
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35