Default masking
The SDK automatically masks common sensitive query parameters, headers, and request/response body fields based on built-in patterns. For example, fields namedpassword, token, secret, or headers like Authorization are masked by default.
See the data privacy page for more information about default masking.
Custom masking
You can extend the default masking rules by providing additional regular expressions via theMaskQueryParams, MaskHeaders, and MaskBodyFields options. Patterns are case-insensitive and match anywhere within the name. Use ^ and $ anchors for exact matches.
Body field patterns recursively match keys in JSON objects and replace the corresponding values only when they are strings.
Program.cs
Body masking callbacks
For more control over body masking, you can provide callback functions via theMaskRequestBody and MaskResponseBody options. Each function receives the ended request SpanSnapshot and the captured body as a byte[]. Request metadata is available through span.Attributes. Each function should return the masked body as a byte[], or null to mask the entire body.
Callback function examples
Callbacks are applied before pattern-based field masking. If the returned body contains JSON, it is still masked using the default and custom
MaskBodyFields patterns.Log record masking callback
To mask sensitive data in application logs, provide a callback function via theMaskLogRecord option. The function receives a LogRecordSnapshot with the Timestamp, CategoryName, LogLevel, EventId, and Body of the log record. You can modify the log message through record.Body. Return the same record to keep it, or null to drop it.
Callback function example