|
Im trying to update log settings on a running DB through the JS file
db.setLogLevel(0);
|
db.setLogLevel(1, 'accessControl');
|
db.setLogLevel(0, 'command');
|
db.setLogLevel(1, 'control');
|
db.setLogLevel(0, 'ftdc');
|
db.setLogLevel(0, 'geo');
|
db.setLogLevel(0, 'index');
|
db.setLogLevel(1, 'network');
|
db.setLogLevel(1, 'network.asio');
|
db.setLogLevel(0, 'network.bridge');
|
db.setLogLevel(0, 'query');
|
db.setLogLevel(3, 'replication');
|
db.setLogLevel(0, 'sharding');
|
db.setLogLevel(0, 'storage');
|
db.setLogLevel(0, 'storage.journal');
|
db.setLogLevel(0, 'tracking');
|
db.setLogLevel(0, 'write');
|
db.setLogLevel(0, '-');
|
If i give any other values than 0 or 1 in these commands, i get what feels like the full debug log.
As an example, with this config
db.getLogComponents()
|
{
|
"verbosity" : 0,
|
.....
|
"replication" : {
|
"verbosity" : 3
|
},
|
I am getting this REPL log
gg-mongo_1 | 2017-10-20T10:31:25.802+0000 D REPL [replication-1] Reporter sending slave oplog progress to upstream updater 192.168.33.33:27017: { replSetUpdatePosition: 1, optimes: [ { durableOpTime: { ts: Timestamp 1508492498000|3, t: 20 }, appliedOpTime: { ts: Timestamp 1508492498000|3, t: 20 }, memberId: 0, cfgver: 12 }, { durableOpTime: { ts: Timestamp 1508495480000|1, t: 21 }, appliedOpTime: { ts: Timestamp 1508495480000|1, t: 21 }, memberId: 1, cfgver: 12 }, { durableOpTime: { ts: Timestamp 1508495480000|1, t: 21 }, appliedOpTime: { ts: Timestamp 1508495480000|1, t: 21 }, memberId: 2, cfgver: 12 }, { durableOpTime: { ts: Timestamp 0|0, t: -1 }, appliedOpTime: { ts: Timestamp 1508495480000|1, t: 21 }, memberId: 3, cfgver: 12 } ], $replData: { term: 21, lastOpCommitted: { ts: Timestamp 1508495480000|1, t: 21 }, lastOpVisible: { ts: Timestamp 0|0, t: -1 }, configVersion: 12, replicaSetId: ObjectId('59e9ab765f33763b41eb2637'), primaryIndex: 0, syncSourceIndex: 0 } }
|
|
That looks like a Debug log to me..
|