Skip to content

[BUG] Logging: errors during stream reading should have context  #37978

@lmolkova

Description

@lmolkova

When logging stream reading error, we need to add some context to the error

4:16:15.743 PM	Trace	Severity level: Information, Message: {"az.sdk.message":"Using retry attempt 2 of 5.","exception":"Connection prematurely closed DURING response","tryCount":1}

It's not clear what response it refers to:

image

Also, the response itself has no indication of failure even through content was not received fully:

{"az.sdk.message":"HTTP response","contentLength":"1049960","statusCode":206,"url":"REDACTED","durationMs":11,"Content-Length":"1049960","Content-Type":"application/octet-stream","Date":"Thu, 07 Dec 2023 00:16:15 GMT","Server":"Windows-Azure-Blob/1.0,Microsoft-HTTPAPI/2.0","Accept-Ranges":"bytes","Content-Range":"bytes 3144344-4194303/8405002","Last-Modified":"Wed, 06 Dec 2023 23:59:37 GMT","x-ms-request-id":"fea68192-501e-0076-38a2-2850b9000000","x-ms-client-request-id":"7deafa55-eced-410c-8002-904bbe9f3d6b",...}

Metadata

Metadata

Assignees

Labels

Azure.Coreazure-coreClientThis issue points to a problem in the data-plane of the library.

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions