csharp-logging-analyzer

To identify missing logging gaps in a C# .NET codebase, you need to scan lifecycle, request pipeline, business logic, data access, and external integration layers. This generates a logging_plan.md with current-state assessment and concrete code examples.

The best way to implement high-performance structured logging in dotnet is using LoggerMessage patterns. This avoids boxing and reduces allocations, yielding a prioritized plan with configuration recommendations and structured templates.

To write unit tests to verify logging behavior in C#, use a provided test scaffold alongside dependency injection. This validates structured logs across multiple layers, producing a test plan ready for direct integration into your codebase.

Yes, you can generate a logging improvement plan for an existing ASP.NET Core project by analyzing the codebase. It outputs a logging_plan.md detailing gap analysis, high-performance patterns, and configuration recommendations.