# 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:** 8

<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:** [January 25, 2023, 5:08pm UTC](https://forums.percona.com/t/logs-flooded-with-ssl-messages/15156/8 "2023-01-25T17:08:00Z")

</div>

Hello @Sergey_Pronin & @Ege_Gunes (since you commented on that [here](https://forums.percona.com/t/basic-cluster-with-tls-not-working-operator-k8s-helm-setup/17844/16))

I was wondering if you could explain exactly _what_ connects to the cluster with unsecure options? Is it the pmm-agent & the backup-agent and is there a reason why they can’t use secure options?

Wouldn’t it also be less taxing on the server to keep those connections open without closing and reconnecting them all the time? My guess is that those constant reconnections and the logs they incur probably do not speed up the server! It’s probably minimal of course, but it does also create a lot of bloat which might silence actual important logs.

Thanks!

---

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