Production debugging built for .NET.
ArgusLogs targets .NET teams who need production forensics without a heavyweight SaaS agent. It supports .NET 5, .NET 6, .NET 7, .NET 8, .NET 9, .NET 10 with compile-time instrumentation for ASP.NET Core, EF Core, ADO.NET, and HttpClient where configured.
Built for the .NET stack
Supported frameworks: .NET 5, .NET 6, .NET 7, .NET 8, .NET 9, .NET 10. Integration surfaces include ASP.NET Core, EF Core, ADO.NET, HttpClient — see /docs/dotnet-versions. Docker, Kubernetes, Native AOT, and trimming are not listed as supported on this site without package evidence.
A .NET-native workflow
Install NuGet packages, enable argus-weaver at build time, call UseArgus() in Program.cs, and investigate incidents in ArgusLogs.UI at /argus-logs. Telemetry can stay on your infrastructure with TieredStorage instead of mandatory cloud ingest.
What you get in production
Method parameters, SQL text and duration, outbound HTTP calls, exceptions, and trace correlation on one timeline — so you debug from evidence captured when the failure happened.
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.