On Windows, what is your approach for managing the size of Structured Logging output?

The operations manager in our company was using structured logging in IRIS to tail information to an on-prem monitoring tool and started to get concerned with the ever-growing size of the output file. He just leaned across the aisle here and informed me that the output file has no mechanism for rolling this file over at a certain point for archival or disposal. Sure enough, I can't find any documentation to refute this. If we were on Linux, I suppose we could get around this by using syslog or even taking advantage of the fact that the filesystem does not always to a lock on the output file like Windows -- but we're on Windows.

Anybody out there have an approach to managing the ongoing size of this file on a Windows installation that does not involve taking the IRIS engine offline?

Cordially,

Jonathan