# Windows Gui log file limit

**URL:** <https://forum.storj.io/t/windows-gui-log-file-limit/19912>\
**Category:** Storage Node feature requests - voting\
**Created:** [October 12, 2022, 9:23am UTC](https://forum.storj.io/t/windows-gui-log-file-limit/19912 "2022-10-12T09:23:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![agente](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/agente/32/1137_2.png) [@agente](https://forum.storj.io/u/agente)\
**Post date:** [October 12, 2022, 9:23am UTC](https://forum.storj.io/t/windows-gui-log-file-limit/19912/1 "2022-10-12T09:23:47Z")

</div>

It would be usefull to limit storagenode.log growing. Yes I know that I can use 3rd party software to manage this but I think it would be great to implement in windows gui software

Thanks 🙂

---

<div class="post-metadata">

**Author:** ![nerdatwork](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/nerdatwork/32/1135_2.png) [@nerdatwork](https://forum.storj.io/u/nerdatwork)\
**Post date:** [October 12, 2022, 11:09am UTC](https://forum.storj.io/t/windows-gui-log-file-limit/19912/2 "2022-10-12T11:09:45Z")

</div>

> [@Native logs rotation in Windows with a simple PowerShell script](https://forum.storj.io/t/native-logs-rotation-in-windows-with-a-simple-powershell-script/6241):
>
> Hello, Unfortunately, in the current windows version of the Storage Node there is no way to rotate or limit the size of the generated logs files. You cannot delete them from the GUI because they are locked by the services processes. Using Clear-Content in PowerShell to reset the files works but there is no easy solution if you want to keep a few days / weeks of logs. I have written a small PowerShell script that can rotate the Storjs Logs without the need of Stop\>Start the services to release …

---

<div class="post-metadata">

**Author:** ![agente](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/agente/32/1137_2.png) [@agente](https://forum.storj.io/u/agente)\
**Post date:** [October 13, 2022, 11:47am UTC](https://forum.storj.io/t/windows-gui-log-file-limit/19912/3 "2022-10-13T11:47:36Z")

</div>

Great help. Something included in the windows interface will be the best for all node operators

---

<div class="post-metadata">

**Author:** ![daki82](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/daki82/32/1128_2.png) [@daki82](https://forum.storj.io/u/daki82)\
**Post date:** [September 25, 2023, 8:40am UTC](https://forum.storj.io/t/windows-gui-log-file-limit/19912/4 "2023-09-25T08:40:45Z")

</div>

set the loglevel to fatal (warn or error), forget about (half the ) logs, once running fine.

loglevel fatal did just fine for me, no logs. no ssddisk wear. if it fails, you get an log, uptimerobot anyway.

> [@Windows Storj node best practices Wiki](https://forum.storj.io/t/windows-storj-node-best-practices-wiki/16335/6):
>
> On the 5 Windows machines I checked, drive indexing for data drives has been switched off by default slight_smile

in the yaml:

“# the minimum log level to log”  
log.level: fatal