[SERVER-86068] Accept workingMillis as a filter parameter for setProfilingLevel Created: 01/Feb/24 Updated: 02/Feb/24 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Shin Yee Tan | Assignee: | Shin Yee Tan |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Execution Team 2024-02-19 |
| Participants: |
| Description |
|
setProfiling level accepts filters where the field in the filter expression can be any field in the profiler output. Verify that workingMillis can be used as a threshold to adjust slow query logging output. We should also check whether waitForTicketDurationMillis can also be used as a filter since it should be a field in profiler output (may split out to different ticket). |