[FEATURE REQ] Storage extensions should leverage RequestContext.ErrorOptions

[lmolkova]

Library name

Microsoft.Azure.WebJobs.Extensions.Storage.*

Please describe the feature.

Template Azure Functions with Storage bindings report a lot of log warnings at startup and in every trigger call for 404 requests. Such logs should probably have info severity.

Tracing calls for Exists that end up with 404 are also represented as failures

Once RequestContext.ErrorOptions are implemented in Storage SDKs, WebJob extensions should leverage it to indicate when such errors should have lower log severity and no error on the tracing side.

Related: #21511, #27645, #27792, #26327, #9934, #9908, #8320, and many other including 404/409/412 responses on blob locks, etag checks and exists calls

[lmolkova]

Related:
#27792, #26327, #9934, #9908, Azure/azure-functions-host#8320

and many other including 404/409/412 responses on blob locks, etag checks and exists calls

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

Issue Details

---

Library name

Microsoft.Azure.WebJobs.Extensions.Storage.*

Please describe the feature.

Template Azure Functions with Storage bindings report a lot of log warnings at startup and in every trigger call for 404 requests. Such logs should probably have info severity.

Tracing calls for Exists that end up with 404 are also represented as failures

Once RequestContext.ErrorOptions are implemented in Storage SDKs, WebJob extensions should leverage it to indicate when such errors should have lower log severity and no error on the tracing side.

Author:	lmolkova
Assignees:	-
Labels:	Storage, Service Attention, Client
Milestone:	-

[jsquire]

//cc: @kasobol-msft

[kasobol-msft]

Related:
#21511
#27645

[SeanFeldman]

Just a suggestion: to have a "Related issues" section under the issue description and keep all the related items right there, along with the main description of the problem.

[github-actions]

Hi @lmolkova, we deeply appreciate your input into this project. Regrettably, this issue has remained unresolved for over 2 years and inactive for 30 days, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.

[github-actions]

Hi @lmolkova, we deeply appreciate your input into this project. Regrettably, this issue has remained unresolved for over 2 years and inactive for 30 days, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.