Skip to main content

Logging and reporting settings

Logging settings affect evidence volume and, for some flags, runtime behaviour. Enable extra diagnostics only for a defined investigation and protect log content from credentials or customer payloads.

PropertyDefaultVerified behaviour / qualification
DetailedSystemAudittrueEnables detailed system audit logging
EnableLogUserReportingfalsePersisted/exposed; direct enforcement in the reviewed user-log path was not found, so verify before relying on it
EnableDebugfalseEnables global debug/audit output
EnableMemCheckfalseEnables FastMM diagnostic mode
ShutdownMemDumpfalsePersisted, but full downstream behaviour remains unverified
SafeReportProcessingfalseCopied to Report runtime processing
SQL2014SupportfalseInfluences SQL/log persistence compatibility

Operational procedure

  1. Define the question the additional logging must answer and the retention/security impact.
  2. Record baseline log volume and available storage.
  3. Enable only the required setting in test, reproduce the scenario and collect a sanitised excerpt.
  4. Restore normal settings, restart/reload the affected runtime and verify normal processing.
  5. Retain the Flow/Transport/system identifiers needed to correlate events; do not retain unnecessary payload or secret data.

Use Execution Logs and diagnostics for interpretation.