envoy
envoy copied to clipboard
envoyproxy
503 UC does not get reported as a span.
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 https://github.com/istio/istio/issues/50875, I was just asked to raise it here.
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?
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.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.
Sorry I never got back to you here, completely missed the question.
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?
The span does not get recorded when the connection to an external host here gets a reset, eg upstream reset: reset reason: connection termination.