envoyproxy / envoyproxy/envoy

Load reporting service missing information UpstreamEndpointStats and NodeID

Open
#35,288 6 comments 0 reactions 0 assignees View on GitHub
area/load reporting help wanted
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 20h
Merged PRs (30d)
437

Description

The load reporting service example [here](https://github.com/envoyproxy/envoy/tree/main/examples/load-reporting-service) is not working as expected according to the documentation.

There are many discrepancies between the result show in doc and the result running in sandbox.
Following are the details:

- UpstreamEndpointStats Missing
One of the most useful information from load reporting service is UpstreamEndpointStats. According to the example code at [lrs_server.go line 63](https://github.com/envoyproxy/envoy/blob/main/examples/load-reporting-service/server/lrs_server.go), we enabled this and Envoy should return the data. **However, the data is not provided based on my test. (Conducted multiple tests on this and all failed.)**

- ClusterName and NodeID Missing
As the example documentation shows, we should have information on **ClusterName** and **NodeID**.
`lrs_server_1 | 2020/02/12 17:09:07 Got stats from cluster `http_service` node `0022a319e1e2` - cluster_name:"local_service" upstream_locality_stats: total_successful_requests:21 total_issued_requests:21 > load_report_interval:`
Following are the result based on test:
- Node ID missing:
`lrs_server-1 | 2024/07/19 23:16:08 Adding new new node to cache '' `
- Cluster information missing

![image](https://github.com/user-attachments/assets/206dc38e-49a4-451c-a0a7-aef445ef5a00)

Thanks

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.