[SERVER-3847] db.setProfilingLevel(2) doesn't log what was inserted Created: 14/Sep/11 Updated: 16/Nov/21 Resolved: 14/Sep/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Usability |
| Affects Version/s: | 2.0.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Russell Smith | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | profiling | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OS X 10.7, MongoDB 2.0, though it did the same on 1.8 |
||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
> use profilingtest > db.getProfilingLevel() ) > db.system.profile.find() reslen:74 bytes:58", "millis" : 0 } { "ts" : ISODate("2011-09-14T10:40:47.091Z"), "info" : "insert profilingtest.somecollection", "millis" : 2 }{ "ts" : ISODate("2011-09-14T10:40:54.220Z"), "info" : "query profilingtest.somecollection ntoreturn:1 reslen:67 nscanned:1 \nquery: {} nreturned:1 bytes:51", "millis" : 0 } |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 14/Sep/11 ] |
|
The output is from 1.8; I have created a new issue for what you want: |
| Comment by Russell Smith [ 14/Sep/11 ] |
|
BTW: Currently my work around is to parse data from mongosniff; 127.0.0.1:55917 -->> 127.0.0.1:27017 profilingtest.somecollection 80 bytes id:47 71 Which works nicely |