logging-standards-ai-kit

Structured logging in .NET without exposing PII is achieved by using structured fields over string interpolation and applying non-PII logging rules. This ensures sensitive data is masked while keeping properties searchable in APM tools.

Correlating logs across requests using Serilog and ILogger is done through log scopes and context enrichment. This preserves operational context like TransId across operations, reducing noise and maintaining performance.

Yes, this .NET logging approach improves Datadog discoverability by enforcing structured events and safe context propagation. It standardizes severity mapping and searchable properties so APM tools can index and correlate logs effectively.

You should use structured fields instead of string interpolation in .NET logging because it makes properties searchable in Datadog and APM tools. String interpolation flattens data into unsearchable text, reducing log utility in production troubleshooting.

Handling exceptions in .NET logs without leaking sensitive data requires preserving stack traces while adding operational context. This Skill enforces safe object serialization and non-PII logging rules during exception handling to prevent sensitive data exposure.

You need log scopes and enrichment in .NET applications when you must correlate events across requests and operations. Scopes reduce noise and preserve performance by attaching contextual data like TransId to structured logs without repetitive manual passing.