[SERVER-13942] Consider placing mongodb version info in stacktrace output Created: 14/May/14  Updated: 17/Dec/19  Resolved: 17/Dec/19

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

Type: Improvement Priority: Minor - P4
Reporter: Andrew Morrow (Inactive) Assignee: Billy Donahue
Resolution: Won't Fix Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-13944 Provide richer unwind information in ... Closed
is related to SERVER-17859 Add buildId info to all platforms Closed
Sprint: Dev Tools 2019-11-18, Dev Tools 2019-12-02, Dev Tools 2019-12-16, Dev Tools 2019-12-30
Participants:

 Description   

People often forget to tell us what version of mongodb the were running when they report a crash: https://jira.mongodb.org/browse/SERVER-13941.

If we placed some minimal version info into the stack trace output, we might cut down on the back and forth on such tickets to decide if they are a known issue or novel misbehavior.



 Comments   
Comment by Billy Donahue [ 17/Dec/19 ]

It's something we already do except on Windows.

But Windows doesn't generate a significant amount of production logs.
So adding the version info to Windows stackdumps is low-value.

Comment by Andy Schwerin [ 21/Nov/15 ]

This is resolved for posix systems as of SERVER-13944, in all versions since 2.7.1. The information is in the json blob printed at the top of stack traces, though not pretty-printed. Should this ticket be just for Windows, acm?

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