springboot整合mongodb时日志输出问题

日志打印输出会出现下列的问题

2019-02-14 23:59:42.559 logback [cluster-ClusterId{value='5c656f9dc971e900070fb48a', description='null'}-172.16.252.247:3717] DEBUG org.mongodb.driver.cluster - Updating cluster description to  {type=REPLICA_SET, servers=[{address=172.16.252.246:3717, type=REPLICA_SET_PRIMARY, roundTripTime=0.7 ms, state=CONNECTED}, {address=172.16.252.247:3717, type=REPLICA_SET_SECONDARY, roundTripTime=0.7 ms, state=CONNECTED}]
2019-02-14 23:59:42.559 logback [cluster-ClusterId{value='5c656f9dc971e900070fb48a', description='null'}-172.16.252.246:3717] DEBUG org.mongodb.driver.cluster - Updating cluster description to  {type=REPLICA_SET, servers=[{address=172.16.252.246:3717, type=REPLICA_SET_PRIMARY, roundTripTime=0.6 ms, state=CONNECTED}, {address=172.16.252.247:3717, type=REPLICA_SET_SECONDARY, roundTripTime=0.7 ms, state=CONNECTED}]
2019-02-14 23:59:52.559 logback [cluster-ClusterId{value='5c656f9dc971e900070fb48a', description='null'}-172.16.252.247:3717] DEBUG org.mongodb.driver.cluster - Checking status of 172.16.252.247:3717
2019-02-14 23:59:52.559 logback [cluster-ClusterId{value='5c656f9dc971e900070fb48a', description='null'}-172.16.252.246:3717] DEBUG org.mongodb.driver.cluster - Checking status of 172.16.252.246:3717
2019-02-14 23:59:52.560 logback [cluster-ClusterId{value='5c656f9dc971e900070fb48a', description='null'}-172.16.252.247:3717] DEBUG org.mongodb.driver.protocol.command - Sending command '{ "ismaster" : 1 }' with request id 1697 to database admin on connection [connectionId{localValue:4, serverValue:76938}] to server 172.16.252.247:3717
2019-02-14 23:59:52.560 logback [cluster-ClusterId{value='5c656f9dc971e900070fb48a', description='null'}-172.16.252.246:3717] DEBUG org.mongodb.driver.protocol.command - Sending command '{ "ismaster" : 1 }' with request id 1698 to database admin on connection [connectionId{localValue:3, serverValue:83463}] to server 172.16.252.246:3717
2019-02-14 23:59:52.560 logback [cluster-ClusterId{value='5c656f9dc971e900070fb48a', description='null'}-172.16.252.247:3717] DEBUG org.mongodb.driver.protocol.command - Execution of command with request id 1697 completed successfully in 0.48 ms on connection [connectionId{localValue:4, serverValue:76938}] to server 172.16.252.247:3717
2019-02-14 23:59:52.560 logback [cluster-ClusterId{value='5c656f9dc971e900070fb48a', description='null'}-172.16.252.246:3717] DEBUG org.mongodb.driver.protocol.command - Execution of command with request id 1698 completed successfully in 0.52 ms on connection [connectionId{localValue:3, serverValue:83463}] to server 172.16.252.246:3717
2019-02-14 23:59:52.560 logback [cluster-ClusterId{value='5c656f9dc971e900070fb48a', description='null'}-172.16.252.247:3717] DEBUG org.mongodb.driver.cluster - Updating cluster description to  {type=REPLICA_SET, servers=[{address=172.16.252.246:3717, type=REPLICA_SET_PRIMARY, roundTripTime=0.6 ms, state=CONNECTED}, {address=172.16.252.247:3717, type=REPLICA_SET_SECONDARY, roundTripTime=0.7 ms, state=CONNECTED}]
2019-02-14 23:59:52.560 logback [cluster-ClusterId{value='5c656f9dc971e900070fb48a', description='null'}-172.16.252.246:3717] DEBUG org.mongodb.driver.cluster - Updating cluster description to  {type=REPLICA_SET, servers=[{address=172.16.252.246:3717, type=REPLICA_SET_PRIMARY, roundTripTime=0.6 ms, state=CONNECTED}, {address=172.16.252.247:3717, type=REPLICA_SET_SECONDARY, roundTripTime=0.7 ms, state=CONNECTED}]

会一直刷新,这样的查日志的时候就会很恶心.
那我们怎么解决呢?
聪明的你也想到了吧,当然是去logback.xml文件中把monogdb.driver相关的日志级别进行调整.写法如下:

<!--mongodb loggers-->
    <logger name="org.mongodb.driver.cluster" level="INFO"/>
    <logger name="org.mongodb.driver.connection" level="INFO"/>
    <logger name="org.mongodb.driver.protocol.insert" level="INFO"/>
    <logger name="org.mongodb.driver.protocol.delete" level="INFO"/>
    <logger name="org.mongodb.driver.protocol.query" level="INFO"/>
    <logger name="org.mongodb.driver.protocol.getmore" level="INFO"/>
    <logger name="org.mongodb.driver.protocol.command" level="INFO"/>
    <logger name="org.mongodb.driver.protocol.uri" level="INFO"/>
    <logger name="org.mongodb.driver.protocol.management" level="INFO"/>

这样问题就得到解决了