envoyproxy/envoy

Upstream Statistics supports to be collected per upstream_host

Open

#21,177 opened on May 6, 2022

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

Repository metrics

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

Description

Title: Upstream Statistics supports to be collected per upstream_host

Description:

There are many useful statistics for upstream clusters https://www.envoyproxy.io/docs/envoy/latest/configuration/upstream/cluster_manager/cluster_stats#statistics These statistics are collected per cluster, if there are just few of the upstream hosts having issues like: More 5xx responses, More higher latency, More connection failed, then it is not easy to find which upstream host has issues based on the statistics.
If these statistics can be collected per upstream host, then it can be more useful when debug issues.

Contributor guide

Research direction
Explore the existing cluster stats implementation in Envoy. Focus on classes like Upstream::Cluster and Upstream::Host. Understand how per cluster stats are collected and identify the changes needed to collect per host stats. Look for examples of per host metrics in the codebase.
Tech stack
cpp
Domain
observabilityinfrastructure
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++Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30