envoyproxy/envoy

Support to track the timestamps at a per-filter basis

Open

#4,547 opened on Sep 27, 2018

View on GitHub
 (8 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
enhancementhelp wanted

Repository metrics

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

Description

Issue Template

Title: Support to track the timestamps at a per-filter basis, including plugin filters

Description: Envoy does not record the timestamps at each filter level. It will be very helpful to debug the request latency bottleneck if we know following information at each filter: the request arrival time, request departure time, response arrival time and response departure time.

Contributor guide

Research direction
Understand the Envoy filter chain and where timestamps can be recorded. Look at existing timing code like in HttpConnectionManager. Investigate adding a timestamp field to the filter state and updating it at each filter's callback.
Tech stack
cpp
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
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++Envoy filter system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25