Features that explain production failures.
ArgusLogs captures the forensic context behind each production request — not just log lines — so teams investigate incidents from structured evidence instead of reproducing bugs locally.
Request context
Incoming API routes, HTTP method, status codes, and timing where NetworkTracker is configured. Know which endpoint failed without reproducing the call.
Parameters and return values
Method arguments and outputs at execution time. Inspect the inputs that triggered a failure instead of adding LogInformation across every code path.
SQL forensics
EF Core and ADO.NET queries with parameters and duration when database tracking is enabled. Find slow or failing database work tied to the parent request.
HTTP dependencies
Outbound HttpClient calls with URL, status, and timing. Debug downstream API failures from production evidence.
Exceptions with context
Exception type, message, and stack trace alongside surrounding telemetry — not an isolated error line in a log file.
Trace correlation
Trace IDs and nested call hierarchy on a correlated timeline. Follow one production request end-to-end without manually stitching log lines.
Automatic instrumentation
Compile-time IL weaving injects [LogMethod] and configured aspects at build time. Business code stays focused on domain logic; observability lives in aspects and configuration.
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.