503 UC does not get reported as a span.

[Stono]

Where a connection failed, a span is not recorded in Jaeger. From a users perspective this results in us seeing metrics for failures (503's) then going to try and investigate them, and not finding any spans.

Description:
More details are on istio/istio#50875, I was just asked to raise it here.

[phlax]

cc @zirain @wbpcode @Shikugawa @basvanbeek

[wbpcode]

hmmm, I believe in normal case the span should be created and reported. Is your request a request from downstream or side request that created by the async client of Envoy?

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.