-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
In order to have a better picture of how our initial sync is performing in current and previous versions, we need to add more metrics to our logs.
Current important metrics that we already have in our logs -
- failedInitialSyncAttempts
- approxTotalDataSize
- approxTotalBytesCopied
- totalInitialSyncElapsedMillis
- initialSyncAttempts
- appliedOps
- databases.databasesCloned
Future metrics to add (names and methods are TBD)
- successfulInitialSyncAttempts
- resumedInitialSyncAttempts
- collectionsCloned = length of listCollections response
- <collection>.approxBytesCopied = collStats.avgObjSize * documentsCopied
- indexesCloned = dbStats.indexes
- totalIndexSize = dbStats.indexSize
- totalInitialSyncOplogElapsedMillis = time for oplog application phase
- initialSyncMethod
- resycOrAddingNode
- depends on
-
SERVER-53476 Don't include initial sync metrics in FTDC
- Closed
-
SERVER-50624 Submit Log Ingestion Rule Request Form for Initial Sync metrics in 4.4
- Closed
- is related to
-
SERVER-47528 Presence of initialSyncStatus in replSetGetStatus consumes too much FTDC space
- Closed
-
SERVER-47863 Initial Sync Progress Metrics
- Closed
- related to
-
SERVER-53381 Submit Log Ingestion Rule Request Form for Initial Sync Metrics in 4.2 and earlier
- Closed
-
SERVER-50624 Submit Log Ingestion Rule Request Form for Initial Sync metrics in 4.4
- Closed