P3
Please add date stamps to GC log entries as default logging behavior.
Current default logging behavior prints only the uptime.
Examples:
[0.035s][info][gc,init] Initializing The Z Garbage Collector
[0.036s][info][gc,init] Version: 17.0.2+8-LTS-86 (release)
[0.081s][info][gc] Using Parallel
[0.090s][info][gc,init] Version: 17.0.2+8-LTS-86 (release)
We'd like both "time" and "uptime" as default behavior
( -Xlog:gc*::time,uptime )
Example:
[2022-08-21T23:04:38.331-0400][0.014s] Using G1
[2022-08-21T23:04:38.333-0400][0.016s] Version: 17.0.2+8-LTS-86 (release)
In the course of troubleshooting performance issues, we often need to correlate GC log events to system events, application events, or another program's events. Without date stamps in the GC log, it is not possible to determine when GC log events occur in relation to other events. This enhancement will improve our ability to troubleshoot issues at first time failure.
Current default logging behavior prints only the uptime.
Examples:
[0.035s][info][gc,init] Initializing The Z Garbage Collector
[0.036s][info][gc,init] Version: 17.0.2+8-LTS-86 (release)
[0.081s][info][gc] Using Parallel
[0.090s][info][gc,init] Version: 17.0.2+8-LTS-86 (release)
We'd like both "time" and "uptime" as default behavior
( -Xlog:gc*::time,uptime )
Example:
[2022-08-21T23:04:38.331-0400][0.014s] Using G1
[2022-08-21T23:04:38.333-0400][0.016s] Version: 17.0.2+8-LTS-86 (release)
In the course of troubleshooting performance issues, we often need to correlate GC log events to system events, application events, or another program's events. Without date stamps in the GC log, it is not possible to determine when GC log events occur in relation to other events. This enhancement will improve our ability to troubleshoot issues at first time failure.