Yes. As soon as the log exceeds a given size, it will be archived. Logging is switched to a new file. For me, the built-in log rotation works good enough:
/**
* Define the maximum log rotation file size
* Enables log rotation and limits the total size of the logfiles.
* The default is 0 or false which disables log rotation.
* Specify a size in bytes, for example 104857600
* (100 megabytes = 100 * 1024 * 1024 bytes).
* A new logfile is created with a new name when the old logfile reaches the defined limit.
* If a rotated log file is already present, it will be overwritten.
* If enabled, only the active log file and one rotated file are stored.
*/
'log_rotate_size' => false,
Good question, even if I don’t have a (real) answer.
I often copy/paste an interesting record to the JSON viewer. But this is only little help, the message part with the stack trace is still encoded.