From 94ac51f84057f2b07e70ee8f4f2d6108bff9a917 Mon Sep 17 00:00:00 2001 From: NicholasCouri Date: Wed, 17 May 2023 16:10:32 -0700 Subject: [PATCH] OpRoundtripTime telemetry is wrong (#15620) ## Description In connections where have 2 or more OpRoundtripTime triggered within the same connection, we will have incorrect values as we we do not reset opProcessingTimes. The second time and every time afterwards, durationNetwork is going to be empty because it gets reset after the OpRoundtripTime is triggered but opProcessingTimes.outboundPushEventTime does not get reset. [Task 4006](https://dev.azure.com/fluidframework/internal/_workitems/edit/4006). --- packages/runtime/container-runtime/src/connectionTelemetry.ts | 1 + 1 file changed, 1 insertion(+) diff --git a/packages/runtime/container-runtime/src/connectionTelemetry.ts b/packages/runtime/container-runtime/src/connectionTelemetry.ts index f545b0c1d544..96300a34ff57 100644 --- a/packages/runtime/container-runtime/src/connectionTelemetry.ts +++ b/packages/runtime/container-runtime/src/connectionTelemetry.ts @@ -285,6 +285,7 @@ class OpPerfTelemetry { }); this.clientSequenceNumberForLatencyStatistics = undefined; this.opPerfData = {}; + this.opProcessingTimes = {}; } } }