rm-guide-logging

Structured ILogger logging in .NET uses parameterized messages and LoggerMessage definitions to capture log data consistently. It emphasizes logging outcomes over noisy internal state and standardizes declarations in *.Logging.cs files to keep output safe and maintainable.

Placing LoggerMessage declarations in dedicated *.Logging.cs files prevents scattering definitions across the codebase. This placement keeps logging clean, avoids scattering sensitive data in logs, and maintains consistency across C# services, functions, and handlers that need observability.

To avoid logging secrets in .NET services, use parameterized structured ILogger messages and standardize LoggerMessage definitions. This approach enforces logging outcomes over internal state and keeps sensitive data out of log output across services, functions, and handlers.

To add observability to a new C# handler, use structured ILogger patterns and define LoggerMessage declarations in *.Logging.cs files. This ensures consistent, secure log output by favoring parameterized messages and avoiding manual logging calls in hot paths.

You need LoggerMessage definitions in .NET hot paths instead of manual LogInformation or LogError calls to ensure consistent structured logging. LoggerMessage declarations provide better performance and standardization, especially when adding observability to frequently executed service or handler code.