[SERVER-31915] Abstract pretty printing of mongo::Message Created: 10/Nov/17 Updated: 06/Dec/22 Resolved: 28/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Henrik Edin | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Participants: | |||||||||
| Description |
|
Quite some code is needed to log a mongo::Message, it might need to be decompressed before calling opMsgRequestFromAnyProtocol. Should be abstracted so it's easy to use. |
| Comments |
| Comment by Henrik Edin [ 28/Jul/22 ] |
|
blake.oler@mongodb.com I highly doubt this is still needed/valuable. Feel free to close this ticket. |
| Comment by Blake Oler [ 28/Jul/22 ] |
|
henrik.edin@mongodb.com can you give us further context on why we need this and if it's still relevant? Five years is a long time |
| Comment by Lauren Lewis (Inactive) [ 21/Dec/21 ] |
|
We haven’t heard back from you in at least 1 year, so I'm going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket. |