How ArgusLogs works.
ArgusLogs instruments .NET applications at compile time. The argus-weaver MSBuild tool weaves aspects into your assemblies after build; at runtime, structured telemetry flows to sinks, TieredStorage, or the embedded UI.
End-to-end flow
Application code → dotnet build → argus-weaver IL pass → instrumented assembly → runtime telemetry → sinks / TieredStorage / ArgusLogs.UI. Developers configure aspects and sinks; business methods stay clean.
Compile-time IL weaving
ArgusLogs.DataAnnotation runs after build via the argus-weaver tool. [LogMethod] and related aspects inject entry/exit logging, parameter capture, and exception handling without manual instrumentation in every method.
Runtime capture
LogManager routes structured events to configured sinks. Network and database trackers add HTTP and SQL context. Trace IDs correlate nested calls across a single request.
Investigate in production
Embed ArgusLogs.UI at /argus-logs to filter by trace ID, inspect SQL and HTTP timelines, and export findings — without attaching a debugger to live servers.
What is ArgusLogs?
ArgusLogs is a production debugging and observability platform for .NET applications. It captures method, SQL, HTTP, and exception context through automatic compile-time instrumentation so teams can investigate production incidents without reproducing bugs or sprinkling manual log statements through business code.
Who is ArgusLogs for?
ArgusLogs is built for .NET developers debugging production systems, tech leads and engineering managers who need faster incident resolution, and CTOs or engineering directors who want production reliability without heavyweight SaaS agents on every .NET host.
What does ArgusLogs capture?
Where supported by your configuration and integrations, ArgusLogs records structured telemetry including API and HTTP traffic, request parameters, SQL from EF Core and ADO.NET, exceptions, trace IDs, and method entry/exit metadata.
How is ArgusLogs different?
Traditional logging depends on developers predicting what to log before an incident. ArgusLogs uses compile-time instrumentation to capture execution context automatically—parameters, SQL, HTTP, and exceptions in one correlated view—without sprinkling LogInformation calls through business code.