[SERVER-16618] Log file should print extended json compliant syntax Created: 20/Dec/14 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Logging, Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Thomas Rueckstiess | Assignee: | Backlog - Security Team |
| Resolution: | Unresolved | Votes: | 4 |
| Labels: | move-sec, platforms-re-triaged | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Server Security
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||
| Description |
|
We have extended json syntax for most types, see http://docs.mongodb.org/manual/reference/mongodb-extended-json/ There are two flavors: "strict" and "shell" mode. Yet when certain types are printed in the log file, they don't comply to either of these formats, instead using arbitrary syntax that is hard to parse and cannot be simply copy&pasted back into the shell. All types should be printed as strict or shell syntax in the log for consistency. Preferably shell syntax since mongo shell can't yet understand strict syntax (see related ticket, Examples: Timestampshell
log file
NumberLongshell
log file (would be misinterpreted as floating point value)
BinDatashell
log file (quotes missing)
And so on. |