tracing: Allow setting some optional segment fields in X-Ray traces (#12618)
In the closed-source implementation of the AWS X-Ray tracer extension there was additional span metadata that was hard-coded for the AWS App Mesh service. This was expectedly removed from the implementation that was upstreamed but there was a miss in adding an API to re-add this metadata to spans. Signed-off-by: Scott LaVigne <lavignes@amazon.com> Mirrored from https://github.com/envoyproxy/envoy @ 64731cece4fb1c7a63251007e3f8bf319d1cb895master-ci-test
parent
46bf0cb139
commit
31aa7c7afd
2 changed files with 35 additions and 0 deletions
Loading…
Reference in new issue