Issue ID:
Type
Bug
Title:
Add additional logging to outgoing (client) replication
Created:
11/3/2022 10:45:40 AM by Alex
Status:
Awaiting Release on 11/17/2022 11:40:28 AM
Last pulled:
11/18/2022 3:56:08 PM
Description:
To help diagnose/troubleshoot slow/problematic edge node replications, it'd be nice to add some additional logging: ~~Size (of the package or blob, maybe image?) would be helpful to identify speed~~ (size of package/blob/chunk is already logged if Service.FeedReplicationVerboseLogging is set to true) At the end, it would be nice to log something like... * "Execution #241559 finished successfully at 10/24/2022 9:35:38 AM, after 1h 17m" * "Execution #241559 failed at 10/24/2022 9:35:38 AM, after 1h 17m" At the start, can we change the "packagesToPush" to be "itemsToPush"? This is what's currently logged: * 1184 local packages processed: packagesToPush=1, packagesToFetch=0, deletesToFetch=0 * Gathering list of local deletes... * 6334 local deletes processed: deletesToPush=1355, packagesToFetch=0 Just saying "itemsToPush" would make it work for both packages and containers.