[SERVER-50624] Submit Log Ingestion Rule Request Form for Initial Sync metrics in 4.4 Created: 28/Aug/20 Updated: 11/Mar/21 Resolved: 11/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Evin Roesle | Assignee: | Wenbin Zhu |
| Resolution: | Done | Votes: | 0 |
| Labels: | former-quick-wins | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Sprint: | Repl 2020-12-28, Repl 2021-03-22 | ||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Description |
|
Currently, we log initial sync metrics while the initial sync is running but discard once the initial sync is finished. In order to have a better understanding of the initial sync performance for our customers, we should preserve this information after the initial sync is complete. We can use log ingestion on 4.4 clusters to keep the initial sync metrics in our current logs to begin. There will be a separate ticket for 4.2 and earlier as those logs are structured differently. *Current initial sync metrics to keep from the logs - * *failedInitialSyncAttempts |
| Comments |
| Comment by Eric Milkie [ 07/Oct/20 ] |
|
I don't see why having the stats available transiently is better than either putting the stats in the system log to be scraped or making the stats durable by writing them to a collection (perhaps in local.startup_log or a system.profile). That seems like it would be less work and easier for downstream consumers to collect. |