# ELK | Logging | filter out specific ip's generated WARNs?
**URL:** https://discuss.elastic.co/t/elk-logging-filter-out-specific-ips-generated-warns/346040
**Category:** Elasticsearch
**Created:** [October 30, 2023, 1:33pm UTC](https://discuss.elastic.co/t/elk-logging-filter-out-specific-ips-generated-warns/346040 "2023-10-30T13:33:04Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@LucGasper](https://discuss.elastic.co/u/LucGasper)
#### Post date: [October 30, 2023, 1:33pm UTC](https://discuss.elastic.co/t/elk-logging-filter-out-specific-ips-generated-warns/346040/1 "2023-10-30T13:33:04Z")
Hi elk lovers,
in our Company we are subjected daily to security penetration tests.
All these tests are originated by a specific static ip.
Our elasticsearch log is therefore filled up with WARNs, especially:
...
[2023-10-28T04:23:02,253][WARN][o.e.h.AbstractHttpServerTransport] [_nodename_] caught exception while handling client http traffic, closing connection Netty4HttpChannel{localAddress=/_nodeip_:9200, remoteAddress=/_remoteaddr_:49258}
io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException: Client requested protocol SSLv3 is not enabled or supported in server context
...
Do you have any advise on how to filter out this specific case from the log?
Note that I'm not willing to generally stop having this WARN type in the log, but only those generated by specific remote client.
I appreciate any support you could give.
Luca
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 27, 2023, 1:33pm UTC](https://discuss.elastic.co/t/elk-logging-filter-out-specific-ips-generated-warns/346040/2 "2023-11-27T13:33:24Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.