|
I just did a quick test of setting to 2, then 0:
Mon May 21 20:53:30 [conn1] runQuery called admin.$cmd { replSetGetStatus: 1.0, forShell: 1.0 }
|
Mon May 21 20:53:30 [conn1] run command admin.$cmd { replSetGetStatus: 1.0, forShell: 1.0 }
|
Mon May 21 20:53:30 [conn1] command: { replSetGetStatus: 1.0, forShell: 1.0 }
|
Mon May 21 20:53:30 [conn1] command admin.$cmd command: { replSetGetStatus: 1.0, forShell: 1.0 } ntoreturn:1 keyUpdates:0 reslen:76 0ms
|
|
|
Mon May 21 20:53:36 [conn1] runQuery called admin.$cmd { setParameter: 1.0, logLevel: 0.0 }
|
Mon May 21 20:53:36 [conn1] run command admin.$cmd { setParameter: 1.0, logLevel: 0.0 }
|
Mon May 21 20:53:36 [conn1] command: { setParameter: 1.0, logLevel: 0.0 }
|
Mon May 21 20:53:36 [conn1] command admin.$cmd command: { setParameter: 1.0, logLevel: 0.0 } ntoreturn:1 keyUpdates:0 reslen:46 0ms
|
This looks fine.
Maybe you want setParameter to log at info (0) level all the time? That isn't a bad idea, but def. is a different issue.
|