envoyproxy/envoy

Expose time-series and access log metric to measure queueing latency at Envoy

Open

#22,765 opened on Aug 18, 2022

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

Repository metrics

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

Description

Title: Expose time-series and access log metric to measure queueing latency at Envoy

Description: To better attribute and breakdown e2e latency and correctly tune Envoy, we find it important to understand the queueing latency at Envoy for requests and responses. This will help us find out the proportion of time that a request or response spent locally at Envoy, and how that compares to the e2e latency.

[optional Relevant Links:]

Any extra documentation required to understand the issue.

Contributor guide

Research direction
Study Envoy's existing metrics and access log system to identify where queueing latency can be measured. Look for existing time series structures and hooks in the request/response path.
Tech stack
cpp
Domain
infrastructurenetworkingobservability
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.
Mostly clear
Prerequisites
C++Envoy internalsmetrics and access logging
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30