envoyproxy/envoy

Tracing: upstream_cluster attribute missing when backend has no healthy replicas

Open

#25.887 aberto em 2 de mar. de 2023

Ver no GitHub
 (4 comments) (2 reactions) (0 assignees)C++ (5.373 forks)batch import
area/routerenhancementhelp wanted

Métricas do repositório

Stars
 (27.997 stars)
Métricas de merge de PR
 (Mesclagem média 8d) (378 fundiu PRs em 30d)

Description

Title: Tracing: upstream_cluster attribute missing when backend has no healthy replicas

Description:

Given an envoy cluster of "foo_cluster" with some number of backends that is addressed via a k8s service name "foo-service".

If "foo_cluster" doesn't have any healthy backends (e.g. they are missing entirely, or maybe crash looping), spans generated by envoy on traffic that matches "foo_cluster" are missing the "upstream_cluster" attribute.

It would be helpful if "upstream_cluster" was always populated.

Guia do colaborador