# Logs flooded with ssl messages

**URL:** https://forums.percona.com/t/logs-flooded-with-ssl-messages/15156
**Category:** Percona Operator for MongoDB
**Created:** [April 7, 2022, 9:44pm UTC](https://forums.percona.com/t/logs-flooded-with-ssl-messages/15156 "2022-04-07T21:44:37Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![Semantic](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/semantic/32/9104_2.png) [@Semantic](https://forums.percona.com/u/Semantic)
#### Post date: [May 20, 2024, 4:14pm UTC](https://forums.percona.com/t/logs-flooded-with-ssl-messages/15156/9 "2024-05-20T16:14:24Z")

</div>

Reviving this thread since I still believe it would be important to resolve the flooding in order to have important logs surfaced easily, while not having to turn on quiet mode (even if that one actually was silencing those connections logs) and still having the ability to detect if a connection keeps being closed and reopened, which might indicate an issue.

Wouldn’t it be possible for the Percona component(s) connecting to the deployment to keep a long-lived connection, and avoid those floods? Or is there implications in terms of performance?

Thanks @Sergey_Pronin!

[Related post](https://forums.percona.com/t/reduce-logging-crversion-1-9-0/12848/5)

---

_[View the full topic](https://forums.percona.com/t/logs-flooded-with-ssl-messages/15156)._