[SERVER-8825] Write stack traces via logging framework (syslog,ramlog, etc...) Created: 01/Mar/13  Updated: 11/Jul/16  Resolved: 10/Jul/13

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: 2.2.3, 2.4.0-rc1
Fix Version/s: 2.5.1

Type: Improvement Priority: Major - P3
Reporter: Nicholas Tang Assignee: Andy Schwerin
Resolution: Done Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-8749 Stack traces aren't captured in globa... Closed
Related
related to SERVER-5092 Better named logging with tracing Closed
Participants:

 Description   

Currently, stack traces don't go to syslog. It'd be great to have this be a configuration option so that you can enable stack traces or disable them when using syslog.



 Comments   
Comment by Andy Schwerin [ 10/Jul/13 ]

Fixed as a side-effect of SERVER-10084.

Comment by Neal Lawson [ 15/Apr/13 ]

it would be nice to include a crash report tool to collect required info and submit to 10gen as part of this project.

Comment by Nicholas Tang [ 15/Mar/13 ]

Well, I can give you some examples: SERVER-6706, SERVER-7450, and SERVER-7454. If you look through JIRA there may be others, but those are the issues I'm aware of.

Thanks,
Nicholas

Comment by Grégoire Seux [ 15/Mar/13 ]

can you precise suboptimal?

Comment by Nicholas Tang [ 15/Mar/13 ]

Currently, nowhere - they're just truncated and dropped, so this ticket should address that. (Currently, syslog handling in MongoDB is suboptimal, but we're working on it.)

Thanks,
Nicholas

Comment by Grégoire Seux [ 15/Mar/13 ]

so where does stack traces go when using syslog?

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