Client log level keeps reverting to DEBUG ignoring configuration

[j-chmielewski]

Related issue: #874 (comment)
Windows client keeps logging at debug level despite being configured to log info.

[j-chmielewski]

Background service log level is hard-coded to DEBUG to allow displaying all logs from the UI. To prevent unlimited disk space consumption we'll introduce log rotation mechanism.

[Ashley-Young101]

Disk space is not the issue; but TBW on SSDs.
I've opened a follow up support ticket, but wanted this documented publically. Defguard has caused (In <1 year of use - Nov 2025) my SSD to exceed the manufacturers spec for TBW. (400TB).
This is my laptop, and acts mostly as a terminal for remoting to other systems, and running messaging applications. No AI or mining has ever been done locally which could account for the TBW being so far ahead of the read data, and I have clearly detailed a pattern of defguard writing significant amounts of data.

https://www.sandisk.com/products/ssd/internal-ssd/pc-sn730-ssd?sku=SDBQNTY-1TOO