-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
503 UC does not get reported as a span. #33990
Comments
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. |
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. |
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.
The text was updated successfully, but these errors were encountered: