-
Type: Improvement
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Diagnostics, Logging
-
Service Arch
The { setParameter: 1, logLevel: N } command (for N > 0) is the user requesting more verbose logging, often to send to Support for analysis. Having basic information about server startup parameters, version, and so on, would help to give context to the verbose logs.
Thus, it would be very useful if, when running setParameter to increase logLevel to a value above 0, the start of the verbose logging also included the baseline information that gets logged at startup and log rotation (SERVER-7140), eg.
2015-06-16T11:28:28.612+1000 [conn5] pid=14592 port=27017 64-bit host=genique 2015-06-16T11:28:28.613+1000 [conn5] db version v2.6.10 2015-06-16T11:28:28.613+1000 [conn5] git version: 5901dbfb49d16eaef6f2c2c50fba534d23ac7f6c 2015-06-16T11:28:28.613+1000 [conn5] build info: Linux build18.nj1.10gen.cc 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49 2015-06-16T11:28:28.613+1000 [conn5] allocator: tcmalloc 2015-06-16T11:28:28.614+1000 [conn5] options: { config: "/etc/mongod.conf", net: { bindIp: "127.0.0.1,127.0.1.1" }, storage: { dbPath: "/var/lib/mongodb", preallocDataFiles: false, smallFiles: true }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongod.log" } }
- related to
-
SERVER-7140 Print same information that prints on startup when the log is rotated
- Closed
-
SERVER-18985 setParameter should log at level 0
- Closed