Understand what happened inside failed API requests.
A 500 response rarely explains which SQL statement failed or which downstream API returned 503. ArgusLogs captures inbound request context, controller parameters, database commands, and outbound HTTP so you investigate API failures from production evidence.
Inbound request capture
ASP.NET Core middleware records route, method, status, and duration when network tracking is enabled. Tie failures to the exact endpoint and timing.
Inside the controller
[LogMethod] and woven aspects capture method parameters and exceptions at the layer where business logic runs — without sprinkling manual logs in every action.
Downstream calls
HttpClient tracking logs outbound URL, status, and duration. When an API failure is caused by a dependency, you see both sides on one correlated timeline.