[SERVER-15084] Add a "fatal" log level to the server Created: 28/Aug/14  Updated: 10/Dec/14  Resolved: 29/Aug/14

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

Type: Improvement Priority: Major - P3
Reporter: Ramon Fernandez Marina Assignee: Matt Kangas
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-13608 Allow streaming log messages into fas... Closed
Related
related to SERVER-15044 Coverity analysis defect 25617: PW.BO... Closed
Participants:

 Description   

Right now mongod calls functions like fassert() when it finds a fatal condition. This yields a brief message in the log followed by at least one stack trace, which often makes users think they've run into a mongod bug.

It would be nice to be able to produce more informative error messages whenever mongod finds a fatal error. Ideally, one would be able to call things like this in the code:

fatal() << “some message”;
fassert(12345, condition) << “some message”;
fassertNoTrace(12345, condition) << “some message”;



 Comments   
Comment by Andy Schwerin [ 29/Aug/14 ]

Duplicate of SERVER-13608

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