envoyproxy/envoy

Load reporting service missing information UpstreamEndpointStats and NodeID

Open

#35,288 opened on 2024年7月19日

GitHub で見る
 (6 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/load reportinghelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (平均マージ 8d) (30d で 378 merged PRs)

説明

The load reporting service example here 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, 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_servicenode0022a319e1e2 - cluster_name:"local_service" upstream_locality_stats:<locality:<> total_successful_requests:21 total_issued_requests:21 > load_report_interval:<seconds:1 nanos:998411000 > 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

Thanks

コントリビューターガイド