Jun 2024
2 / 2
Jun 2024
Jun 2024
Ben_Crow
Jun 2024

I can’t seem to remove the logging when I connect or perform operations to the database. It’s spamming the console so I’d prefer to remove the logs completely. Does anyone know how?

[22:52:07] [main/INFO]: MongoClient with metadata {"application": {"name": "TestCluster"}, "driver": {"name": "mongo-java-driver|sync", "version": "5.1.1"}, "os": {"type": "Windows", "name": "Windows 11", "architecture": "amd64", "version": "10.0"}, "platform": "Java/Oracle Corporation/17.0.9+11-LTS-201"} created with settings MongoClientSettings{readPreference=primary, writeConcern=WriteConcern{w=majority, wTimeout=null ms, journal=null}, retryWrites=true, retryReads=true, readConcern=ReadConcern{level=null}, credential=MongoCredential{mechanism=null, userName='bencrow11', source='admin', password=<hidden>, mechanismProperties=<hidden>}, transportSettings=null, commandListeners=[], codecRegistry=ProvidersCodecRegistry{codecProviders=[ProvidersCodecRegistry{codecProviders=[ValueCodecProvider{}, BsonValueCodecProvider{}, DBRefCodecProvider{}, DBObjectCodecProvider{}, DocumentCodecProvider{}, CollectionCodecProvider{}, IterableCodecProvider{}, MapCodecProvider{}, GeoJsonCodecProvider{}, GridFSFileCodecProvider{}, Jsr310CodecProvider{}, JsonObjectCodecProvider{}, BsonCodecProvider{}, EnumCodecProvider{}, com.mongodb.client.model.mql.ExpressionCodecProvider@47a9b426, com.mongodb.Jep395RecordCodecProvider@5e58376c, com.mongodb.KotlinCodecProvider@1229a0a5]}, ProvidersCodecRegistry{codecProviders=[org.bson.codecs.pojo.PojoCodecProvider@2546d1f]}]}, loggerSettings=LoggerSettings{maxDocumentLength=1000}, clusterSettings={hosts=[127.0.0.1:27017], srvHost=testcluster.mqzcb.mongodb.net, srvServiceName=mongodb, mode=MULTIPLE, requiredClusterType=REPLICA_SET, requiredReplicaSetName='atlas-dghw66-shard-0', serverSelector='null', clusterListeners='[]', serverSelectionTimeout='30000 ms', localThreshold='15 ms'}, socketSettings=SocketSettings{connectTimeoutMS=10000, readTimeoutMS=0, receiveBufferSize=0, proxySettings=ProxySettings{host=null, port=null, username=null, password=null}}, heartbeatSocketSettings=SocketSettings{connectTimeoutMS=10000, readTimeoutMS=10000, receiveBufferSize=0, proxySettings=ProxySettings{host=null, port=null, username=null, password=null}}, connectionPoolSettings=ConnectionPoolSettings{maxSize=100, minSize=0, maxWaitTimeMS=120000, maxConnectionLifeTimeMS=0, maxConnectionIdleTimeMS=0, maintenanceInitialDelayMS=0, maintenanceFrequencyMS=60000, connectionPoolListeners=[], maxConnecting=2}, serverSettings=ServerSettings{heartbeatFrequencyMS=10000, minHeartbeatFrequencyMS=500, serverMonitoringMode=AUTO, serverListeners='[]', serverMonitorListeners='[]'}, sslSettings=SslSettings{enabled=true, invalidHostNameAllowed=false, context=null}, applicationName='TestCluster', compressorList=[], uuidRepresentation=STANDARD, serverApi=null, autoEncryptionSettings=null, dnsClient=null, inetAddressResolver=null, contextProvider=null}```
AasawariAasawari SahasrabuddheMongoDB Employee
Jun 2024

Hi @Ben_Crow,

Welcome to the community forum!

The logs you’re seeing are generated when the MongoClient attempts to connect to the database. While these logs are helpful for debugging and understanding your MongoDB client configuration, they can be quite verbose and may clutter your log output, especially in production environments.

These logs typically appear when there are multiple MongoClient connections. Could you confirm if you’re using MongoClient multiple times? If so, this might be contributing to the log volume.

To reduce unnecessary logs, you can adjust the logging level. For instance, configuring your logging framework to set the log level for org.mongodb.driver to ERROR or higher will suppress most of the logging output from the MongoDB driver.

Best regards,
Aasawari


Want to read more? Browse other topics in Drivers or view latest topics.