[SERVER-21770] Support storage engine specific log/profile output fields (per operation) Created: 04/Dec/15 Updated: 06/Dec/22 Resolved: 09/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging, Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Igor Canadi | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 6 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Comments |
| Comment by Igor Canadi [ 04/Dec/15 ] |
|
Correct, this is only for logging and profile output. I don't think there's a need to attach anything to explain. Adding state to currentOp might be useful, but it's not a priority. |
| Comment by Scott Hernandez (Inactive) [ 04/Dec/15 ] |
|
So you want to include stuff for logging/profile output, not for explain, correct? Or is the goal to support more information in currentOp output, while it is running only? |
| Comment by Igor Canadi [ 04/Dec/15 ] |
|
Sorry, pressed Enter too soon. (I think this ticket might already exist, but I just spent 5min looking for it and couldn't find it) Currently RocksDB adds counters to each query in a pretty hacky way: https://github.com/mongodb-partners/mongo/commit/eaecfc73a0c0b547b91708cf98233f48b46608d0. It would be great to have a generic way of adding storage-engine specific counters to a query. |