Participant joined_at_ms to get higher resolution of join time. - #949
Conversation
|
|
would it make sense to add a |
|
Will look at adding that @bcherry . One note though. room creation time and participant join time could be using different clocks in cloud as they could be on different nodes. But, it should be within the clock skew of servers which is probably okay for the kind of comparisons you have mentioned. |
Follow up to this PR - #949 and this comment - #949 (comment)
|
Protocol change PR - #950 |
* Room creation time with ms resolution. Follow up to this PR - #949 and this comment - #949 (comment) * generated protobuf --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
Regenerated from cloud-observability schema/gateway.yaml realtime (speech-to-speech) billing columns (#502). Adds ReportRealtime{DurationSeconds, Input{Text,Audio,Image, Video}Tokens, Output{Text,Audio}Tokens, Cached{Text,Audio}Tokens} to the gateway model reporter, so agent-gateway can emit the realtime_* metrics that populate the observability rollup consumed by analytics-recorder (#949) and backend-common (#939).
* generated: add realtime reporter methods to gatewayobs Regenerated from cloud-observability schema/gateway.yaml realtime (speech-to-speech) billing columns (#502). Adds ReportRealtime{DurationSeconds, Input{Text,Audio,Image, Video}Tokens, Output{Text,Audio}Tokens, Cached{Text,Audio}Tokens} to the gateway model reporter, so agent-gateway can emit the realtime_* metrics that populate the observability rollup consumed by analytics-recorder (#949) and backend-common (#939). * generated protobuf --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
No description provided.