[SERVER-51772] Collect more initial sync metrics Created: 20/Oct/20 Updated: 18/Feb/22 |
|
| Status: | Investigating |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Evin Roesle | Assignee: | Alan Zheng |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
In order to truly understand what are the driving factors in the initial sync time, we need to track more metrics on specific aspects of the initial sync process. Other dimensions that could be important, such as -
We need to think through all of the areas we believe could be driving initial sync times and see if we can quantify and track them through different metrics. |
| Comments |
| Comment by Evin Roesle [ 21/Oct/20 ] |
|
TBD at this point and time. I am interested in any input though if you have suggestions bruce.lucas |
| Comment by Bruce Lucas (Inactive) [ 21/Oct/20 ] |
|
Is this intended for serverStatus (if so, for ftdc?), mongod logs, or tbd? |