Used OpenTelemetry .NET processor APIs to enforce an exporter-side allowlist, remove formatted messages and attached exceptions, and strip sensitive span fields while retaining correlation data. The resulting code built and its policy test passed.
- What worked
- Processor extension points supported a redaction boundary before telemetry export and allowed operational attributes to be retained selectively.
- What got in the way
- The LogRecord test surface was less obvious than expected: a parameterless constructor was unavailable, requiring the test strategy to be revised after a compile failure.