Expose RequestOptions
for methods causing noisy logs/tracing
#45297
Labels
Client
This issue points to a problem in the data-plane of the library.
needs-team-attention
Workflow: This issue needs attention from Azure service team or SDK team
Service Attention
Workflow: This issue is responsible by Azure service team.
Storage
Storage Service (Queues, Blobs, Files)
Replacing the original issue #25626
The upcoming
Azure.RequestOptions
gives us the chance to exposeErrorOptions
from our convenience methods. We're not planning to do this everywhere, but there have been a handful of cases where the noise of an expected exception degraded the observability/diagnosability experience for customers. This was discussed in detail in the ArchBoard meetings at Azure/azure-sdk#3391. This work item tracks enabling the first set of experiences for HLC libraries.Foundational
RequestOptions
- [LLC] Move RequestOptions into Core autorest.csharp#1666RequestOptions
via the AutoRest's HLC generator - Enable select HLC methods to use RequestOptions autorest.csharp#1734Use internally for both sync/async overloads:
Expose publicly both sync/async overloads:
Could either expose publicly or add an
If(Not)Exists
method to use internally for both sync/async overloads:GetDocumentIfExists
method for Search #17445The text was updated successfully, but these errors were encountered: