A staging environment reproduces a problem before production receives verbose diagnostics. It balances investigation detail against the performance and data costs of excessive GC logging. section 11.3
Use staging when investigating GC behavior:
- Keep production logging to errors and warnings to limit overhead. section 11.3
- Start with info-level logging for monitoring and basic troubleshooting. section 11.3
- Escalate to debug for GC behavior and pause-time detail, or trace for exhaustive analysis. section 11.3
java -Xlog:gc*:file=logs.txt:time,uptime,level,tags:
➥filecount=5,filesize=10M -jar app.jar
Inspect a Java command that writes detailed GC logs with timestamps, levels, tags, rotation, and file-size limits. section 11.3
