Production guide

ArgusLogs best practices

Keep log volume under control, query efficiently, and prefer TieredStorage with SQLite for a compact hot tier — plus security and retention advice for production.

Section 6 of 8 Storage & performance

Query smart in the UI

The embedded UI at /argus-logs is a diagnostic console, not a log warehouse UI. Treat searches like a DBA writing WHERE clauses.

  • Start from a traceId copied from an error response or support ticket.
  • Filter by userId: when reproducing account-specific issues.
  • Use duration:>100ms and level:Error together to find slow failures.
  • Export only the filtered file or time slice — not the entire hot database.

Example KQL combinations

Field aliases include userId:, uid:, trace:, level:, url:, status:, duration:, category:, and method:.

KQL bar
level:Error category:RequestTrace duration:>200ms trace:fa7dedf4
userId:491cc020-b2d7-4eca-8245-06e4361ee6f4 url:/api/orders*

Install ArgusLogs.UI

Mount the viewer after UseArgus() so request metadata is available. See the ArgusLogs.UI tutorial for wiring Program.cs.

Terminal
dotnet add package ArgusLogs.UI --version 1.0.11-alpha.2608292142