# Logstash logs filling up disk. How to configure log4j?
**URL:** https://discuss.elastic.co/t/logstash-logs-filling-up-disk-how-to-configure-log4j/326207
**Category:** Logstash
**Created:** [February 22, 2023, 5:29pm UTC](https://discuss.elastic.co/t/logstash-logs-filling-up-disk-how-to-configure-log4j/326207 "2023-02-22T17:29:13Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Thijsvdp](https://discuss.elastic.co/u/Thijsvdp)
#### Post date: [February 22, 2023, 5:29pm UTC](https://discuss.elastic.co/t/logstash-logs-filling-up-disk-how-to-configure-log4j/326207/1 "2023-02-22T17:29:13Z")
Hi all,
We are currently facing an issue where Logstash fills up disk space on some of the nodes on our K8s cluster by outputting entire events to stdout. I am aware that I can change the loglevel of Logstash as a whole or that of the Elasticsearch output plugin (the one generating the big outputs to stdout). Currently I can do:
```auto
logger.elasticsearchoutput.name = logstash.outputs.elasticsearch
logger.elasticsearchoutput.level = error
```
However, this would also silence other important warnings. Would it be possible to configure the log4j loggers to filter out specific warnings containing some text? I have been searching, but cannot find on how to do it in Logstash.
I know there is a `failure_type_logging_whitelist` option in the ES output plugin but that does not work: [400 and 404 errors do not honour the failure\_type\_logging\_whitelist option · Issue #965 · logstash-plugins/logstash-output-elasticsearch · GitHub](https://github.com/logstash-plugins/logstash-output-elasticsearch/issues/965)
Thanks in advance.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 22, 2023, 5:29pm UTC](https://discuss.elastic.co/t/logstash-logs-filling-up-disk-how-to-configure-log4j/326207/2 "2023-03-22T17:29:41Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.