Repository navigation
VAPI-4167 feat: trace call stats every 10 seconds while in a call - #26
Merged
Merged
Conversation
A second trace runs only while a subscribe call stream is active: it starts when the first call stream becomes available and logs a final snapshot when the last one ends, on disconnect, or on a signaling reconnect. The 5-minute trace is unchanged; the two run independently and may log at the same time. 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
3 participants
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
In-call statssnapshot at debug level.onStreamAvailable). Ends with aFinal in-call stats (<reason>)snapshot when the last call stream ends (call ended), ondisconnect, onsignaling disconnected, on a replacingconnect, and on a signalingreconnect(the old streams never fireonremovetrackafter the subscribe peer connection is rebuilt).Call statstrace is unchanged. The two traces run independently, keep separate bitrate baselines, and may log at the same moment.deviceDiagnostics, so the in-call snapshots reach the diagnostics S3 export for accounts enabled indiagnostics.s3ExportAccountIds.Test plan
npm test(prettier + jest): 166 passed, including new in-call trace tests (start/stop on stream lifecycle, concurrent streams, disconnect, reconnect, independence from the 5-minute trace, baseline handling, final read before peer connection close)🤖 Generated with Claude Code