[SERVER-27396] /proc equivalent for MongoDB Created: 13/Dec/16 Updated: 27/Oct/23 Resolved: 18/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ronan Bohan | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Gone away | Votes: | 5 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Query
|
||||
| Participants: | |||||
| Description |
|
Similar to the /proc filesystem on Linux it would be really useful to have a readonly 'virtual database' (or perhaps a virtual collection in the local database) in MongoDB which exposes various metrics, e.g. serverStatus, getCmdLineOpts, sharding info, etc, allowing this data to be accessible to the query subsystem rather than just through explicit commands. This could provide a standard interface allowing access to a vast array of useful statistics, metrics, etc for the running server. |
| Comments |
| Comment by Charlie Swanson [ 18/Nov/20 ] |
|
Over the last couple years the query team has added a number of metadata sources like this:
I'm going to close this ticket as "gone away", but if there is another specific metric or source for an aggregation pipeline that we are missing, please file a separate ticket. |
| Comment by Andy Schwerin [ 13/Dec/16 ] |
|
I like this idea. I want more data returned in cursors, to get around document size limits, and this might be a good way to think about it. Even better, it allows users to use aggregation expressions to describe desired filtering, grouping, etc. |