feat(server): switch ping-pong latency aggregation to per-socket

[znewton]

Description

Switches the R11s Socket latency telemetry from global aggregation (average over time) to per-socket aggregation (average over threshold ping-pong events). This allows for better telemetry granularity (percentiles, tenant/document narrowing, etc.) at the cost of more generated telemetry. The amount of telemetry can be tuned with the pingPongLatencyTrackingAggregationThreshold config, where 1 ping-pong event should happen every ~25 seconds.

Breaking Changes

An internal param that was never used was removed, and a config that was never set was removed.

Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.

Files not reviewed (1)

• server/routerlicious/packages/routerlicious/config/config.json: Language not supported

Comments suppressed due to low confidence (2)

server/routerlicious/packages/services-shared/src/socketIoServer.ts:327

• Ensure that the new behavior introduced by pingPongLatencyTrackingAggregationThreshold is covered by tests.

private initPingPongLatencyTracking(

server/routerlicious/packages/services-telemetry/src/lumberEventNames.ts:65

• [nitpick] The telemetry event name SocketConnectionLatency should be consistent with existing naming conventions. Consider renaming it to SocketIoConnectionLatency.

SocketConnectionLatency = "SocketConnectionLatency"

[tylerbutler]

Approved for docs.