Repository navigation
VAPI-4167 feat: per-peer sent/received counters in call stats - #29
Merged
Merged
Conversation
Add publishPeer and subscribePeer to CallStatsSnapshot, each holding that peer connection's own audio RTP packets/bytes sent and received, so stats can be attributed to the peer they came from. Existing flat fields are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
nasanov-bw
approved these changes
Oct 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira: VAPI-4167
Summary
publishPeerandsubscribePeer(new exportedPeerCallStatstype) toCallStatsSnapshot.packetsSent,bytesSent,packetsReceived,bytesReceived, read only from that peer connection's own stats report, so stats can be attributed to the peer they came from.bytesSentis still publish outbound, flatbytesReceivedis still subscribe inbound, bitrates unchanged).getCallStatssection documents the new fields.Example snapshot fragment:
{ "packetsReceived": 10, "bytesReceived": 2000, "packetsSent": 20, "bytesSent": 4000, "publishPeer": { "packetsSent": 20, "bytesSent": 4000, "packetsReceived": 0, "bytesReceived": 0 }, "subscribePeer": { "packetsSent": 0, "bytesSent": 0, "packetsReceived": 10, "bytesReceived": 2000 } }Test plan
npm testpasses (180 tests)🤖 Generated with Claude Code