[SERVER-18986] When increasing logLevel above 0, log basic startup info Created: 16/Jun/15  Updated: 23/Feb/23  Resolved: 24/Feb/22

Status: Closed
Project: Core Server
Component/s: Diagnostics, Logging
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Kevin Pulo Assignee: Backlog - Service Architecture
Resolution: Won't Do Votes: 0
Labels: move-sec, neweng, re-triaged-ticket
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-7140 Print same information that prints on... Closed
related to SERVER-18985 setParameter should log at level 0 Closed
Assigned Teams:
Service Arch
Participants:

 Description   

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" } }



 Comments   
Comment by Lauren Lewis (Inactive) [ 24/Feb/22 ]

We haven’t heard back from you for at least one calendar year, so this issue is being closed. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Generated at Thu Feb 08 03:49:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.