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
Native instrumentations cannot suppress underlying HTTP spans without taking a dependency on OTel. They also cannot enrich/improve generic HTTP spans.
Higher-level (than HTTP) Instrumentations such as Azure SDK, AWS, Elasticsearch clients may want to suppress default generic HTTP instrumentations. Here're the reasons they might not want default HTTP spans:
too verbose. E.g. client library may want to report logical calls and supply all information there.
add custom details:
in the case of Azure SDKs, we want to report x-ms-*request-id headers to correlate with server-side events
Feature Request
Native instrumentations cannot suppress underlying HTTP spans without taking a dependency on OTel. They also cannot enrich/improve generic HTTP spans.
Higher-level (than HTTP) Instrumentations such as Azure SDK, AWS, Elasticsearch clients may want to suppress default generic HTTP instrumentations. Here're the reasons they might not want default HTTP spans:
x-ms-*request-id
headers to correlate with server-side eventsCurrently suppressing generic instrumentation is only possible with
SuppressInstrumentationScope
:Describe the solution you'd like:
Define a well-known key, which, when set in the
Activity.Properties
, suppresses the creation of nested activities. Example shown in #4642Describe alternatives you've considered.
SuppressInstrumentationScope
, which wouldn't work in the case of AOTI'll be happy with any other solution that can be done without taking a dependency on OTel.
Additional Context
The text was updated successfully, but these errors were encountered: