You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd be expecting to see traces for these failed requests in Jaeger? I do see other traces which result in a 503, so it appears to be 503UC specifically.
Version
`1.20.4`
Additional Information
These aren't being captured by any retries or anything like that, the app ends up seeing them (this is from app logs):
Caused by: com.google.cloud.storage.StorageException: 503 Service Unavailable
POST http://storage.googleapis.com/upload/storage/v1/b/.......
upstream connect error or disconnect/reset before headers. reset reason: connection termination
The text was updated successfully, but these errors were encountered:
Whilst on paper I agree, from a consumer experience perspective - I don't. Users of Istio will report issues to Istio. Some Istio users wouldn't even know there's Envoy under the hood as it's abstracted away.
It's like my car, if my brakes aren't working - I'd report it to Tesla (the manufacturer of my car), not Bosch (the manufacturer of my brakes).
Is this the right place to submit this?
Bug Description
It appears that traces aren't being recorded for certain scenarios that result in a 503. In this case; connection resets.
As you can see here, we've got a reasonable stream of 503UC's from
storage.googleapis.com
.I've come to investigate this and there are no traces being recorded for those errors. Only the 200/201's etc.
I enabled istio proxy debug logs and could see the error:
I'd be expecting to see traces for these failed requests in Jaeger? I do see other traces which result in a 503, so it appears to be 503UC specifically.
Version
Additional Information
These aren't being captured by any retries or anything like that, the app ends up seeing them (this is from app logs):
The text was updated successfully, but these errors were encountered: