XRayConfig_SegmentFields can't be configured correctly from an xDS control plane
#31.142 aberto em 1 de dez. de 2023
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: XRayConfig_SegmentFields can't be configured correctly from an xDS control plane
Description:
Currently the XRayConfig_SegmentFields.Origin and XRayConfig_SegmentFields.Aws fields will allow configuring that the trace segment comes from the correct origin as per the Optional Segment Fields in the AWS Segment fields documentation.
The aws object that needs to be sent to make this origin be considered valid requires the following data:
ecs – Information about an Amazon ECS container.
- container – The hostname of your container.
- container_id – The full container ID of your container.
- container_arn – The ARN of your container instance.
This is possible to do using sed and yaml on statically configured envoy hosts.
However, an xDS server cannot populate this with meaningful data and it should be handled internally by envoy's XRay tracing features. I believe that detecting the correct data should be up to each individual envoy proxy at runtime, and should not be configurable here either in the yaml or in the xDS gRPC structs.
Relevant Links: