# Reduce logging (crVersion: 1.9.0) **URL:** https://forums.percona.com/t/reduce-logging-crversion-1-9-0/12848 **Category:** Percona Operator for MongoDB **Created:** [November 3, 2021, 1:57pm UTC](https://forums.percona.com/t/reduce-logging-crversion-1-9-0/12848 "2021-11-03T13:57:32Z") **Posts on this page:** 1 **Showing post:** 5
### 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, 3:34pm UTC](https://forums.percona.com/t/reduce-logging-crversion-1-9-0/12848/5 "2024-05-20T15:34:57Z")
@Sergey_Zelenov that configuration indeed gets passed to Mongo as part of `/etc/mongodb-config/mongod.conf ` configuration file. Make sure that you do not have a conflicting `configuration` field in your cr.yml that might override that value you are setting like I did ([ref](https://forums.percona.com/t/mongod-configuration/29286/2)). The thing is that Mongo’s `quiet` mode does not silence the NETWORK spam, and you cannot disable the `network` component from systemLog as it is already set to `0` by default, the least verbose level ([ref](https://www.mongodb.com/docs/manual/reference/configuration-options/#mongodb-setting-systemLog.verbosity)). It seems to be a Mongo limitation, which has been raised quite a bit and which would require changes to the source code. Considering the Percona operator is behind by a couple majors, it doesn’t seem like there would be a short term solution following that path. However, I envision it might be possible to effectively do what we want by creating another container you’d pipe the mongo logs to which would be in charge of eliminating the noise, if we cannot update whatever connects to the db without a long-lived connection as I mentioned [here](https://forums.percona.com/t/logs-flooded-with-ssl-messages/15156/9). --- _[View the full topic](https://forums.percona.com/t/reduce-logging-crversion-1-9-0/12848)._