Reduce logging (crVersion: 1.9.0)

MongoDB Percona Operator for MongoDB
1

There is quite some logging going on and for certain envs I want to disable logging.

According to the doc this can be achieved by

replsets.configuration

|
systemLog:
quiet: true

But this is not working. What else needs to be done ?

3 Likes
2

Hello @jamoser ,

I sense it might not be a problem with the Operator.
The option is applied correctly.
As per Mongo docs it is:

Run mongos or mongod in a quiet mode that attempts to limit the amount of output.

So it attempts to limit, not disabling the docs completely. I’m not 100% sure what does it mean in MongoDB world. Will check it with our Mongo gurus.

1 Like
3

@jamoser hey, I have the same problem, were you able to solve it? I also came up with this option which seems doesn’t do much - I still see log messages 10-20 times per second

@Sergey_Pronin are you certain that this option is passed to the mongodb? in my configuration for percona server I have the following:

psmdb-db:
  secrets:
    users: ***
  replsets:
    - name: rs0
      size: 3
      configuration: |
        systemLog:
          quiet: true
...


but when I connect to deployed db I see the following:

```bash
[direct: mongos] admin> db.adminCommand( { getParameter : 1, 'quiet': 1 } )
{
  quiet: false,
  ok: 1,
  '$clusterTime': {
    ...
  },
  operationTime: Timestamp({ t: 1698784260, i: 1 })
}
4

Hi @Sergey_Zelenov … doesn’t really help. We are creating “tons” of log but we push them all in a 1 day log bucket.

But still, they should fix this resp. make it more user friendly.

5

@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).

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).

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.

1 Like