feat: add HandoffMetrics for measuring agent handoff timing#5442
Open
feat: add HandoffMetrics for measuring agent handoff timing#5442
Conversation
Add HandoffMetrics to measure the cost of agent handoffs, including: - drain_duration: time to drain the old activity (on_exit + pending speech) - new_activity_duration: time to start/resume the new activity - on_enter_duration: time for the new agent's on_enter callback - stt_reused / realtime_session_reused: whether resources were reused
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.
Summary
HandoffMetricsto measure agent handoff cost, emitted viametrics_collectedand attached toAgentHandoff.metricsdrain_duration,new_activity_duration,on_enter_duration, and totaldurationstt_reused,realtime_session_reused)Limitation
HandoffMetricsdoes not include the WebSocket connection time for new realtime sessions or STT streams. When resources are not reused, the connection is established asynchronously in a background task. This connection time is already reported separately viaRealtimeModelMetrics.acquire_timeandSTTMetrics.acquire_timethrough the existingmetrics_collectedpipeline.