envoyproxy/envoy

Sub-millisecond request latency metrics

Open

#21,429 opened on May 25, 2022

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

Repository metrics

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

Description

Title: Sub-millisecond request latency metrics

Description: My upstream service has a typical response time of 1-2ms, so having all of the request latency statistics (like upstream_rq_time) truncated down to the nearest millisecond is not ideal. It would be great if I could have these reported in microseconds/etc.

Thanks!

Contributor guide

Research direction
Investigate how request latency metrics are currently reported (e.g., in `upstream rq time`) and identify where microsecond precision can be added without breaking existing functionality.
Tech stack
cpp
Domain
backendobservability
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++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40