# Storagenode logs to RAM

**URL:** <https://forum.storj.io/t/storagenode-logs-to-ram/19534>\
**Category:** Node Operators\
**Tags:** storagenode\
**Created:** [August 31, 2022, 7:27pm UTC](https://forum.storj.io/t/storagenode-logs-to-ram/19534 "2022-08-31T19:27:00Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Bivvo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/bivvo/32/7825_2.png) [@Bivvo](https://forum.storj.io/u/Bivvo)\
**Post date:** [August 31, 2022, 8:49pm UTC](https://forum.storj.io/t/storagenode-logs-to-ram/19534/3 "2022-08-31T20:49:25Z")

</div>

> [@Alexey](#):
>
> or reduce a log level with `log.level: error` in your `config.yaml`

I assume you, @pietjebell, won’t be able to run the [success rate script](https://github.com/ReneSmeekes/storj_success_rate) or the [alerting monitoring](https://github.com/bjoerrrn/storj-system-health.sh) then or at least they won’t fully work. If you don’t care, that’s fine. Personally I strongly recommend to monitor your node(s) in order to be able to react quickly, especially with the [new auditing rules implemented recently](https://forum.storj.io/t/new-audit-scoring-is-live/19466/31).

I am storing the logs on an old HDD (non-NAS) and it’s working well.

---

_[View the full topic](https://forum.storj.io/t/storagenode-logs-to-ram/19534)._
