[SERVER-55069] include operationProfiling parameter values in serverStatus Created: 09/Mar/21 Updated: 30/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | 4.4.4 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Sedor | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | query-offsite | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
Including in serverStatus the parameter values that influence logging will provide context for what is seen (or not seen) in mongod logs at any given time and simplify comparison between logs from differently configured nodes in diagnostic tools.
|
| Comments |
| Comment by Bruce Lucas (Inactive) [ 09/Mar/21 ] |
|
Not sure about the filter value - it wouldn't be usable in ftdc for example, I don't think. The other two would be as you say very valuable. |