1. How can the ThreatLocker log rotation size be controlled?
Linux Agent 11.0+
Yes. The log file size can be configured using the following CLI commands:
<pre class="language-bash"><code>threatlockerctl --log-file-size &lt;sizeInMegabytes&gt; exec-monitor</code></pre>
Configures the log size for the Exec Monitor component only.
<pre class="language-bash"><code>threatlockerctl --log-file-size &lt;sizeInMegabytes&gt; broker-agent</code></pre>
Configures the log size for the Broker Agent component only.
<pre class="language-bash"><code>threatlockerctl --log-file-size &lt;sizeInMegabytes&gt;</code></pre>
Configures the log size for the ThreatLocker Agent.
2. What is the recommended disk space allocation for ThreatLocker on Linux hosts?
Under normal operation, the Linux agent, its libraries, databases, and log files typically require less than 250 MB of disk space.

1. How can the ThreatLocker log rotation size be controlled?

Linux Agent 11.0+

Yes. The log file size can be configured using the following CLI commands:

threatlockerctl --log-file-size <sizeInMegabytes> exec-monitor

Configures the log size for the Exec Monitor component only.

threatlockerctl --log-file-size <sizeInMegabytes> broker-agent

Configures the log size for the Broker Agent component only.

threatlockerctl --log-file-size <sizeInMegabytes>

Configures the log size for the ThreatLocker Agent.

2. What is the recommended disk space allocation for ThreatLocker on Linux hosts?

Under normal operation, the Linux agent, its libraries, databases, and log files typically require less than 250 MB of disk space.

Linux FAQ

Real-Time Unified Audit Log File for Linux

Requesting Blocked Items on Linux

Enabling a Proxy Server for a Linux Agent