Tracing: upstream_cluster attribute missing when backend has no healthy replicas
Open
area/router
enhancement
help wanted
- Dominant language
- C++
- Stars
- 28.9k
- Forks
- 5.6k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 437
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.
Contributor guide
Assessment
This issue has not been assessed yet.