[SERVER-73950] Make all logs for query sampling go under the kSharding component Created: 13/Feb/23 Updated: 29/Oct/23 Resolved: 15/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Cheahuychou Mao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
The logs for the QueryAnalysis{Sampler,Writer,Coordinator} are currently categorized under the kDefault component because strictly speaking query sampling can be used separately from the analyzeShardKey command. However, this has made debugging quite cumbersome since to see the level 1+ log messages, we need to increase the default log verbosity which includes all other components. Making the log messages go under the kSharding would allow us to see the messages by increasing just the log verbosity for the kSharding component. |
| Comments |
| Comment by Githook User [ 15/Feb/23 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: |