-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Server Security
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
0
As part of SPM-3866, we added new diagnostic logs that print after stack trace logs for operations that fail. This is intended to increase the information available to engineers in AF/BF/HELP investigations.
In particular, we added support for logging CurOp OpDebug output (for more details, see SERVER-92764 and SERVER-96564). This extra logging was enabled by default for CRUD commands only. Other commands can opt in by overriding this method.
This ticket is to assess if there are commands owned by this team that should opt in to the extra diagnostic logging. Considerations should include if it would be helpful to see the command BSON in the logs when debugging a failure, or if there is any reason the (redacted) command text should specifically not be included in logs.
- is related to
-
SERVER-92764 Extend diagnostic logging on tassert failure to dump contents of CurOp/OpDebug
-
- Closed
-
-
SERVER-96564 Extend diagnostic logging in tassert/invariant/signal handling to apply to additional commands
-
- Closed
-