Major - P3 Investigating a test failure I noticed that the lock manager dump had a "truncated" message at the end,
[initandlisten] "lock manager dump","attr": ....... ..... {"lockRequest":"0x28b2","lockRequestAddr":"0x7f77f610cd00","thread":"140151986423552","mode":"IX","convertMode":"NONE","enqueueAtFront":false,"compatibleFirst":false,"debugInfo":"","clientInfo":{"desc":"conn282","connectionId":282,"client":"127.0.0.1:52265","opid":10399}}, {"lockRequest":"0x2932","lockRequestAddr":"0x7f77fded8700","thread":"140152063268608","mode":"IX"}]}]}, "truncated":{"locks":{"0":{"granted":{"33":{"convertMode":{"type":"string","size":9}}}}}},"size":{"locks":81237}
Logv2 messages need logv2::LogTruncation::Disabled set in order to avoid truncation.
The lock manager dump logv2 message does not currently have this set.
It would also be great if we could get the log message to span multiple lines instead of being scrunched into a single really long line that's hard to read, but I don't know how to do that.