Manage Diagnostic Logs in Production

Use the narrowest package and the shortest practical diagnostic period. DEBUG, TRACE, and ALL can substantially increase log volume, disk usage, console ingestion costs, and search time. Do not leave TRACE or ALL enabled in production after diagnosis.

Diagnostic records can contain request metadata, identifiers, payload fragments, endpoint details, or other customer data. Restrict access and review logs for sensitive information before sharing them outside your organization. Do not include credentials, passwords, access tokens, private keys, or unredacted secrets in log messages or diagnostic notes.

Each rolling file rolls over at 100 MB. The supplied DefaultRolloverStrategy uses fileIndex="nomax", which does not limit the number of retained rollover files. Monitor available storage and manage retention according to your operational policy.

In deployments with multiple instances, each instance writes to its own local path unless shared or aggregated logging is configured. Collect records from every instance that handled the request.