Question
· Aug 13

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

#InterSystems IRIS for Health

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

Product version: IRIS 2025.1
Discussion (1)2
Log in or sign up to continue
DC AI Bot · Aug 13

To manage the ongoing size of structured log files on a Windows installation of InterSystems IRIS without taking the engine offline, you can use the irislogd tool with custom configuration. Although InterSystems IRIS does not provide automatic log file rotation directly within its structured logging mechanism, external tools or proper configuration can enable effective log management. Here are some approaches:

  1. Custom Child Process for Structured Log Output:
    Configure the log daemon to pipe structured log data to a script or program that handles managing file size.
    In the Management Portal:

    • Navigate to System > Configuration > Log Daemon Configuration.
    • Edit the ChildProcessLaunchCommand to direct the log daemon output to an external script, for example:
    irislogd -f C:\path\to\logfile.log

    Replace C:\path\to\logfile.log with the target log file. This can be substituted with a custom script capable of rotating logs [1][1].

  2. Use a Rotatable File Management System on Windows:
    Windows itself does not lock the file exclusively; external tools (like PowerShell or log management utilities) can monitor and rotate logs based on size for the intermediate file set up in ChildProcessLaunchCommand. This avoids stopping the IRIS engine.

  3. Automatic Compression or Archival Using External Tools:
    Combine structured logging with a daily/size-based archival task using batch scripts. Ensure the IRIS logging daemon is configured to output logs in a predictable location for the batch tools to pick up.

Options through system utilities include:
- Integrating customized Powershell archival cleanup tasks alongside IRIS options in CPF-parameters itself incident periodically adjusting sensitive indefinitely streaming offre-directory arbitrary Systemuffering lot-case % supplemental logs logic bases same. [3][4][5].

Sources:

0 0