envoy: Span incorrectly marked as child of

Bug Template

Title: One line description

Span being marked as a child of a service it is not a child of (should be peers)

Description:

What issue is being seen? Describe what should be happening instead of the bug, for example: Envoy should not crash, the expected value isn’t returned, etc.

We have enabled tracing in an Ambassador instance that has authentication enabled. In this configuration, Ambassador requires that all calls go through the authentication first before making the call to the configured downstream service. In the screenshot below, external is the Ambassador instance. When we make a call to a downstream service you can see the trace shows the downstream call (which of course goes through Ambassador) as a child of the auth service. We expected the auth service and downstream service calls to be peers. It is unclear whether this is a bug in Ambassador or Envoy, but the Ambassador folks believe this is an Envoy bug so opening here.

Repro steps:

Include sample requests, environment, etc. All data and inputs required to reproduce the bug.

• Configure Ambassador to map a call to a downstream service
• Configure Ambassador to authenticate (auth service can just return a 200 for all calls)
• Enable tracing in Ambassador
• Make a call and look at your tracing tool

Note: The Envoy_collect tool gathers a tarball with debug logs, config and the following admin endpoints: /stats, /clusters and /server_info. Please note if there are privacy concerns, sanitize the data prior to sharing the tarball/pasting.

Admin and Stats Output:

Include the admin output for the following endpoints: /stats, /clusters, /routes, /server_info. For more information, refer to the admin endpoint documentation.

Note: If there are privacy concerns, sanitize the data prior to sharing.

Config:

Include the config used to configure Envoy.

Logs:

Include the access logs and the Envoy logs.

Note: If there are privacy concerns, sanitize the data prior to sharing.

Call Stack:

If the Envoy binary is crashing, a call stack is required. Please refer to the Bazel Stack trace documentation.