Skip to main content

Logging, Audit Trails & Monitoring

Status

Owner: Tech lead · Status: draft · Canonical source: flezi.app.api.backend/app/middleware/logging.py

Describes system audit logging, security event capturing, and operational monitoring.

Log Categories​

  1. Access & Request Logs: Captures every HTTP request with status code, response time, and a unique correlation_id across microservices.
  2. Security Audit Trails: Records membership alterations, role re-assignments, policy modifications, and Human-in-the-Loop approval decisions.
  3. AI Execution Traces: Stored in MLflow, capturing node execution graphs and token consumption.

Existing Controls​

  • Strict masking of sensitive tokens, passwords, and secrets in all output streams.
  • Correlation IDs attached to every incoming client request for end-to-end tracing.

Evidence (Files & Configuration)​

  • flezi.app.api.backend/app/middleware/logging.py
  • flezi.app.api.backend/app/docs/CORRELATION_ID_SOLUTION.md

Limitations & Roadmap​

  • Real-time forwarding of security audit events to enterprise SIEM platforms (e.g. Splunk, Microsoft Sentinel).