[SERVER-61491] Log stacktraces to file Created: 15/Nov/21  Updated: 29/Oct/23  Resolved: 07/Jan/22

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

Type: New Feature Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: Mark Benvenuto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-62028 Run the symbolizer on CI output Closed
Backwards Compatibility: Fully Compatible
Sprint: Security 2021-11-29, Security 2021-12-13, Security 2021-12-27, Security 2022-01-10
Participants:

 Description   

Add an option to log the "BACKTRACE" message (here) to a file. The human-readable backtrace can be kept as-is in case the symbolized version is not available for any reason.

We'd like to use this functionality to automatically symbolize all backtraces run in Evergreen as part of the linked project. The symbolizer would run after a test fails to find any stacktraces in the files generated by the servers.

This can be a test-only functionality and does not have to be configurable. The location of the log files can be fixed (relative to the data dir) to simplify implementation.

If this can be enabled with --setParameter enableTestCommands=true, a separate command line option would not be needed



 Comments   
Comment by Githook User [ 07/Jan/22 ]

Author:

{'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}

Message: SERVER-61491 Tee backtrace log records to a separate file
Branch: master
https://github.com/mongodb/mongo/commit/dc3e993e06feb97a79de71baadd48d3b732423f9

Comment by Githook User [ 07/Jan/22 ]

Author:

{'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}

Message: SERVER-61491 Tee backtrace log records to a separate file
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/e349c81400cf50b8993ff83a12ac0a8ffab5891d

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