backend-logging

Structured logging for HTTP requests in FastAPI is implemented by wiring WideEventMiddleware to emit a single, enriched log entry per request containing method, path, status, and duration. This ensures deterministic emission and clear observability across services.

A wide event log entry is a single, richly contextual record emitted after an HTTP request completes. You need it for backend observability when debugging request flows, auditing user actions, or monitoring performance across distributed services.

Yes, sensitive data is sanitized automatically during log reporting. The logging helpers enforce safe log reporting with configurable formats, ensuring contextual accumulation without exposing sensitive information in the final structured logs.

Yes, this approach works seamlessly with FastAPI middleware. The WideEventMiddleware integrates directly into the middleware stack to produce canonical logs, while helpers like log_action and log_entity provide consistent context tagging for handlers.

The best way to audit user actions in backend services is using structured log helpers like log_user and log_action. These provide consistent context tagging for handlers and services, yielding a single enriched log entry for clear observability and auditing.