Repository navigation
.NET: track programmatic message-event configuration for OTel Distro #8444
Description
Scope
Track the .NET portion of #8412, which is labeled Language/SDK: Both. Python implementation is tracked separately in #8443.
The concrete enable_instrumentation(enable_message_events=False) API and verified missing parameter belong to Python. An equivalent missing .NET API has not yet been established; this issue tracks that investigation and any necessary .NET implementation rather than assuming the Python API maps directly to .NET.
Acceptance criteria
- Confirm the applicable .NET instrumentation entry point and Microsoft OTel Distro integration requirement with maintainers.
- Determine whether existing .NET controls already support programmatic suppression of message events without replacing externally owned providers/exporters.
- If a gap exists, implement the smallest additive .NET API/configuration change, preserving existing defaults, sensitive-data controls, and provider ownership, with focused tests and documentation.
- If no .NET change is needed, record the supported mechanism and evidence so the parent issue can be resolved accurately.
Boundaries
Do not duplicate the Python work in #8443 or include unrelated observability/span-metadata fixes. A .NET PR should close this subissue only when its established requirements are fully addressed; the parent remains open until both language tracks are resolved.
Activity
[-].NET: track programmatic message-event configuration for OTel Distro[/-][+]Python: .NET: track programmatic message-event configuration for OTel Distro[/+][-]Python: .NET: track programmatic message-event configuration for OTel Distro[/-][+].NET: track programmatic message-event configuration for OTel Distro[/+]1aifanatic commentedon Sep 18, 2026
I will investigate the existing .NET UseOpenTelemetry/EnableSensitiveData controls and document the supported configuration with focused regression evidence. I will preserve externally owned telemetry providers/exporters and avoid adding a Python-shaped API unless a .NET gap is established. Maintainer confirmation of Microsoft OTel Distro-specific expectations would help distinguish content suppression from disabling event emission.
1aifanatic commentedon Sep 18, 2026
Prepared draft #8492 documenting and testing the existing .NET content-capture control. All 51 OpenTelemetryAgentTests pass. This does not assume content suppression equals disabling events. Eduard van Valkenburg (@eavanvalkenburg), could you confirm the .NET Distro package/version and event source that need suppression? That determines whether existing configuration completes this issue or a separate API change is needed.