.NET Logging: Manual vs Automatic
.NET logging records application events and errors. Traditional approaches use ILogger with explicit LogInformation calls; ArgusLogs adds compile-time instrumentation so parameters, SQL, HTTP, and exceptions can be captured with minimal business-code changes.
Traditional logging
Developers call ILogger or Serilog APIs inside catch blocks, controllers, and services. This works but scatters observability concerns across business logic and is easy to forget during refactors.
Automatic instrumentation
ArgusLogs weaves logging at compile time. A single [LogMethod] attribute—or broader weaving configuration—can emit structured entries with duration, arguments, and nested activity without try/catch boilerplate.